Agile Deveopment-with-Scrum for CapitalCamp DC


Published on

Manager of Technical Delivery Shannon Lucas gave this overview of Scrum methodology for CapitalCamp DC.

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Agile Deveopment-with-Scrum for CapitalCamp DC

  1. 1. Agile Development with Scrum<br />Shannon Lucas<br />July 22nd, 2011<br />
  2. 2. Outline<br />What is Scrum?<br />The Scrum Team<br />Scrum Events<br />Scrum Artifacts<br />UX & Testing<br />Organizational Impacts<br />Selling Scrum<br />
  3. 3. What is Scrum?<br />
  4. 4.
  5. 5. Scrum framework<br />Founded on empirical process control theory<br />Intentionally incomplete<br />Iterative & incremental<br />Outwardly facing & transparent<br />Requires a definition of “done”<br />Adapts to changing requirements<br />
  6. 6. The Scrum Team<br />
  7. 7. The Scrum Team<br />Scrum Master<br />Business owner<br />Product Owner<br />Scrum Team<br />Stakeholders<br />
  8. 8. Product Owner<br />Manages the Product Backlog and ensures business value of the Team’s work<br />Represents stakeholder interests to the team<br />Plans product releases and maintains product roadmap<br />One person, not a committee<br />Ultimately responsible for product’s success<br />
  9. 9. Scrum Master<br />Serves as coach, fixer, and gatekeeper<br />A leadership role rather than managerial<br />Plans individual Sprints with Team<br />Facilitates all of the Scrum events<br />Manages relationship between Product Owner and rest of team<br />
  10. 10. The Development Team<br />Cross-functional group of 5 to 9 people<br />Self-organizing & continuously improving<br />Team determines how to transform Product Backlog into shippable functionality<br />Accountability belongs to Team as a whole<br />No domain-specific sub-teams<br />
  11. 11. Scrum Events<br />
  12. 12. Sprints<br />24 Hours<br />Daily Scrum meeting<br />14 Days<br />Sprint Backlog<br />Expanded tasks<br />Potentially shippable product increment<br />Product Backlog<br />
  13. 13. Sprints<br />Consistent duration throughout project<br />Team composition and quality goals remain constant<br />No changes made that affect Sprint Goal<br />Scope can be clarified or re-negotiated as more is learned<br />Risk is limited to cost of one sprint<br />
  14. 14. Sprint Planning Meeting<br />Time-boxed meeting to determine work to be done in a Sprint<br />First event of every Sprint<br />Answers “What will be delivered in this Sprint?”<br />Answers “How will the work be achieved?”<br />
  15. 15. Daily Scrum<br />Daily 15 minute (max) meeting<br />Each team member answers three questions:<br /> - What has been accomplished since last meeting?<br /> - What will be done before the next meeting?<br />- What obstacles are in the way?<br />Not a status meeting<br />Only Development Team can participate<br />
  16. 16. Sprint Review<br />Development Team demonstrates work done in the Sprint<br />Product Owner determines what has been “Done” or not “Done”<br />Results in a revised Product Backlog<br />Informs planning for the next Sprint<br />
  17. 17. Sprint Retrospective<br />Final activity of every Sprint<br />Team reflects on the Sprint in terms of people, relationships, process, and tools<br />Identify what went well and where improvements are needed. <br />Team plans how to implement improvements<br />
  18. 18. Scrum Artifacts<br />
  19. 19. Product Backlog<br />Single source of requirements and changes to the product<br />Ordered by unique priority<br />Never complete<br />Dynamic and changes as needed responding to changing business needs<br />Anyone involved can contribute to it<br />
  20. 20. Product Backlog<br />Highest priority items have the most detail<br />Detail on lower priority items deferred until it’s needed <br />
  21. 21. Sprint Backlog<br />Set of Backlog items that the Team commits to delivering in the Sprint<br />Serves as a real-time picture of how work is progressing<br />Belongs solely to the Development Team<br />
  22. 22. Definition of “Done”<br />A shared understanding of what it means when work is considered done<br />Defined at the beginning of the project<br />Applies globally to the project<br />Might include things such as:<br /> - Unit & functional tests<br /> - Documentation<br />
  23. 23. User Experience & Testing<br />
  24. 24. User Experience Tasks<br />UX tasks happen slightly ahead of programming tasks<br />UX expertise stays involved<br />No big handoffs<br />
  25. 25. Testing<br />No distinct testing phase<br />Features are tested as they are completed, during the Sprint they are developed in<br />
  26. 26. Organizational Impacts<br />
  27. 27. Organizational Impacts<br />Transitioning to Scrum isn’t always easy<br />Traditional roles change<br />Cultural changes<br />Commitment to continuous improvement.<br />
  28. 28. Selling Scrum<br />
  29. 29. Selling Scrum<br />Clients may perceive fixed-bid contracts as less risky<br />Target-scope & target-cost models<br />Limiting client exposure to the internal process<br />
  30. 30. Who uses Scrum?<br />
  31. 31. Questions?<br />
  32. 32. Thank you!<br />
  33. 33. Resources<br /> -<br />Scrum Alliance -<br />All Things Product Owner -<br />Agile Project Management with Scrum by Ken Schwaber<br />Succeeding with Agile: Software Development Using Scrum by Mike Cohn<br />A Practical Guide to Distributed Scrum by Elizabeth Woodward<br />