Jun 9, 2023Liked by Conor Bronsdon, Dev Interrupted
I really like the idea that yesterday/today messages should be written before the daily, and the daily itself then is about blockers and the health of the iteration.
And in addition to people having a hard time confessing they're having difficulties, sometimes they simply don't realise they're blocked. There's this kind of tunnel effect and one (based on true story that happened to myself many oh times) keeps digging on the ticket/story with a certainly that it's progressing well, while, in fact, it's stalled. One symptom of that could be the same item being worked on for several days, and the yesterday/today update is the same.
In my experience, this will result in the "OMG, is this already the end of the iteration?!" surprise.
So for example, if the update for both days is "integrating with service X" or "creating component Y", then either the author is not verbose enough or they're in that stealth blocker.
For the verbosity, a better would be "Yesterday. Integrating with service X. Establishing framework and first connection. / Today. Integrating with service X. Implementing full capability and covering with tests."
Ideally, this would be different subtasks and obvious on the board, but splitting work into day-size sub-tasks is hard and often not worth the time.
I really like the idea that yesterday/today messages should be written before the daily, and the daily itself then is about blockers and the health of the iteration.
And in addition to people having a hard time confessing they're having difficulties, sometimes they simply don't realise they're blocked. There's this kind of tunnel effect and one (based on true story that happened to myself many oh times) keeps digging on the ticket/story with a certainly that it's progressing well, while, in fact, it's stalled. One symptom of that could be the same item being worked on for several days, and the yesterday/today update is the same.
In my experience, this will result in the "OMG, is this already the end of the iteration?!" surprise.
So for example, if the update for both days is "integrating with service X" or "creating component Y", then either the author is not verbose enough or they're in that stealth blocker.
For the verbosity, a better would be "Yesterday. Integrating with service X. Establishing framework and first connection. / Today. Integrating with service X. Implementing full capability and covering with tests."
Ideally, this would be different subtasks and obvious on the board, but splitting work into day-size sub-tasks is hard and often not worth the time.