A CIO's Playbook for Adopting the Scrum Method of ... - Rally Software

More documents

Recommendations

Info

Appendix C - Scrum MetricsTable 1 – Scrum Process Metrics (Hartmann, Stallings)Project:Scoring (0-5) Sprint 1 Sprint 21. Product OwnerProduct Backlog developed owned and managed by Product OwnerProduct Owner process is flexible; collaboration with team is ongoingProduct Owner and stake-holder participation at Sprint ReviewProduct Owner manages project by valueTotal "Product Owner" Score2. PlanningProduct Backlog is descriptive, prioritized and has effective estimatesTeam develops and manages Sprint BacklogTeam involves stakeholders and dependencies in effective mannerProject progress can be tracked by backlog BurnDown and value burnupSustainable paceTotal "Planning" Score3. ScheduleSprint Planning regular, on time, fully attendedSprint Review regular, on time, fully attendedDaily Scrum occurs on time, is fully attendedTeam meets its commitments to SprintTotal "Schedule" Score4. ProcessTeam self-polices and reinforces use of process and rulesOrganization is able to comply with Scrum rulesScrumMaster is effective in getting process followedTeam is self-managingSurprises don't occurTeam is cross-functionalTeam and Product Owner collaborate and work closely togetherTeam works to improve itself and its processesTeam adequately manages dependenciesTotal "Process" Score© 2005 Rally Software Development Corp., Ken Schwaber and ScrumAlliance 26
Project:Scoring (0-5) Sprint 1 Sprint 25. TeamTeam members are dedicated and honor commitmentsTeam effectively acts upon indicators in Sprint BurndownCommunications between team members is effectiveTeam effectively manages conflict within teamTeam improves internal development processesTotal "Team" Score6. ReportingProduct Backlog is effectively maintained and communicatedSprint Backlog is effectively maintained and communicatedProject and Sprint reporting are effective and understoodValue is used to manage Product BacklogTotal "Reporting" Score7. Engineering Practices/InfrastructureAt least daily buildCommon source code libraryMetric for quality of incrementIncrement metric metTest driven development practicesRefactoring practicesDesign review practicesCode review practicesCoding standardsAutomated unit test harnessAutomated acceptance test harnessTotal "Engineering" Score© 2005 Rally Software Development Corp., Ken Schwaber and ScrumAlliance 27
Page 1 and 2: Rally Software Development Corporat
Page 3 and 4: IntroductionThe pressures of a trul
Page 5 and 6: Scrum PrinciplesWhile those are som
Page 7 and 8: Scrum and Software AgilityScrum has
Page 9 and 10: The Organizational ScrumMaster peri
Page 11 and 12: Establish MetricsDescription: Revie
Page 13 and 14: Description: Organizational change
Page 15 and 16: Organizational Impediments to Adopt
Page 17 and 18: Scaling ScrumThe business benefits
Page 19 and 20: Tooling Infrastructure for Enterpri
Page 21 and 22: Evolving the Infrastructure in Spri
Page 23 and 24: BibliographyAgile Manifesto: www.ag
Page 25: Appendix B - The Agile ManifestoIn

A CIO's Playbook for Adopting the Scrum Method of ... - Rally Software

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?