Project Management Central
|
Please login or join to subscribe to this thread
|
||||||
|
||||||
Hum, this is an interesting and confusing question.
Another interesting one would be: "Why do you wnt to create a template for the daily Standup?" A Daily Standup is a informal dicussion that is supposed to answer the 3 questions listed by Christiana. It is not supposed to be a meeting with a formal agenda and meeting minutes. During the Daily Standup you focus on the communication, not on keeping notes of it. So I am confused. What would be the point of a template? ...
2 replies by Christiana Etuk
Jan 26, 2023 12:29 AM
Christiana Etuk
...
The aim is to have some form of reference but it may not necessarily be a long sentence depending on the team's choice
Jan 26, 2023 12:43 AM
Christiana Etuk
...
Hello Patrice, the aim of my question is to share my view and also understand the views of the seasoned professionals regarding having a template for a Daily stand-up. The outcome of this template is to build consistency and a point of reference if the team chooses to do so.
Christiana -
Those three questions are no longer considered to be "standard" for daily coordination events. If you check the Scrum Guide, it does not reference them any more. Each team needs to: 1. Decide if a daily coordination event is necessary and valuable to them. 2. Figure out how they will run it and what they will discuss 3. Regularly review the value of the event and adjust it as needed to continue to be of value. This could include dropping it entirely if they are already collaborating well and would be better served with a just-in-time approach to such events. And having a standard template breaks two of the Manifesto's values: - Individuals and interactions over processes and tools - Working software over comprehensive documentation Kiron ...
2 replies by Aaron Porter and Christiana Etuk
Jan 25, 2023 10:29 AM
Aaron Porter
...
Just having one or two standard templates doesn't break the Agile Manifesto's values. OVER does not mean IN PLACE OF, and the intent needs to be considered, as well. Creating a quick template as a starting point and allowing the meeting format to evolve in response to team needs is not the same as creating a template and enforcing it across multiple teams without allowing for flexibility or adaptation.
To your point, not allowing the team to have input into how the meeting is run could be considered less agile, but what does that really mean?. I'm just saying that occasionally straying onto the right side of the manifesto doesn't necessarily break anything. Jan 26, 2023 12:30 AM
Christiana Etuk
...
Kiron thank you such an elaborate points. I will have to agree with you on this but however the template will not change the meeting but to build consistency.
I agree with Kiron.
Christiana, I do fully agree with Kiron’s feedback on every front.
Jan 25, 2023 7:47 AM
Replying to Kiron Bondale
...
Christiana -
Those three questions are no longer considered to be "standard" for daily coordination events. If you check the Scrum Guide, it does not reference them any more. Each team needs to: 1. Decide if a daily coordination event is necessary and valuable to them. 2. Figure out how they will run it and what they will discuss 3. Regularly review the value of the event and adjust it as needed to continue to be of value. This could include dropping it entirely if they are already collaborating well and would be better served with a just-in-time approach to such events. And having a standard template breaks two of the Manifesto's values: - Individuals and interactions over processes and tools - Working software over comprehensive documentation Kiron To your point, not allowing the team to have input into how the meeting is run could be considered less agile, but what does that really mean?. I'm just saying that occasionally straying onto the right side of the manifesto doesn't necessarily break anything. ...
1 reply by Kiron Bondale
Jan 25, 2023 4:55 PM
Kiron Bondale
...
The benefit of a template is reduction in effort and an increase in consistency.
Deciding whether and how to hold a daily coordination event takes next to no effort and because the event is by the team and for the team, consistency won't really matter (between teams). I think it is reasonable for a seasoned agile lead to provide examples of how an event was held in their past experiences but multiple examples will not stifle the team's creativity the way a template with a single option would. I believe this is the main reason why the Scrum Guide authors elected to do away with the standard questions. Kiron
Check this article about daily standup templates for agile teams using Atlassian: https://www.atlassian.com/agile/scrum/standups
...
2 replies by Christiana Etuk and KWIYUH MICHAEL WEPNGONG
Jan 26, 2023 12:35 AM
Christiana Etuk
...
Thank you Veronica for this template.
Jan 26, 2023 11:10 AM
KWIYUH MICHAEL WEPNGONG
...
Useful resource, thanks Veronica
Jan 25, 2023 10:29 AM
Replying to Aaron Porter
...
Just having one or two standard templates doesn't break the Agile Manifesto's values. OVER does not mean IN PLACE OF, and the intent needs to be considered, as well. Creating a quick template as a starting point and allowing the meeting format to evolve in response to team needs is not the same as creating a template and enforcing it across multiple teams without allowing for flexibility or adaptation.
To your point, not allowing the team to have input into how the meeting is run could be considered less agile, but what does that really mean?. I'm just saying that occasionally straying onto the right side of the manifesto doesn't necessarily break anything. Deciding whether and how to hold a daily coordination event takes next to no effort and because the event is by the team and for the team, consistency won't really matter (between teams). I think it is reasonable for a seasoned agile lead to provide examples of how an event was held in their past experiences but multiple examples will not stifle the team's creativity the way a template with a single option would. I believe this is the main reason why the Scrum Guide authors elected to do away with the standard questions. Kiron Jan 25, 2023 5:21 AM
Replying to Patrice Blanchard
...
Hum, this is an interesting and confusing question.
Another interesting one would be: "Why do you wnt to create a template for the daily Standup?" A Daily Standup is a informal dicussion that is supposed to answer the 3 questions listed by Christiana. It is not supposed to be a meeting with a formal agenda and meeting minutes. During the Daily Standup you focus on the communication, not on keeping notes of it. So I am confused. What would be the point of a template? Jan 25, 2023 7:47 AM
Replying to Kiron Bondale
...
Christiana -
Those three questions are no longer considered to be "standard" for daily coordination events. If you check the Scrum Guide, it does not reference them any more. Each team needs to: 1. Decide if a daily coordination event is necessary and valuable to them. 2. Figure out how they will run it and what they will discuss 3. Regularly review the value of the event and adjust it as needed to continue to be of value. This could include dropping it entirely if they are already collaborating well and would be better served with a just-in-time approach to such events. And having a standard template breaks two of the Manifesto's values: - Individuals and interactions over processes and tools - Working software over comprehensive documentation Kiron Jan 25, 2023 2:58 PM
Replying to Verónica Elizabeth Pozo Ruiz
...
Check this article about daily standup templates for agile teams using Atlassian: https://www.atlassian.com/agile/scrum/standups
|
||||||
Please login or join to reply
ADVERTISEMENTS
|
"Talk low, talk slow, and don't say too much." - John Wayne |
