The standups are also organized around disrupting a small group of people for the convenience of one.
replyStandups should eliminate almost all other meetings engineers need to attend. Except to go deeper on questions that came up in standup that cannot be instantly resolved.
replyOtherwise yeah there’s really no point.
Do you mean standups as part of Scrum? Scrum dictates several other meetings.
replyI will allow one more meeting to start a new sprint and end the previous one. Everyone should have prepared ahead of time to report on all their sprint items and whether they were completed, if not why not, and to present the work they will be doing in the next sprint.
replyIf the Scrum Master or whatever their title schedules any other repeating process meetings, fire them.
I would be pleased with the standup if it eliminated other meetings, but that has definitely not been my experience.
replyBe the change you want to see.
replythere should be only 3 regular meetings in an agile engineering team
- weekly iteration planning (1-2 hours max)
- daily standup (15 mins max)
- weekly demo & retro (1-2 hours max)
replyliterally everything else is work off the kanban board or backlog.
in my teams everyone was told to decline all meetings unless it explicitly led to the completion of a weekly planned story/task. this way all meetings for the team have a clear agenda and end in mind.
for mandatory external meetings & running interference with external parties, there are ways to insulate the majority of the team from that.
Is that three kinds of regular meetings? Because I count 8 meetings (and four kinds, as I don't think I've ever had demo and retro combined due to different groups of people being in both).
reply