The document discusses patterns and anti-patterns of daily standup meetings. It provides guidance on who should attend, what should be discussed, how to structure the meeting for efficiency. Key points include keeping the meeting focused on status updates, time-boxed to 15 minutes or less, standing instead of sitting to encourage brevity, and rotating facilitation to encourage autonomy. Anti-patterns that can undermine the meeting are identified as well, such as allowing socializing, late starts, or obstacle discussion without resolution.

1. Patterns &
Anti Patterns
of Stand Up
Xtreme Testing
19th & 20th Nov

2. Patterns of Daily StandUp Meeting
Who attends?
What do we talk about?
What order do we talk in?
Where and when?
How do we keep the energy level up?
How do we encourage autonomy?

3. Who Attends?
Developers
BAs
QAs
XDs
Managers
Product Owners
Client
People who wish to contribute to the status

4. What do we talk about?
Yesterday Today Obstacles

5. What order do we talk in?
Round Robin
Pass the token
Take a card
Walk the board

6. Where & When?
Meet where the work happens
Same Place Same Time
Use the Stand Up to start the day orDon’t use Stand Up to start the day

7. How do we keep the energy level Up?
Huddle over Meeting
Stand Up not Sitting
15 min or less
Signal the End
Time box the Meeting
Take it Offline

8. How do we encourage autonomy?
Rotate the facilitator
Break Eye Contact

9. Anti Patterns of Stand Up

10. How do we know when a Stand Up is going Poorly?
Focussed on the runners not the baton
Reporting to the leader
People are late and Stand Up Meeting starts the day...Late
Obstacles are not raised and removed
Obstacles raised only during stand up
Socialising
I can’t remember
Story Telling

11. Thank You!
“Get Up Stand Up”