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.

Bill Krebs - 10 Years of Scrum Meetings


Published on

presented at Southern Fried Agile 2010.

Published in: Technology
  • Be the first to comment

Bill Krebs - 10 Years of Scrum Meetings

  1. 1. 10 years of Scrum Meetings<br />William Krebs, Agile Dimensions LLC<br />© 2010 Agile Dimensions LLC<br />
  2. 2. AgileBill Krebs<br />IBM Developer ’83-09<br />Founder of Agile Dimensions<br />Rockcliffe Board of Directors<br />Internal Agile Coach at Allscripts<br /><ul><li>Agile since 2001
  3. 3. MIS, CSM, CSP,MBTI, Innovation Games
  4. 4. Certificate in Virtual Worlds
  5. 5. Taught Agile Scrum and Lean to over 1,000 worldwide
  6. 6. Specialist in 2d and 3d web basedtraining and collaboration</li></li></ul><li>Before Agile - 1995<br />Format<br />What did you do<br />What will you do<br />Open space team room / bullpen<br />
  7. 7. Before Agile - 1995<br />Results<br />Not done often<br />Not understood as a pillar practice<br />Kept other meetings, so loathe to even add short ones<br />
  8. 8. XP Standup - 2002<br />Learned Agile – introduced to team<br />Not comfortable with all practices yet, so we started with the daily meetings“Hey, this is just like our daily war room meetings, we’ll do that!”<br />
  9. 9. XP Standup - 2002<br />Results<br />We crawled through the list of every bug. <br />For an hour. Each day.<br />Some tried to sand.<br />The experts talked.<br />The insecure talked more.<br />Bad smells<br />Needed 3 question format. Timeboxing. No status.<br />
  10. 10. Better XP Standup - 2004<br />3 Question Format<br />Yesterday<br />Today<br />Blockers<br />
  11. 11. XP Standup - 2004<br />Results<br />Late meetings<br />Long meetings<br />Few Blockers<br />Design on the Fly<br />Status Mania<br />
  12. 12. Bad Scrum Meeting – 2006<br />Approach<br />3 Question Format<br />Took minutes for those who could not attend<br />Tried to force timebox<br />
  13. 13. Bad Scrum Meeting – 2006<br />Results<br />No one read minutes<br />People panic when told they have two minutes<br />“Take it offline” items were not followed up<br />Few blockers arose<br />
  14. 14. Good Scrum 2008<br />Approach<br />Better understanding of Role of Scrum Master<br />Rotated into Scrum Master role, so people know what to look for<br />Used ‘Power of 2’ – focus talk on the top two things you did<br />Talk about stuff from the sprint backlog<br />Culture change – blockers are good!<br />
  15. 15. Good Scrum 2008<br />Results<br />On time<br />Early problem detection<br />Ties into big visible indicators like taskboard and burndown<br />Key gear on the Scrum process machine<br />
  16. 16. Now teams are global<br />
  17. 17. Global Scrum 2010<br />Global Teams are the norm<br />Sometimes used teleconferences <br />Used virtual worlds for sense of proximity and “co-interaction”<br />
  18. 18. Teleplace – Data Centric<br />
  19. 19.
  20. 20.
  21. 21.
  22. 22. Many timezones, but feel together<br />
  23. 23. Agile Hopscotch © 2010 Agile Dimensions LLC <br />
  24. 24. Global Scrum 2010<br />Results<br />Spatial Audio, body language, shared venue, and co interactive objects made us feel together<br />Able to quickly teach Scrum concepts to laypersons<br />
  25. 25. Discussion Questions<br />When do we update our burndown numbers?<br />What do we do for timezone spreads?<br />What do we do with specialists supporting multiple teams?<br />
  26. 26. Recommendations<br />Know who speaks next<br />Grid, circle, or prompt<br />“Take it offline” – and really do<br />Power of “2” – for beginners<br />Use for Pairing<br />Dump the 1 hour status meeting<br />Schedule 15 min buffer after Scrum meeting for quick breakouts<br />
  27. 27. More<br /><br /><br /><br /><br /><br />