This document summarizes Bill Krebs' experience with Scrum meetings over 10 years, from early implementations in 2002 to more modern global implementations in 2010. It describes the evolution from long, status-focused meetings to shorter daily standups adhering more closely to the Scrum framework. Key lessons learned include using a structured format, timeboxing meetings, focusing on progress and blockers rather than status, and leveraging virtual tools to facilitate global collaboration. The document provides recommendations for effective Scrum meetings and handling different contexts like distributed teams.

1. 10 years of Scrum Meetings William Krebs, Agile Dimensions LLC © 2010 Agile Dimensions LLC

3. MIS, CSM, CSP,MBTI, Innovation Games

4. Certificate in Virtual Worlds

5. Taught Agile Scrum and Lean to over 1,000 worldwide

7. Before Agile - 1995 Results Not done often Not understood as a pillar practice Kept other meetings, so loathe to even add short ones

8. XP Standup - 2002 Learned Agile – introduced to team 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!”

9. XP Standup - 2002 Results We crawled through the list of every bug. For an hour. Each day. Some tried to sand. The experts talked. The insecure talked more. Bad smells Needed 3 question format. Timeboxing. No status.

10. Better XP Standup - 2004 3 Question Format Yesterday Today Blockers

11. XP Standup - 2004 Results Late meetings Long meetings Few Blockers Design on the Fly Status Mania

12. Bad Scrum Meeting – 2006 Approach 3 Question Format Took minutes for those who could not attend Tried to force timebox

13. Bad Scrum Meeting – 2006 Results No one read minutes People panic when told they have two minutes “Take it offline” items were not followed up Few blockers arose

14. Good Scrum 2008 Approach Better understanding of Role of Scrum Master Rotated into Scrum Master role, so people know what to look for Used ‘Power of 2’ – focus talk on the top two things you did Talk about stuff from the sprint backlog Culture change – blockers are good!

15. Good Scrum 2008 Results On time Early problem detection Ties into big visible indicators like taskboard and burndown Key gear on the Scrum process machine

16. Now teams are global

17. Global Scrum 2010 Global Teams are the norm Sometimes used teleconferences Used virtual worlds for sense of proximity and “co-interaction”

18. Teleplace – Data Centric

22. Many timezones, but feel together

23. Agile Hopscotch © 2010 Agile Dimensions LLC

24. Global Scrum 2010 Results Spatial Audio, body language, shared venue, and co interactive objects made us feel together Able to quickly teach Scrum concepts to laypersons

25. Discussion Questions When do we update our burndown numbers? What do we do for timezone spreads? What do we do with specialists supporting multiple teams?

26. Recommendations Know who speaks next Grid, circle, or prompt “Take it offline” – and really do Power of “2” – for beginners Use for Pairing Dump the 1 hour status meeting Schedule 15 min buffer after Scrum meeting for quick breakouts

27. More mmpubs.com meetup.com/agile3d agiledimensions.com linkedin.com/in/BillKrebs twitter.com/AgileBill4d