Death By Scrum Meeting 2009

Pete Behrens Agile Organization & Process Coach  Guide enterprise organizations in transitioning to an agile organization implementing agile methods  Services for agile assessment, alignment, training and coaching Previous Experience  Led development of the requirements management solution RequisitePro – a core product in the IBM Rational product line – using the Rational Unified Process (RUP)  Consulted with EDS leading development of large data warehouse solutions using Rapid Application Development (RAD) © 2009 Trail Ridge Consulting, LLC 2

Certified Scrum Coach (CSC) Program  Guide-Level Certification equal to CST  Initiated in 2007  20 Certified Coaches Today (4 Local)  Pete Behrens, Bob Hartman, Richard Lawrence, Brad Swanson  CSC Principles 1. Advise and Consult Agile Organizations 2. Facilitate Learning and Adoption 3. Mentor Agile Leadership at all levels 4. Guide Agile Organizational Development © 2009 Trail Ridge Consulting, LLC 3

 CSM Certification Testing  CSM 2 Year Renewal  CSPO Standardization  Scrum Guide  Member Only Content  PMI and other partnerships  User Groups Starting Worldwide  Sao Paulo, Brazil - May 12-13  Munich, Germany - October 19-21 © 2009 Trail Ridge Consulting, LLC 4

Do these sound familiar?  “All members of the Scrum team should help testing.”  “PM should recognize the value of quality over features.”  “I’m pissed off to fix other guy’s bad design.”  “A lot of shitty code.”  “Sprints: I just hate the artificial time limits.”  “Give us more time per Sprint.”  “Scrum does not work unless management is committed to not disrupting the team in the Sprint.”  “Micro management causes a lack of motivation.” © 2009 Trail Ridge Consulting, LLC 6

We implement Scrum “All team members are working in the sprint. Developers are developing the backlog items. Testers are testing the backlog items the developers completed in the last sprint or two. Product Management is preparing the items for the next few sprints.” © 2009 Trail Ridge Consulting, LLC 7

Adding all Scrum meetings... 16 Sprint Meetings (in hours) c rum y S e 12 Dail ctiv o spe etr n tR Spri w 8 vie int Re Spr ann ing Spri nt Pl 4 0 1 2 3 4 Sprint Length (in weeks) © 2009 Trail Ridge Consulting, LLC 26

Adding all Scrum meetings... 16 Sprint Meetings (in hours) c rum y S e 12 Dail ctiv pe How much is o s etr n tR Spri w 8 vie int Re Spr 4 too much? Spri nt Pl ann ing 0 1 2 3 4 Sprint Length (in weeks) © 2009 Trail Ridge Consulting, LLC 27

Meetings are Ineffective - they lack context or focus Meeting Type Time Required Purpose & Format Keys to Success Daily 5 minutes Share daily schedules  Don’t sit down and activities  Keep it administrative Check-in  Don’t cancel even when some people can’t be there Weekly 45 – 90 minutes Review weekly  Don’t set agenda until after activities and metrics, initial reporting Tactical and resolve tactical  Postpone strategic obstacles and issues discussions Quarterly 1 - 2 days Discuss, analyze,  Limit to one or two topics brainstorm, and decide  Prepare and do research Strategic upon critical issues  Engage in good conflict affecting long-term  Get out of the office success Source: Death by Meeting, Patrick Lencioni © 2009 Trail Ridge Consulting, LLC 31

Death by Meeting - circa Scrum Meeting Type Time Required Purpose & Format Keys to Success Daily 5 minutes Share daily schedules  Don’t sit down Daily Scrum and activities  Keep it administrative Check-in  Don’t cancel even when some people can’t be there Weekly 45 – 90 minutes Review weekly  Don’t set agenda until after Sprint Meetings activities and metrics, initial reporting Tactical and resolve tactical  Postpone strategic obstacles and issues discussions Quarterly 1 - 2 days Discuss, analyze,  Limit to one or two topics Release Planning brainstorm, and decide  Prepare and do research Strategic upon critical issues  Engage in good conflict affecting long-term  Get out of the office success © 2009 Trail Ridge Consulting, LLC 32

