Downloaded 35 times
Uploaded byDigicomp Academy AG
Empiricism with scrum
The document discusses the application of empiricism within the Scrum framework, emphasizing the importance of addressing complexity and fostering adaptability in software development. It highlights the contrast between traditional waterfall methods and agile practices, advocating for Scrum's iterative approach to enhance project success rates. Key elements include roles, artifacts, and events that facilitate collaboration and responsiveness to changing requirements.
Empiricism with scrum
- 1. Empiricism with Scrum Ralph Jocham effective agile. ralph.jocham@effectiveagile.com
- 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
- 3. Plan Analyze Design Code Test Release 13-‐Nov-‐12 effective agile. 3
- 4. Work is organized by activity Plan Analyze Design Code Test Release è Big Batches 13-‐Nov-‐12 effective agile. 4
- 5. Big Batches Is this the right approach for software development? 13-‐Nov-‐12 effective agile. 5
- 6. Scientific Management Is this the righttr on ol an d C approachdfor software mm an Co development? 13-‐Nov-‐12 effective agile. 6
- 7. Scientific Management 13-‐Nov-‐12 effective agile. 7
- 8. Complexity Stacey Graph Cynefin Empirical Defined 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
- 9. Demming Cycle 13-‐Nov-‐12 effective agile. 9
- 10. 35% of RequirementsChange 25-‐Nov-‐2011 effective agile. 10
- 11. >60% of featuresare rarely or never used (source: Standish Group) 25-‐Nov-‐2011 effective agile. 11
- 12. Value Original SoluDon Welcoming change/ Coping with Complexity Spri nt n prin t n+1 S AddiDonal Value 2 Sprin Sprint t 11 Original Vision 13-‐Nov-‐12 effective agile. 12
- 13. 13-‐Nov-‐12 effective agile. 13
- 14. t 1970 Aug us 13-‐Nov-‐12 effective agile. 14
- 15. 13-‐Nov-‐12 effective agile. 15
- 16. Defined Waterfall (Defined)" Plan forthe 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
- 17. Defined Waterfall (Defined)" Plan forthe 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
- 18. Defined Waterfall (Defined)" Plan forthe 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
- 19. Defined vs Emperical Waterfall (Defined)" Plan for the entire Plan Analyze Design Code Test Release project up-front Scrum (Empirical)" Plan Plan Plan Plan Design Design Design Design Plan Plan a little for the Plan Plan Plan Plan Code Code Code Code entire project and then Test 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
- 20. Higher Chance ofSuccess 0.9 Probality of Success 0.5 Empirical Defined Edge of Chaos 0.1 Low Medium High Complexity (source: ADM) 13-‐Nov-‐12 effective agile. 20
- 21. Why a higherChange? Visibility Ability to Change Business Value Risk (source: ADM) Waterfall Scrum 13-‐Nov-‐12 effective agile. 21
- 22. A simple Definitionof 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
- 23. Framework Roles Artifacts 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
- 24. Roles, Artifacts andEvents in Action Review 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 DefiniDon Sprint Planning Backlog of Done Sprint Daily Scrum Sprint Review RetrospecDve ScrumMaster (source: ADM) 13-‐Nov-‐12 effective agile. 24
- 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
- 26. Cost of fixinga 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
- 27. Reporting 13-‐Nov-‐12 effective agile. 27
- 28. Reporting 13-‐Nov-‐12 effective agile. 28
- 29. Questions? hgp://www.scrum.org/Scrum-‐Guides 13-‐Nov-‐12 effective agile. 29
- 30. Ralph Jocham www.effecHveagile.com effective agile. ralph@effecDveagile.com @rjocham 25-‐Nov-‐2011 effective agile. 30