Scrum in Practice

437 views

Published on

Scrum in Practice. the art of the possible @ Wizard. Rowan Bunning. ESUG 2006, Prague

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
437
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Scrum in Practice

  1. 1. Scrum in Practice the art of the possible @ Wizard Rowan Bunning Wizard Information Services & Software WithStyle ESUG 2006 - Prague
  2. 2. Overview  Part A:  Scrum usage @ Wizard  Scrum+XP in a Nutshell  Part B:  15 minute sprint  Part C:  Selling Scrum  Challenges
  3. 3. Scrum Usage @ Wizard
  4. 4. Wizard Information Services  One of 5 Wizard businesses  Smalltalk for last 10 years  MAVIS - collection management system  Prestigious clients  User conference this month in Berlin  Transitioned from bespoke apps to products
  5. 5. Timeline 2003 2004 2005 2006 Scott Ambler @ Smalltalk Solutions EzyXML project - some Scrum practices Certified ScrumMaster project Used for non dev. activities WizDom2 project Scrum Mentor
  6. 6. Scrum Usage @ Wizard  All R&D / Product Development Projects  Internal Customer  Few fixed constraints  EzyXML - XML editor development  ACO - Community portal development  WizDom2 - Software Platform development  ICT&R - Management of IT contracting business  Wizard Power - Solar Power R&D  Tendering - Response preparation  QMS, Scrum - Methodology Documentation
  7. 7. Why Scrum is Succeeding  Championed by Executive Chairman  Positive re-enforcement  Business decision makers are empowered  Developers are empowered  No more BA/Architect - developer disconnect  Smalltalk is excellent for rapid development
  8. 8. Who else is Using Scrum?  Microsoft  .NET Platform Group  IBM  Google  Yahoo!  Federal Reserve Bank  IDX GE Healthcare: 330 people, 15 apps, 1 year  FDA- approved, life-critical software for x-rays, MRIs  Financial payment applications  24x7 with 99.99999% uptime requirements  Multi-terabyte database applications  Biotech projects  Oracle  Sun Microsystems  Siemens  SAP  Nokia  BBC
  9. 9. Scrum+XP in a Nutshell
  10. 10. Defined vs Empirical  Defined Process  Try to make reality follow an upfront plan  Empirical Process  Continually inspect and adapt to the emerging reality  “visibility, inspection & adaptation”
  11. 11. Slice it like Sushimi
  12. 12. Vertical slices - architecture User Interface Time Database Middleware Model 1 2 3 4 5 6 7 8
  13. 13. ...and all activities Testing Time Analysis Design Coding 1 2 3 4 5 6 7 8
  14. 14. Scrum Roles  Product Owner - vision, ROI, release  Represents customer, users  Makes prioritisation decisions  ScrumMaster - process facilitator  Promotes Scrum values  Removed impediments  Chairs meetings  Scrum Team - analysis, design, development, testing  Multi-disciplinary  5 - 10 individuals  Self-organising
  15. 15. Scrum + XP Business Focus Prioritised Requirements Management controls Progress tracking Decision-making boundaries Pair Programming Refactoring TDD Continuous Integration Iteration planning Daily stand-up meetings Customer always available Frequent small releases Velocity is measured Project Management Software Development XPScrum
  16. 16. Customisations at Wizard  2 week sprints  2 - 4 hours total of review and planning meetings  Retrospectives integrated into review  Task allocation often left open  Testing on Development server - bugs reports from tool  Transition to QA server - formal change tracking
  17. 17. Sprint Role play
  18. 18. Role play Outline 1. Sprint Review 2. Sprint Planning 3. Test Creation 4. Develop Implementation 5. Clarification 6. Sprint Review
  19. 19. Backlog  Requirement: “Reduce repetitive moderation tasks.”  Task: “Select feature Groups randomly.”
  20. 20. Role play Outline 1. Sprint Review 2. Sprint Planning 3. Test Creation 4. Develop Implementation 5. Clarification 6. Sprint Review
  21. 21. Pitching Scrum
  22. 22. Avoid Unused Features Seldom or never used: 64% Always or often used: 20% Always 7% Often 13% Sometimes 16% Seldom 19% Never 45% Source: The Standish Group CHAOS'2000 Survey
  23. 23. Avoid Critical Risk Impact at end of Project Requirements Analysis Design Implement Integrate & System Test Potential Impact of Risks being tackled Time Highest risk activities such as integration, system testing, load testing are tackled late - Craig Larman First build and deliver
  24. 24. Reduce Risk Early Potential Impact of Risks being tackled Time All activities are tackled early Iterations First build and deliver Analysis Design Implement Integrate & System Test Analysis Design Implement Integrate & System Test Analysis Design Implement Integrate & System Test Analysis Design Implement Integrate & System Test Analysis Design Implement Integrate & System Test - Craig Larman
  25. 25. Keep Cost of Change Flat Cost of change % Complete Traditional development process Agile software engineering practices
  26. 26. Take on Complexity... and Win!
  27. 27. Releasable software after every iteration Planning is poorly informed TestingDevelopment Release deadline Release Develop then Test Test as you develop Time saved
  28. 28. Other Key Advantages  Efficiency  Flexibility  Openness and Inclusive input  Customer control  Business value driven  Conceptual integrity  Built-in Risk Management  Early risk identification and mitigation  Control measures & frequent control points  Early partial product
  29. 29. Challenges
  30. 30. Challenges  Organisational:  Organisational boundaries  Reliance on external resources  Conceptual:  Sashimi - thinking in vertical slices  Discipline:  Comprehensive test coverage  TDD  Integration with other practices  Traceability
  31. 31. Join us in the Scrum!
  32. 32. Questions?  Resources  www.scrumalliance.org  www.controlchaos.com  www.mountaingoatsoftware.com

×