Empiricism with scrum

  • Published on
    20-Aug-2015

  • View
    1.081

  • Download
    0

Embed Size (px)

Transcript

<ol><li> 1. Empiricism with ScrumRalph Jochameffective agile. ralph.jocham@effectiveagile.com </li><li> 2. Ralph Jocham Started as programmer; discovered process as a problem early on First Unified Process with UML Agile since 2000 with XP Scrum in 2003 Oracle, LinkedIn, Roche, Google, The Gap, Swisscom, Texas Instruments, Siemens Medical, ThoughtWorks, JPMorganChase Did come around, different cultures and domains Founder of effective agile. Trainer with Scrum.org </li><li> 3. Plan Analyze Design Code Test Release 13-Nov-12 effective agile. 3 </li><li> 4. Work is organizedby activityPlan Analyze Design Code Test Release Big Batches13-Nov-12 effective agile. 4 </li><li> 5. Big BatchesIs this the rightapproach for software development?13-Nov-12 effective agile. 5 </li><li> 6. Scientific Management Is this the righttron ol an d C approachdfor softwaremmanCo development?13-Nov-12 effective agile. 6 </li><li> 7. Scientific Management13-Nov-12 effective agile. 7 </li><li> 8. Complexity Stacey Graph Cynen EmpiricalDened far from agreement Complex Complicated Chaos Probe Sense Sense Analyze Respond Requirements Respond Complex Emergent Good PracDces Chaos Simple Act Sense Sense Categorize agreement Respond Respond Simple Complicated close to Novel Best PracDces close to certainty Technology far from certainty (source: Dave Snowden, IBM) (source: Ralph Stacey, University of Herfordshire) 13-Nov-12 effective agile.8 </li><li> 9. Demming Cycle13-Nov-12 effective agile. 9 </li><li> 10. 35% of Requirements Change25-Nov-2011 effective agile. 10 </li><li> 11. &gt;60% of features are rarely or never used (source: Standish Group) 25-Nov-2011 effective agile. 11 </li><li> 12. Value Original SoluDon Welcoming change/ Coping with Complexity Sprint nprin t n+1 S AddiDonal Value 2 Sprin Sprint t 11 Original Vision 13-Nov-12 effective agile. 12 </li><li> 13. 13-Nov-12 effective agile. 13 </li><li> 14. t 1970 Aug us13-Nov-12 effective agile. 14 </li><li> 15. 13-Nov-12 effective agile. 15 </li><li> 16. DefinedWaterfall (Dened)"Plan for the entire Plan Analyze Design Code Test Release project up-front JSP-188 V-Model GAM-T-17 Hermes MIL-STD-2167A 13-Nov-12 effective agile.16 </li><li> 17. DefinedWaterfall (Dened)"Plan for the entire Plan Analyze Design Code Test Release project up-front JSP-188 V-Model GAM-T-17 Hermes MIL-STD-2167A 13-Nov-12 effective agile.17 </li><li> 18. DefinedWaterfall (Dened)"Plan for the entire Plan Analyze Design Code Test Release project up-front JSP-188 V-Model GAM-T-17 Hermes MIL-STD-498 13-Nov-12 effective agile.18 </li><li> 19. Defined vs Emperical Waterfall (Dened)" Plan for the entirePlan Analyze Design Code Test Release project up-front Scrum (Empirical)"Plan Plan Plan Plan Design Design Design Design Plan Plan a little for thePlan Plan Plan Plan Code Code Code Code entire project and thenTest Test Test Test a little for each Sprint" Release Release Release Release intern intern intern (source: ADM) extern extern extern 13-Nov-12 effective agile.19 </li><li> 20. Higher Chance of Success 0.9 Probality of Success 0.5 Empirical Dened Edge of Chaos 0.1 Low Medium High Complexity (source: ADM) 13-Nov-12 effective agile. 20 </li><li> 21. Why a higher Change?Visibility Ability to Change Business Value Risk (source: ADM) Waterfall Scrum 13-Nov-12 effective agile. 21 </li><li> 22. A simple Definition of Scrum Scrum (n): A framework within which people can address complex problems, and producDvely and creaDvely develop products of the highest possible value. (source: ADM) 13-Nov-12 effective agile.22 </li><li> 23. FrameworkRolesArtifacts Events Product Owner Increment Sprint Dev Team Product Sprint Planning Scrum Master Backlog Daily Scrum Sprint Backlog Sprint Review Retrospective(source: ADM) 13-Nov-12 effective agile. 23 </li><li> 24. Roles, Artifacts and Events in ActionReview PotenDally Roles Releasable Product Owner Development Team Scrum Master RetrospecDve Increment Daily ArDfacts Scrum Product Backlog Sprint Backlog Sprint Increment Sprint Sprint Backlog Planning MeeDng Events Product DeniDon Sprint Planning Backlog of Done Sprint Daily Scrum Sprint Review RetrospecDve ScrumMaster (source: ADM) 13-Nov-12 effective agile.24 </li><li> 25. 100% 50% 40% Planning Analysis Design Design Dev TesDng Dev Release Release TesDng Release Major Release Planning Analysis Design Dev Dev TesDng Release Major Release 100% Planning Analysis Design Dev TesDng Release Major Release Planning Analysis Design Dev TesDng Release Major Release Point Release Point Release V1 V1.5 Point Point Release Release V4 V4.2 FuncDonal Release FR FR FR FR Stop FR FR FR FR FR V1 2012 Ralph Jocham effective agile.www.effectiveagile.com </li><li> 26. Cost of fixing a Bug ConstrucDon Detailed Design Architecture Requirements Requirements Architecture Requirements Detailed Design Architecture Detailed Design ConstrucDon ConstrucDon (source: Barry Boehm) Maintenance 25-Nov-2011 effective agile.26 </li><li> 27. Reporting13-Nov-12 effective agile. 27 </li><li> 28. Reporting13-Nov-12 effective agile. 28 </li><li> 29. Questions? hgp://www.scrum.org/Scrum-Guides 13-Nov-12 effective agile. 29 </li><li> 30. Ralph Jocham www.eecHveagile.com effective agile.ralph@eecDveagile.com @rjocham 25-Nov-2011 effective agile.30</li></ol>