• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Death By Scrum Meeting 2009
 

Death By Scrum Meeting 2009

on

  • 3,817 views

Pete has a new presentation series on Death by Scrum Meeting. He explores the potential in most organizations to fail with Scrum due to inappropriately applying the Scrum framework without fully ...

Pete has a new presentation series on Death by Scrum Meeting. He explores the potential in most organizations to fail with Scrum due to inappropriately applying the Scrum framework without fully understanding and applying the Scrum principles. In this presentation, he gets at the fundamental characteristic of Scrum - the team, and teaches leaders how to more effectively engage them in owning Scrum and their product/project goals.

Statistics

Views

Total Views
3,817
Views on SlideShare
3,793
Embed Views
24

Actions

Likes
7
Downloads
238
Comments
1

4 Embeds 24

http://www.slideshare.net 14
http://www.linkedin.com 7
https://www.linkedin.com 2
http://www.lmodules.com 1

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Death By Scrum Meeting 2009 Death By Scrum Meeting 2009 Presentation Transcript

    • Death by Scrum Pete Behrens Agile Organization & Process Coach © 2009 Trail Ridge Consulting, LLC pete@trailridgeconsulting.com 303.819.1809
    • 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
    • What are you here? WHAT SCRUM CHALLENGES ARE YOU FACING? © 2009 Trail Ridge Consulting, LLC 5
    • 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
    • How effective are meetings? © 2009 Trail Ridge Consulting, LLC 8
    • Scrum Skeleton? © 2009 Trail Ridge Consulting, LLC 9
    • Scrum Skeleton © 2009 Trail Ridge Consulting, LLC 10
    • What do you know about Scrum? © 2009 Trail Ridge Consulting, LLC 11
    • What do you know about Scrum? Shu Ha Ri © 2009 Trail Ridge Consulting, LLC 11
    • What do you know about Scrum? Shu Ha Ri Imitation Understanding Mastery © 2009 Trail Ridge Consulting, LLC 11
    • So what? Most Organizations IMPLEMENT Scrum But don’t UNDERSTAND Scrum ...and they are DYING © 2009 Trail Ridge Consulting, LLC 12
    • Scrum... WHY WAS SCRUM CREATED? © 2009 Trail Ridge Consulting, LLC 13
    • Why was Scrum Created? TEAMS solve problems better than individuals Teams solve problems better incrementally in short TIMEBOXES © 2009 Trail Ridge Consulting, LLC 14
    • Why was Scrum Created? TEAM © 2009 Trail Ridge Consulting, LLC TIMEBOX 15
    • The Haka © 2009 Trail Ridge Consulting, LLC 16
    • The Haka © 2009 Trail Ridge Consulting, LLC 16
    • Teams... HOW DO A GROUP OF PEOPLE BECOME A TEAM? © 2009 Trail Ridge Consulting, LLC 17
    • Creating a Team... Need to move people from DOING OWNING © 2009 Trail Ridge Consulting, LLC 18
    • ScrumMaster = Coach © 2009 Trail Ridge Consulting, LLC 19
    • Release Planning = Clear Goal © 2009 Trail Ridge Consulting, LLC 20
    • Sprints = Practice © 2009 Trail Ridge Consulting, LLC 21
    • Field = Transparency © 2009 Trail Ridge Consulting, LLC 22
    • Meetings = The Team Entry © 2009 Trail Ridge Consulting, LLC 23
    • How long are your sprint planning meetings? © 2009 Trail Ridge Consulting, LLC 24
    • How long are your sprint planning meetings? 16 Sprint Planning (in hours) 12 8 4 0 1 2 3 4 Sprint Length (in weeks) © 2009 Trail Ridge Consulting, LLC 24
    • How long are your sprint planning meetings? 16 Sprint Planning (in hours) 12 8 4 0 1 2 3 4 Sprint Length (in weeks) © 2009 Trail Ridge Consulting, LLC 24
    • How long are your sprint planning meetings? 16 Sprint Planning (in hours) 12 8 4 0 1 2 3 4 Sprint Length (in weeks) © 2009 Trail Ridge Consulting, LLC 24
    • How long are your sprint planning meetings? 16 Sprint Planning (in hours) 12 8 Why? 4 0 1 2 3 4 Sprint Length (in weeks) © 2009 Trail Ridge Consulting, LLC 25
    • 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
    • What else causes Meeting “Death”? © 2009 Trail Ridge Consulting, LLC 28
    • Death by Meeting  Meetings are boring  Meetings are ineffective © 2009 Trail Ridge Consulting, LLC 29
    • Meetings are Boring - they lack Action, Drama & Conflict © 2009 Trail Ridge Consulting, LLC 30
    • 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
    • Scrum Meeting Keys Focus Timebox Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 33
    • Scrum Meeting Keys Focus Timebox Strategic Tactical Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 33
    • Focus Release Sprint Planning Planning Sprint Review Daily Scrum Sprint Retro © 2009 Trail Ridge Consulting, LLC 34
    • Focus Strategic Tactical Daily Release Sprint Planning Planning Sprint Review Daily Scrum Sprint Retro © 2009 Trail Ridge Consulting, LLC 34
    • Focus Strategic Tactical Daily Release Sprint Scrum Release Sprint Planning Planning Sprint Review Daily Scrum Sprint Retro © 2009 Trail Ridge Consulting, LLC 34
    • Do you play Planning Poker? © 2009 Trail Ridge Consulting, LLC 35
    • Do you play Planning Poker? Why? When? © 2009 Trail Ridge Consulting, LLC 36
    • Planning Poker is a Release Tool Release Sprint Planning Planning Sprint Review Daily Scrum Sprint Retro © 2009 Trail Ridge Consulting, LLC 37
    • Planning Poker is a Release Tool Strategic Tactical Daily Release Sprint Planning Planning Sprint Review Daily Scrum Sprint Retro © 2009 Trail Ridge Consulting, LLC 37
    • Planning Poker is a Release Tool Strategic Tactical Daily Release Sprint Scrum Release Sprint Planning Planning Sprint Review Daily Scrum Sprint Retro © 2009 Trail Ridge Consulting, LLC 37
    • 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
    • Scrum Meeting Keys Focus Timebox Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 40
    • Scrum Meeting Keys Focus Timebox Strategic Tactical Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 40
    • Timebox WHY DO WE TIMEBOX? © 2009 Trail Ridge Consulting, LLC 41
    • Timeboxes drive focus, intensity, decisions, productivity... Waterfall Intensity Scrum Time © 2009 Trail Ridge Consulting, LLC 42
    • Timeboxes drive predictability Predictable Uncertain Unpredictable Sprint Sprint Sprint Sprint Sprint Sprint Sprint Sprint Project Timeline © 2009 Trail Ridge Consulting, LLC 43
    • Daily Scrum Timebox 15 Minutes! © 2009 Trail Ridge Consulting, LLC 44
    • Timebox All Meetings? Timeframe Daily Bi-weekly Quarterly Daily Sprint Sprint Sprint Release Scrum Retro Review Planning Planning Minutes 5 - 15 © 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 © 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 Meeting Keys Focus Timebox Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 47
    • Scrum Meeting Keys Focus Timebox Strategic Tactical Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 47
    • Visualize Color Size Time © 2009 Trail Ridge Consulting, LLC 48
    • Visualize Themes by Color © 2009 Trail Ridge Consulting, LLC 49
    • Visualize Types by Color © 2009 Trail Ridge Consulting, LLC 50
    • Visualize Role by Color © 2009 Trail Ridge Consulting, LLC 51
    • Visualize Size © 2009 Trail Ridge Consulting, LLC 52
    • Visualize Size © 2009 Trail Ridge Consulting, LLC 53
    • Visualize Time © 2009 Trail Ridge Consulting, LLC 54
    • Visualize Time © 2009 Trail Ridge Consulting, LLC 55
    • Scrum Meeting Keys Focus Timebox Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 56
    • Scrum Meeting Keys Focus Timebox Strategic Tactical Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 56
    • Does this look familiar? © 2009 Trail Ridge Consulting, LLC 57
    • Engage the Team? © 2009 Trail Ridge Consulting, LLC 58
    • 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
    • Engage the Team © 2009 Trail Ridge Consulting, LLC 61
    • Engage the Team © 2009 Trail Ridge Consulting, LLC 62
    • Engage the Team © 2009 Trail Ridge Consulting, LLC 63
    • Scrum teams work together © 2009 Trail Ridge Consulting, LLC 64
    • Scrum team share space © 2009 Trail Ridge Consulting, LLC 65
    • 5 Min Review Focus Timebox Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 66
    • 5 Min Review Focus Timebox Strategic Tactical Visualize Engage the Team © 2009 Trail Ridge Consulting, LLC 66
    • Revisiting Planning Poker © 2009 Trail Ridge Consulting, LLC 67
    • Is there a better way to engage the team? © 2009 Trail Ridge Consulting, LLC 68
    • Case Study: Salesforce.com © 2009 Trail Ridge Consulting, LLC 69
    • 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 Releases Last Waterfall Release Since March 2007 every agile release has been deployed on-time (down to the exact minute) © 2009 Trail Ridge Consulting, LLC 71
    • Salesforce.com 2006 vs. 2007 © 2009 Trail Ridge Consulting, LLC 72
    • 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
    • 5 Min Session Retrospective What will you take away? What did you miss?           © 2009 Trail Ridge Consulting, LLC 74