4 ms·
I mainly resent standups because most employers I've ever had scheduled them at 9am, and I'm not really ready to talk to other humans yet at that hour.
by melloclello 12y ago
I mainly resent standups because most employers I've ever had scheduled them at 9am, and I'm not really ready to talk to other humans yet at that hour.
- mbesto 12y agoWhich violates one of the main principles of Agile - "Responding to change over following a plan". That's worth bringing up in a sprint review.
- technofiend 12y agoConsider it the price you pay for potentially spending the balance of your day unmolested. When I ran agile-driven development teams it really helped me and my team in three ways: 1) any blockers they needed to escalate got to me at 9 AM not at 11 or 1 or whenever is more convenient for you, op, 2) it made it immediately clear who was not making progress, 3) it kept people honest about staying focused solely on their story. The latter was the most valuable because I had people who would agree to let (for instance) our deployment tool handle differences between releases as it was designed by the vendor, and then try to check in a zip or tar file because they couldn't be sure about the deployer. Or my guy who would agree to bang out a simple static page and next thing you know he's trying to write a framework. Some of these people were new to agile but the process including the standup helped me break them of a lot of bad habits. Still, I feel ya about early meetings. My boss is in a later timezone so my day starts at 7 local time, man. It could always be worse.
- tomjen3 12y agoCounterpoint: I am often in earlier than 8 but our semi-daily meetings are at 10. The real problem is that we do the meetings in person, rather than by writing a slack post/email, but there you go.
- melloclello 12y agoI'd just like to say that 10am is still too early for me. After lunch is more like where I'm at.
- firepoet 12y agoWhy not change it at retrospective? If daily standup has become rigid, it has violated the most important part of the manifesto: "Individuals and interactions over processes and tools." Every process of the team is open to change at retrospective: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." So change it. :-)