Because that’s how it often goes. I find there are two types of scrums in practice. First is when it goes fast, and everybody just says they’re working. There’s no time to give any detail or context so the status update is largely meaningless. Second is when people start giving details about what they’re working on, and that quickly explodes to an hour long meeting.
Participants need to find the right balance of information. I noticed it is productive when developers give just enough information for other to understand but not too much to confuse them and loose time. This is not easy to achieve…
Because that’s how it often goes. I find there are two types of scrums in practice. First is when it goes fast, and everybody just says they’re working. There’s no time to give any detail or context so the status update is largely meaningless. Second is when people start giving details about what they’re working on, and that quickly explodes to an hour long meeting.
Participants need to find the right balance of information. I noticed it is productive when developers give just enough information for other to understand but not too much to confuse them and loose time. This is not easy to achieve…
Indeed it’s not, I also find developers tend to be really bad at this task in particular.