5 ms·
It doesn't sound like the 'Agile' team is doing standups right. There are either too many people in the room, or people are talking too much, and probably abou
by WalterSear 10y ago
It doesn't sound like the 'Agile' team is doing standups right.
There are either too many people in the room, or people are talking too much, and probably about the wrong things.
And, if they are doing standups wrong, I question how much else they are cargo-culting.
- reacharavindh 10y agoYes, everyone in there knows that scrum meetings should be short, but somehow those meetings take long, because everyone thinks their questions needs answers and their dependabcies definitely must be resolved.. so, an hour it goes.
- WalterSear 10y agoThe point of a standup isn't to get answers or resolve dependencies - it's to make others aware of them. The first thing we do after stand ups is have a bunch of quick one-on-one or small group meetings.
- acbabis 10y agoOur meeting format was for each person to say a) What they worked on, b) What they were about to work on, and c) If they needed help with anything. Our rule was that you could ask for help as long as you were just scheduling a time to meet after the stand-up. It worked really, really well. Then we got a new scrum master whose desired format was to talk about each item on the Kanban board each day, even the ones that weren't being worked on.
- lisivka 10y agoIt's status meeting. Developers unlike status meeting, so they invented their own meeting: daily standup meeting.
- blub 10y agoThis is really bad and a major failure on the part of the scrum master. The point of this meeting is to help the team sync on what they are doing and what they plan to do. It should take 10m at most. Any issues (blockers, dependencies, etc) should be taken to separate ad-hoc discussions to let the team get back to work.
- melvinmt 10y agoIf there is no room for syncing up and every issue is to be taken offline, one should question if it makes sense the stand ups should be kept in sync. In my team we do standups asynchronously over Slack, it's a great and non obtrusive way of updating each other and we achieve the same thing.
- WalterSear 10y agoIt's not the same. The standup performs an important social function of making everyone involved in the work of the team. People have to face each other, feel accountable to, and feel supported by the group. And of course there's no room for synching up: The morning standup is meant to facilitate those synch-up meetings, synch-ups that don't have to involve everyone.
- dasmoth 10y ago>>> The standup performs an important social function of making everyone involved in the work of the team. People have to face each other, feel accountable to, and feel supported by the group. This is a fantastic description. And it goes a long way towards explaining why standup (even if I'm not directly involved) leave me feeling so uncomfortable.
- lisivka 10y agoKick project manager out of standup meeting and you will love them.
- WalterSear 10y agoIf that makes your standups better, you need a competent project manager.
- lisivka 10y agoYou are right, problem is in project manager head, which abuses standup for status updates because of lack of understanding of purpose of standup meeting, or because of lack of discipline (developers may provide infrequent updates in git/jira). It's hard to debug development process by email. However, if developers will do their standups properly, then their development process will fix itself. (Or project manager will fire the most active one. ;-) )
- fsloth 10y agoGenerally claiming that a person is doing the method wrong when the method brings no percieved benefits raises a red flag on the general applicability and value of the methodology itself on the problem the person is trying to solve. There is no one true way to organize development of software and generally shoehorning dogma without proof of value is counterproductive.
- spinlock 10y agoI think you can absolutely diagnose an hour-long daily standup as "wrong". Standups need to be limited to 10-15 minutes. That's one of the key tenants of standups: they need to be short and focused.
- fsloth 10y agoYes, regardless of the process framework used having the team meet daily for an hour is pathological and probably is indicator of deeper issues. Which just doing agile "more by the book" wont fix.
- lisivka 10y agoAre you really can stand for hours at the standup meeting? :-) Standup daily meeting must be short and focused. Moreover, standup meeting is for developers only. No project manager, no customer, no QA team. Just developers talking about their problems. Everything else deserves it own separate, hour long meeting once a week or two.
- reledi 10y agoJust want to stress the importance of having stand-ups be developer-only. Do not let project managers, product owners, stakeholders, clients, and so forth become part of it. The developers won't be ready to start working when they take their seats because a lot was said in standup without actually saying much.
- patmcguire 10y agoEh, it's valid in this case. Ten minutes standup is formulated as being opposed to a full meeting. The full meeting was there first, standups are supposed to be different. If it's turning into the full meeting it's worth calling that out.