3 ms·
I would say that's perfectly okay, but not for the reason you think. If your status is "still working on the same issue", your team should respond with "how can
by paledot 6y ago
I would say that's perfectly okay, but not for the reason you think. If your status is "still working on the same issue", your team should respond with "how can we help?". If your status doesn't change, that's a sign that something's wrong at some level, whether it's because you're stalled or because the issue was poorly scoped or poorly defined.
- navaati 6y agoWhat about the fact that some stuff just takes time, is that not conceivable to you ?
- fragmede 6y agoStand up is not (supposed to be) oppositional/conflict driven (but there are many toxic workplace cultures). Obviously some things "just take time", but what is the stuff that's taking up time? Assume it's all developers in the room and we're all familiar with the code base. Are you doing a stupid boring refactor of a thing tat "just takes time" but someone on the team wrote - and they have thoughts on pitfalls to avoid if they were rewriting it? Are you banging your head against an elusive bug that "will just take time" to tease out? The point of the standup is to shine light on any number of stupid pitfalls that every developer, even (especially) seasoned developers get stuck on, have dealt with in the past, and can give guidance with. If you're just cargo-culting having a daily 15-minute meeting under the guise of agile or whatever, and it's just a status meeting, then cancel it, until after people learn to have a proper stand-up. Waking up just to go to a meeting and report "I'm still working on the thing", is a waste of everyone's time, and is a meeting that would have been better off as an email. (Provided people can send that email, which is not always possible, and is an entirely different topic.)
- crescentfresh 6y ago> your team should respond with "how can we help?" this would kill the meeting at my company, it would go off the rails as a thing that everyone is present for and listening to. Moving it "offline" - as is often done - only occurs once it has gone sufficiently off the rails in the first place. Not saying there's anything wrong with this process, just pointing out it's counter to the "keep it short" discussion happening in this thread.