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

Labels:

Comments

Post a Comment

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
Post a Comment
Read more

Why is potentially shippable product quality important

Agile teams work in iterations. During this period, they are supposed to work on product increments which can be “delivered” at the end of iteration. But how you know that the correct product was delivered? Many teams have different kinds of acceptance criteria and Definition of Done (DoD). But in many cases, this “done” is not the real “done” there might be some testing pending, some integration or review pending or anything else which prevents the actual use of the product increment. Many of these teams will need additional iterations to finish hardening their products. Many teams will implement different types of “gates” or approval steps to move to next stage. The free flow of product will be interrupted. They might end up doing mini waterfall within their agile process. Many don’t even realize this. This results in poor quality and requires additional effort to “harden” the product. Potentially Shippable Product increment The acceptance criteria and DoD should be modified
Post a Comment
Read more

Product Backlog: Should you write everything in user story format?

I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I
Post a Comment
Read more