Common problem for not able to finish Daily Standup in 15 Mins
Reason1: Scrum team size. Scrum team with more than 7 members will impact timebox of 15 mins. For bigger project, the ideal Scrum team size should be 7 people (5 Developers + Product owner + Scrum Master). Smaller projects, the idea size should be 4 people (2 Developers + Product owner + Scrum Master).
Reason2: Discuss more topics than required. Daily Scrum is all about inspect and adapt. Inspect the progress so far and the amount of work that is left.
If the Product Owner and Scrum Master were at the Daily Scrum, I think you'd have an indication as to why the timebox was threatened. It would suggest that this is the only time people collaborate during the working day. They're trying to shoehorn a world of agile practice into 15 minutes.
A good Daily Scrum is 15 minutes out of a busy day in which the Developers stand aside from all of the buzz and collaboration going on and say "Where are we now in our progress towards the Sprint Goal? Which of us will be doing what over the next 24 hours?".
There should be no problem with up to 10 disciplined Developers being part of this. Others, including the PO and SM, have all the rest of the working day to collaborate, and no baggage is brought in which should be dealt with elsewhere.
Thanks Ian for your inputs on this subject. I follow your articles/responses all the time and I always love those.
I have never had this issue because of team size. As @Ian says, if the people are disciplined and fully understand the reason for the event it should be easy to keep within the 15 minute timebox.
As for your second reason that is pretty simple to solve. Focus on progress towards Sprint Goal. If there is something brought up that needs more conversation, do it after the Developers have discussed their progress towards the goal. There is no reason that people can't stay together and discuss things AFTER they have done the due diligence of discussing their progress towards the Sprint Goal. The Scrum Team should be in constant communication so there should be plenty of opportunities to discuss things in more detail. But during the Daily Scrum, they should focus on making sure everyone has the same level of understanding and identify things that need more discussion. It is not uncommon for teams that I work with to stay together for more than 15 minutes. But the first 15 minutes has a very specific purpose and that is their focus. After that, it is just more of their day doing software development as a team.
I agree with your thoughts Daniel but the main challenges come with the new comers who don't have the same level of understandings like others but eventually the stand up event becomes disciplined with same level of understandings with Scrum Master's guidance.
Any change to the team will result in some level of chaos. But if you are seeing frequent "new comers" I would suggest you lead the team in discovering why that happens. It will constantly impact the team's ability to reach a consistent flow.
New comers in the project for mostly changes in Project scope and work load.
Put this into your favorite search engine and do some reading.
tuckman stages of team development
Scrum is not immune to these issues.
Sure. Thanks a lot Daniel.
When Daily Scrum doesn't fit in 15 mins, maybe your PBIs should be bigger?
If you make them bigger, you have a smaller number of them, and you'll have less to talk about in the Daily Scrum.
I agreed with some reasons:
- lack of disciplined and fully understanding about daily
- big team size
- lack of communication and collaboration during sprint
Other things:
- Too many new or existing impediments
- wrongly turn to problem solving