I have never worked at a company where this actually goes right and could not be replaced by [insert ticketing system here]. We use Basecamp to do daily check-ins on a very high priority issue, if we have one, which we usually don't.
I have never worked at a company where this actually goes right and could not be replaced by [insert ticketing system here]. We use Basecamp to do daily check-ins on a very high priority issue, if we have one, which we usually don't.
I've never figured out why you couldn't just do it over slack or equivalent. It's massively inefficient to get everyone to meet up in the morning.
Think of it from the point of view that managers have mangers they report to. When shit goes wrong they have to cover their asses. "So it's late. But did you check on their progress? Wait just over slack, no actual meetings? Ok, that obviously needs improvement".
All this talk of standup meetings being primarily for managers is really weird. It's not for managers, and they have no reason to be present. It's for the team, to improve cooperation within the team. If the team has a better way to accomplish that, then they should use that.
From the scrum guide... "The Daily Scrum is a 15-minute time-boxed event for the Development Team."
It is the team's event, if there are other people there it should be at their request. The guide goes on to say that.. "If others are present, the Scrum Master ensures that they do not disrupt the meeting."
Stand-ups and all the process attendant appears to be universally imposed from on high as a micromanagement technique, or because they were sold the idea as some kind of silver bullet by a talk or a snake-oil consultant.
I feel like Scrum is for teams that suffer Stockholm syndrome from poor management and need to be taught how to human beings again.
The main value of Scrum as an official process, is that it gives you a stick with which to chase toxic management out of the room. They're not sufficiently Scrum if they crash your meetings and demand to be in charge. Though in my experience, most companies that do Scrum have a management that keeps their distance unless invited.
And to be clear, when I say "blocked" I'm not talking like "I can't get any work done until X", I'm more talking like "this particular avenue needs X to happen before I can continue it, so I'm shelving it for now and doing something else until we can get it resolved." If you find yourself in the former case, something has already gone horribly wrong that should probably have been resolved days ago.
Smoothly running teams don't need this, but many teams don't run that smoothly, and then it's better to address it at the stand up than not at all.