Skip to main content

The different types of Daily stand-up for different teams with different maturity; Can product owners and others speak during daily scrum


Daily stand up meeting serves a very important role in agile teams. In a way they are the risk
mitigation meeting. Team members talk about the risk for the iteration and overall product delivery.
The need of a daily stand up for a new team and a matured team is different and hence the need for different rules for different teams. Teams who are starting the agile/scrum journey needs a lot of help. They might be new to agile or might be working together with each other for the first time. A structured well-defined set of rules will help them grow.

For such teams the following rules are more than enough
  1. Daily Scrum Meeting Rules - http://www.theagileschool.com/2012/03/daily-scrum-meeting-rules.html 
  2. Daily scrum misconception, scrum meeting objectives and different stages of meeting http://www.theagileschool.com/2012/03/daily-scrum-misconception-scrum-meeting.html

Only team members are “allowed” to speak and scrum master should be present to help the team. This rule immensely helps the new team. I have followed this rule to the dot for the team who were just starting their journey with agile.  But I had different rules for a matured team.

Nothing is constant in agile. The teams without changes and continuous improvement are not agile at all. Nothing can be more anti-agile than seeing agile zealots and checklist cops “following” all rules without understanding any of them.

As the team matures, they need a different set of rules to help them grow to the next level. If the team feels that by allowing product owner or any other “outsider” speak during the daily stand up helps them then they should be allowed to. A matured scrum master or agile coach can recommend this.  When I was the product owner, I gave lot of updates during the daily stand up meeting and it helped both the team and myself.

Product Owner
  • can give update about the product features they are working on
  • provide industry updates or future of product
  • They can provide clarification to any queries from the team
Scrum Master
  • provide update on the progress on the "impediments" he/she is trying to remove
  • provide update on any organizational updates 
  • or anything which interests team members. 
Only thing you have to take care is about the duration of the meeting. Even with these extra updates duration of daily stand up should not exceed 15 minutes.
If Scrum Master, Product Owner or the invited "guest" feels that their updates will take more 1-2 minutes then they could briefly mention that they are going to talk about the "X" topic and people can stay after the daily scrum to listen to it. 

As with everything in agile the idea is to do continuous changes and keep the things which works. May be this works in one team and might not work in others. Adjust your process according to the needs of your team. As the team improves their agile maturity relax the rules so that they can grow further

Comments

Popular posts from this blog

PDCA & SCRUM (or Agile); Why is it important?

The PDCA (Plan DO Check Act) cycle was made popular by Dr. W. Edwards Deming. This is a scientific cyclic process which can be used to improve the process (or product). This is cyclic in nature and usually time boxed.

Plan 
This is the first stage of the process. During this step the team discusses the objectives, the process and the clear conditions of exit (conditions of acceptance). This stage sets the measurable and achievable goals for the team.

DO
Team works together to achieve the objective set in the planning phase. Team works with the set of agreed process.

Check
Once the implantation is done team regroups and verifies the output and compares it to the agreed conditions of acceptance decided during the planning phase. The deviation, if any, is noted down.

ACT
If any deviation in planned tasks is observed during the Check stage, a root cause analysis is conducted. Team brainstorms and identifies the changes required to prevent such deviations in future. Team also brainstorms idea…

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices.

Some of the rules 

The roles of Scrum
•Scrum Master - http://www.theagileschool.com/2012/03/scrummasters-checklist-roles.html
•Product Owner
•Feature TeamThe PDCA cycle (http://www.theagileschool.com/2012/05/pdca-scrum-or-agile-why-is-it-important.html )  frequent communication about risks (daily)
•Plan – Sprint planning
•Do – Actual engineering sprint – deliver a potential shippable code
•Check – Sprint review
•Act – Retrospective 
The scrum guide @ http://www.scrum.org/Scrum-Guides will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum.
Apart from these rest of the ceremonies and artifacts are there…

Challenge best practice?

Idea of best practices is a seductive but dangerous trap. … The great danger in “best practices” is that the practice can get disconnected from its intent and its context and may acquire a ritual significance that is unrelated to its original purpose.

They also inhibit a “challenge everything” culture and continuous improvement—a pillar of lean thinking. Why would people challenge ‘best’?