Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How to run an effective (and fun) standup


Published on

  • Be the first to comment

How to run an effective (and fun) standup

  1. 1. How to run an effective (and fun) standup.<br />Notes from session at Agile Open NW<br />By Ed Kraay<br />
  2. 2. Objective<br />To communicate the learnings from an Agile Open NW Session to SIQ<br />Goal: To learn to identify when your standup may become dull and pointless, and learn some ways to fix it if that happens.<br />
  3. 3. Effective Standup?<br />What characterizes an<br />
  4. 4.
  5. 5. Ask good questions…<br />
  6. 6. Changeup the Order<br />
  7. 7. …Goes Last<br />
  8. 8. Team picks the time<br />
  9. 9. Use Humor<br />
  10. 10. End Crisply.<br />
  11. 11. Leave with Actions.<br />
  12. 12. Developers talk to eachother.<br />
  13. 13.
  14. 14. Good Audio for offsite.<br />
  15. 15. Non-effective Standup<br />What makes a <br />
  16. 16. Report to Leader<br />
  17. 17. Not coming prepared<br />
  18. 18. Waiting to talk til’ Standup.<br />
  19. 19. Starting too early<br />Too many people at standup<br />Shoegazing<br />
  20. 20. Standup as a design session.<br />Standup sitting down.<br />
  21. 21. Standup as a separate area from the team room.<br />Electronics on during standup.<br />
  22. 22. Standup starts the day.<br />Not reporting impediments.<br />Not stopping rat-holing.<br />
  23. 23. <ul><li>Random Placement of Scrum Master in order of standup
  24. 24. Ask questions to group vs. individuals as smells
  25. 25. SM Don't act as technical leader
  26. 26. SM don't make eye contact
  27. 27. SM Reiterate the value of standup to the team
  28. 28. SM Redirect decisions/approval back to the team
  29. 29. Pigs: Communicate lateness and report to the team, not to SM or PO
  30. 30. Don't say start, let the team say go: Spin the marker
  31. 31. Install a sense of team ownership. Do less for them. They will do more for themselves.</li></ul>Reporting to Leader – How to fix.<br />
  32. 32. People not prepared for Standup, how to fix<br />Make a list of things you did the evening before. Bring in the morning <br />Give some work time before the meeting to get in work mindset <br />Look at commit logs, records of work as a refresher <br />Minute timers: try to fill but not go over <br />Frame your day in how it is relevant to the group <br />Have a Splash Down: A second standup at end of the day or other time to review what we did <br />Have progress charts/info visible during standup <br />Don't tell the detail, pick up the highlights <br />
  33. 33. Only discussion is at Daily Standup<br />Status report takes away from the daily standup <br />Use a parking lot <br />Make sure folks follow up at the end of a meeting, not during the meeting <br />Schedule a design discussion <br />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 <br />Have developers reference the story & the task <br />End the scrum on a positive note <br />
  34. 34. How to make a dull Standup Fun<br />Now that you’ve figured out how to have an effective standup, how do you avoid a dull, repetitive, boring standup…. <br />
  35. 35. Spin the Marker<br />Use a Token<br />Bring a different token each sprint<br />
  36. 36. Bring Appreciations.<br />Team Member, I appreciate you for, X.<br />Encourage Woohoo!<br />Bring Food, Make it a surprise<br />Last one to finish standup says “Thank you”<br />
  37. 37. Do a dance if you’re late.<br />Create a non-human enemy<br />
  38. 38. Some Snapshots of the Event<br />