How to run an effective (and fun) standup
Download as PPTX, PDF6 likes6,609 views
The document provides tips for running an effective daily standup meeting that avoids becoming dull or pointless. Some key recommendations include asking questions of individuals rather than the group, varying the speaking order each day, having developers discuss their work with each other, and ending crisply with defined actions. The document also discusses problems like long-winded status reports or discussions instead of updates, and provides solutions such as using a parking lot for topics needing further discussion outside the standup.
How to run an effective (and fun) standup
- 1. How to run an effective (and fun) standup.Notes from session at Agile Open NWBy Ed Kraay
- 2. ObjectiveTo communicate the learnings from an Agile Open NW Session to SIQGoal: To learn to identify when your standup may become dull and pointless, and learn some ways to fix it if that happens.
- 7. …Goes Last
- 8. Team picks the time
- 9. Use Humor
- 10. End Crisply.
- 12. Developers talk to eachother.
- 14. Good Audio for offsite.
- 16. Report to Leader
- 18. Waiting to talk til’ Standup.
- 19. Starting too earlyToo many people at standupShoegazing
- 20. Standup as a design session.Standup sitting down.
- 21. Standup as a separate area from the team room.Electronics on during standup.
- 22. Standup starts the day.Not reporting impediments.Not stopping rat-holing.
- 23. Random Placement of Scrum Master in order of standup
- 24. Ask questions to group vs. individuals as smells
- 25. SM Don't act as technical leader
- 26. SM don't make eye contact
- 27. SM Reiterate the value of standup to the team
- 28. SM Redirect decisions/approval back to the team
- 29. Pigs: Communicate lateness and report to the team, not to SM or PO
- 30. Don't say start, let the team say go: Spin the marker
- 31. Install a sense of team ownership. Do less for them. They will do more for themselves.Reporting to Leader – How to fix.
- 32. People not prepared for Standup, how to fixMake a list of things you did the evening before. Bring in the morning Give some work time before the meeting to get in work mindset Look at commit logs, records of work as a refresher Minute timers: try to fill but not go over Frame your day in how it is relevant to the group Have a Splash Down: A second standup at end of the day or other time to review what we did Have progress charts/info visible during standup Don't tell the detail, pick up the highlights
- 33. Only discussion is at Daily StandupStatus report takes away from the daily standup Use a parking lot Make sure folks follow up at the end of a meeting, not during the meeting Schedule a design discussion Have an all day chat with the team: why wait to report an impediment in 24 hours, why not bring them to up when they happen **Encourage a developer TODO list Have developers reference the story & the task End the scrum on a positive note
- 34. How to make a dull Standup FunNow that you’ve figured out how to have an effective standup, how do you avoid a dull, repetitive, boring standup….
- 35. Spin the MarkerUse a TokenBring a different token each sprint
- 36. Bring Appreciations.Team Member, I appreciate you for, X.Encourage Woohoo!Bring Food, Make it a surpriseLast one to finish standup says “Thank you”
- 37. Do a dance if you’re late.Create a non-human enemy
- 38. Some Snapshots of the Event
Editor's Notes
- #5: Listening:http://customersrock.files.wordpress.com/2007/03/listening.jpg
- #6: Scrum Master Asking good questions: http://libizblog.files.wordpress.com/2007/10/question-mark.jpg
- #7: Don't go in same order each time : http://www.cs.jhu.edu/~pari/600.107/Horstmann/slides/Ch19/images/queue.png
- #8: PO goes last with updates
- #9: Have the team pick the time: http://www.infowit.com/images/time_graphic.jpg
- #10: Use humor: http://images.buycostumes.com/mgen/merchandiser/19788.jpg
- #11: Declare and End: http://kashifalvi.files.wordpress.com/2007/09/the-end.jpg
- #12: Take action afterward
- #13: Developers talk to eachother
- #14: Chickens are optional
- #15: Proper equipment for offsite folks, e.g. conference lines that work
- #17: Report to Leader
- #18: Not Prepared
- #19: Only Discussion at Standup
- #20: Too Early, Too Big, ShoeGazers
- #21: Standup Used as a design session, Sitting Down
- #22: Standup as a separate room from the team room, Electronics being used
- #23: Standup Starts the Day, No impediments recorded, Ratholing
- #28: Use a token, somethign fluffy that you can throw to the next person when it is their turn Bring a different token each sprint Spin the Marker to decide who goes first Offer appreciations at the beginning of a meeting. <Name of Person>, I appreciate you for <this>. Celebrate progress (Woohoos!), burndowns, impediments removed, etc Offer Food, coffee: better if it is not routine but a special thing Random stuff is helpful (though switching the time of standup is generally not helpful, it's confusing) Ask "How are you feeling?" Tell a story, a personal anecdote to start the meeting When someone leaves for a few days and comes back, tell them to bring back a tacky toy Whoever speaks first says thank you after the meeting Welcome people to standup Use "speed dating method" for impediments. Ask who has an impediment and then who can help them Bring a joke to standup (look up on internet) Create a non-human enemy (Someone mentioned a vista machine that was the enemy on the project) Ask, "how are we doing this morning?"
- #29: Appreciations,