Story Points are for looking ahead Backlog Item Points Release 1. Login portal 2. Display minutes 5 3 Plan 3. Support ticket call 8 4. Remote login help 13 5. Update profile 2 6. Buy more time 8 7. Single sign-on 20 8. Log rotation 5 9. Timer display 3 10. Automatic logout 1 11. Usage warning 2 12. Exchange 12 integration 13 13. HP Openview API 20 14. XML API 8 15. 300 logins/min 13 16. Location tracking 5 17. Intrusion detection 13 18. Update MySQL DB 20 19. Update Web Stack 13 20. Update Linux Kernel 8 21. Support Novel Auth 13 22. Support RADIUS Auth 8 23. Scan & Block Int. 40 24. AP Manager Int. 20 © 2009 Trail Ridge Consulting, LLC 38

Using Velocity Projections 160 160 Completed Remaining Remaining 120 120 Points Points 80 80 40 40 0 0 Jan Feb Mar Apr May Jun Jul Aug Sep Jan Feb Mar Apr May Jun Jul Aug Sep 150.0 Completed 150.0 Completed Remaining Remaining 112.5 112.5 Points Points 75.0 75.0 37.5 37.5 0 0 Jan Feb Mar Apr May Jun Jul Aug Sep Jan Feb Mar Apr May Jun Jul Aug Sep © 2009 Trail Ridge Consulting, LLC 39

Timebox All Meetings? Timeframe Daily Bi-weekly Quarterly Daily Sprint Sprint Sprint Release Scrum Retro Review Planning Planning Minutes 5 - 15 15 - 30 30 - 60 60 - 120 120 - 240 © 2009 Trail Ridge Consulting, LLC 45

Timebox All Meetings? Timeframe Daily Bi-weekly Quarterly Daily Sprint Sprint Sprint Release Scrum Retro Review Planning Planning Minutes 5 - 15 15 - 30 30 - 60 60 - 120 120 - 240 1/2 Day © 2009 Trail Ridge Consulting, LLC 45

Timebox All Meetings! Timeframe Daily Daily How do we Sprint Bi-weekly Sprint Sprint Quarterly Release Minutes Scrum 5 - 15 do this Retro 15 - 30 Review 30 - 60 Planning 60 - 120 Planning 120 - 240 effectively? 1/2 Day © 2009 Trail Ridge Consulting, LLC 46

Scrum teams work together and share commitment Analysis Handoffs Traditional Phased-based Lack Delays approach spreads the of Ownership Design team out over time Task Switching Development Lack of Commitment Test Compromised Quality Deployment Scrum brings the whole team into short time-boxes Analysis Shared Commitment Shared Ownership Design Shared Focus More Productive Development Quality Built In Test Deployment © 2009 Trail Ridge Consulting, LLC 59

Scrum Teams communicate Face-to-face Communication Effectiveness At whiteboard Face-to-face Conversation Video Conversation Phone Modeling Videotape Conversation Options Email Conversation Audiotape Documentation Paper Options Cold Hot © 2009 Trail Ridge Consulting, LLC 60

Where does team direction come from? CIO, CTO, VP Engineering Product Line Product Line Product Line Manager Manager Manager Functional Functional Functional Usability Manager Manager Manager Engineering DBA PMO Infrastructure Scrum Quality Team Assurance © 2009 Trail Ridge Consulting, LLC 70

Salesforce.com Feedback  89% are having the best time or good time  38% increase in feature request delivered per developer  94% feature request increase from 2006 - 2007  Since implementing our iterative development methodology which enables us to deliver more frequent releases, we have seen statistically significant improvements in our satisfactions scores across our service attributes from our features to our platform.  Wendy Close, Salesforce Customer Satisfaction Survey, Sr. Manager Product Marketing, Salesforce.com © 2009 Trail Ridge Consulting, LLC 73

Death By Scrum Meeting 2009

by Pete Behrens on Jun 30, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 15

Statistics

Death By Scrum Meeting 2009 — Presentation Transcript

http://www.slideshare.net	14
http://www.lmodules.com	1