50450Re: [scrumdevelopment] Deviating from Scrum: The standup meeting
- Mar 2, 2011peterskeide,
I was wondering if you could share some more context with us about your question.
How big is your Scrum team?
Is the PO collocated with the dev team?
What % of the PO's time does the PO spend working with the dev team?
As the ScrumMaster, are you also a developer on the team?
Does the PO wear more than one hat as well?
When does your dev team update the sprint backlog and sprint burndown?
Charles Bradley, CSM, PSM I
Experienced Scrum Coach
My blog: http://scrumcrazy.wordpress.com/
From: peterskeide <peterskeide@...>
Sent: Wed, March 2, 2011 7:05:38 AM
Subject: [scrumdevelopment] Deviating from Scrum: The standup meeting
During the last couple of years I have been a member of several small teams (3-4 people) that have started out using Scrum or some variation. After a while, I started noticing a trend: The teammembers see little or no value in the daily scrum meeting. Sometimes the team decides to drop it.
I'm currently Scrum Master for a team where we have made significant changes to the format for the standup meeting based on feedback from the retrospectives: we focus solely on impediments (a bit like the Kanban style standups). At present time, I get the feeling that some members of the team see no point in keeping even this part of the standup. This sprint I'm running an experiment where I've relied entierly on the team to self-organize the standup meeting. The result has been almost no standup meetings so far.
The best argument I have heard so far in favor of dropping the standup is that it can be redundant in a small, colocated team. When you sit around the same table all day, pair program often and generally talk to each other a lot, it's a bit like gilding the lily.
There are obvious downsides to dropping the standup: the visibility aspect of it lost. Granted, this only matters if people outside the team actually bothers to attend the meeting. Still, if there are no standup meetings, there will be nothing for potentially interested stakeholders to start attending.
Another problem I've experienced on teams who don't do standups is that important issues will sometimes escape the attention of people who can do anything about them before it is too late, despite colocation. Keeping the daily scrum will perhaps help teams catch some of these issues.
Standup meetings also have a commitment aspect that will be lost without them. Perhaps this can be offset by a collective feeling of responsibility for getting things done. When almost the entire team will work on a User Story, having each team member commit to get something done in front of the rest of the team doesn't always feel quite natural. A bit like going through the motions, perhaps.
Any thoughts about this? Similar experiences? Anybody know a format for the standup meeting that is a good fit for a small team?
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...! Groups Links
<*> To visit your group on the web, go to:
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
- << Previous post in topic Next post in topic >>