Project Management

Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Leadership, Teams
How Do You Plan For & Manage Stand-Ups?
Been leading a number of stand-ups now, and am thankful that my team is vastly experienced - we cover a lot of ground within just 15 mins.

Will be doing the same for a much less experienced team so the question has to be asked: are there any tips or general best practices to take note when: 1) planning for; and 2) running team stand-ups?
Sort By:
Jonathan -

Rather than re-invent the wheel, I'd suggest you search for the multiple articles which Mike Cohn has written on improving key Scrum ceremonies.

Kiron
Anonymous
The team ought to run stand-ups themselves and they shouldn't need any planning or management. In Scrum it is the Scrum Master's job to make sure that stand-ups happen but not to manage the meeting or even necessarily to be present at it (Scrum Master's presence is optional unless the SM is also a member of the development team).
@Kiron hit the nail. Adding to that, "we cover a lot of ground" means that something is not working in the daily stand up.
The purpose of Stand up meetings are to get status,
- What you did yesterday?
- What you work on today?
- Is there any impediment I can help?
It normally first thing in morning to get PM idea there was or wasn't any issue yesterday, what team will work on today, is there any blockage which need to be address or team needs PM help.
Its necessary for PM to help complete the sprint and monitor 'burn down chart', if everything is working smoothly then PM knows that sprint will be complete without any issue or any incomplete user stories.
Lets say if any developer has issue yesterday, PM can talk to that developer off line and help him resolve it. This way it won't be too late
...
2 replies by Kiron Bondale and Sergio Luis Conte
Jul 07, 2020 7:25 AM
Kiron Bondale
...
Sorry Tabassum -

the purpose of stand ups is NOT to get status. Status can be seen by using one of the information radiators available to any stakeholders such as a work board, burn down chart or so on.

Kiron
Jul 07, 2020 8:24 AM
Sergio Luis Conte
...
Well, when I read your post, my first reaction was to write the same than @Kiron. If people that using Scrum or others (Daily Stand-Up do not belongs to Scrum only) think the objective is getting status then forget about Agile or other thing at all. This is a classical "micro management" symptom which is worst in Agile based environments. In fact, the key, the indicator you are in the right way is when no questions are needed. The team goes to the meeting and express in a free way what help they need to moving forward. When some people say Agile is "a change in mindset" the change must start from the project/program/portfolio manager itself. And it is more than a change of mindset, is a change of behavor. At least, Agile by definition is "way of thinking and behave with focus in client, value and quality".
Jul 07, 2020 12:03 AM
Replying to Tabassum Mehmood
...
The purpose of Stand up meetings are to get status,
- What you did yesterday?
- What you work on today?
- Is there any impediment I can help?
It normally first thing in morning to get PM idea there was or wasn't any issue yesterday, what team will work on today, is there any blockage which need to be address or team needs PM help.
Its necessary for PM to help complete the sprint and monitor 'burn down chart', if everything is working smoothly then PM knows that sprint will be complete without any issue or any incomplete user stories.
Lets say if any developer has issue yesterday, PM can talk to that developer off line and help him resolve it. This way it won't be too late
Sorry Tabassum -

the purpose of stand ups is NOT to get status. Status can be seen by using one of the information radiators available to any stakeholders such as a work board, burn down chart or so on.

Kiron
Jul 07, 2020 12:03 AM
Replying to Tabassum Mehmood
...
The purpose of Stand up meetings are to get status,
- What you did yesterday?
- What you work on today?
- Is there any impediment I can help?
It normally first thing in morning to get PM idea there was or wasn't any issue yesterday, what team will work on today, is there any blockage which need to be address or team needs PM help.
Its necessary for PM to help complete the sprint and monitor 'burn down chart', if everything is working smoothly then PM knows that sprint will be complete without any issue or any incomplete user stories.
Lets say if any developer has issue yesterday, PM can talk to that developer off line and help him resolve it. This way it won't be too late
Well, when I read your post, my first reaction was to write the same than @Kiron. If people that using Scrum or others (Daily Stand-Up do not belongs to Scrum only) think the objective is getting status then forget about Agile or other thing at all. This is a classical "micro management" symptom which is worst in Agile based environments. In fact, the key, the indicator you are in the right way is when no questions are needed. The team goes to the meeting and express in a free way what help they need to moving forward. When some people say Agile is "a change in mindset" the change must start from the project/program/portfolio manager itself. And it is more than a change of mindset, is a change of behavor. At least, Agile by definition is "way of thinking and behave with focus in client, value and quality".
Hi,
I think Tabassum does not mean the status of project, He mean those questions to be answered/discussed during stand up meeting (for 10-15 min).
However for me I learned a good point from Kiron.
Thanks for sharing.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Common sense is the collection of prejudices acquired by age 18."

- Albert Einstein

ADVERTISEMENT

Sponsors