3 ms·
I don't agree entirely that the did/doing/next dialogue is bad. It's a well understood phenomena that declaring intent, and reflecting on achievement and pace i
by ggm 4y ago
I don't agree entirely that the did/doing/next dialogue is bad. It's a well understood phenomena that declaring intent, and reflecting on achievement and pace influences how you approach the problem.
This list is good, but it reads like the product of a person with focus and a low tolerance for others with a different pace and style. I can imagine them getting intensely frustrated with slow speakers, rambling PMs (me) and the like.
Does this inherently make them "right" or "more productive" -Yes, at the cost of possibly burn out, and the lack of cohesion from ideaologues who cannot listen or engage with others in their problems unless on the kanban, declared as blockers.
Its intruding another formalism for the one they don't like.
"don't talk to me this way" is a poor basis for mutuality. Maybe its "a little from box A, and a little from box B" ?
if 10 minutes of engagement with others causes this much angst, there's a bigger problem in play.
- lucasfcosta 4y agoAuthor here, thanks for your comment, I thought it was really thoughtful and well structured. I don't think the rambling itself is a problem. It will inevitably happen sometimes, and that's fine. It's part of making everyone feel safe. What I'm advocating for in this post is that we shouldn't create structures or formats which actively encourage rambling that does not add to the discussion. Furthermore, if those structures are inefficient (i.e. encourage rambling) and instil fear, you won't have 10 minutes of engagement with others, you'll probably have something like 30 minutes of unproductive technical discussion, which will cause the whole team to stop believing in the stand-up's purpose. That's not to say I disagree with you. I do agree we must find a balance, and that's why I add a few caveats to each of the recommendations, it's just that some practices are more prone to lead to inefficient meetings than others. Thanks again for chiming in with such a detailed and thoughtful piece of feedback.
- bigiain 4y agoFWIW, I mostly agree with your article, but I did find myself rolling my eyes a little when you started out reminding us of the origins of "Agile" and its principles, and criticising the rigid frameworks and practices it's metastasised into, but then the first piece of advice about how to "do it better" is to assume a Kanban board... For me, the "What did you do yesterday? What do you plan to do today? Is there anything blocking you?" questions work pretty well, with the expectation than nobody spends more than about 90 seconds answering all three. (This might just be because places I've recently worked haven't had well groomed or curated Kanban boards, but have had a mid and senior-heavy dev demographic?)
- ggm 4y agoAnother side of this is that I hate Jira, which is the kanban I am directed by work to use, so 'talk to the kanban' doesn't work for me personally. I do know highly effective PMs who are living it, and it works for them. I truly believe to do what you propose, you probably have to be a high functional unit workwise. If you are, and you know you are, your suggestions are a laudable goal.