Introduction to Scrum

This is an introductory overview of the Scrum Framework based on the Scrum Guide.

These charts are also the basis for the corresponding presentation available at the Enduring Agile channel on youtube, accessible using the link provided below:

https://youtu.be/eAZyChHY4Jo

1. Introduction to Scrum

2. What, Why and How

3. Predictive Approach ”Waterfall” project work is completed in phases of maturation Concept -> Design -> Build -> Deliver -> Support ”Waterfall” is a predictive process Works only when “one can establish a complete vision, define all of the requirements of the vision, and then devise the detailed plan to turn the requirements into the vision” Depends on the “accuracy of the project plan and its unswerving execution” Ref: Software In 30 Days by Ken Schwaber and Jeff Sutherland

4. Empirical approach Ref: ScrumInc Maximize Visibility, Inspect Frequently, Welcome Change Scrum Pillars

5. Scrum Values Commitment, Focus, Openness, Respect, and Courage The Scrum Team commits to achieving its goals and to supporting each other. Their primary focus is on the work of the Sprint to make the best possible progress toward these goals. The Scrum Team and its stakeholders are open about the work and the challenges. Scrum Team members respect each other to be capable, independent people, and are respected as such by the people with whom they work. The Scrum Team members have the courage to do the right thing, to work on tough problems. Ref: The 2020 Scrum Guide

6. https://s3.amazonaws.com/ scrumorg -website-prod/ drupal /2016-06/ScrumFramework_17x11.pdf

7. Scrum Framework Scrum is a simple, lightweight framework Roles Scrum Master, Product Owner, Developers The “Scrum Team” consists of members with all three roles Artifacts Increment, Product Backlog and Sprint Backlog Events Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective “Scrum is built upon by the collective intelligence of the people using it.” The 2020 Scrum Guide

8. Scrum Roles

9. Scrum Artifacts

10. The Product Goal

11. The Sprint Goal

12. Definition of Done

13. Definition of a Done Increment Transparency of the increment means that everyone equally has a shared definition and understanding of a done increment “A done, completed increment is something you can use” The capability resulting from an increment should be immediately deployable for use The Product Owner should not accept incomplete sprints Partially completed functionality that is accepted is built upon in subsequent iterations Technical debt accumulates as work is done Technical debt is more expensive to fix when it is built upon by subsequent functionality Ref: Software In 30 Days by Ken Schwaber and Jeff Sutherland

14. Scrum Events

15. The Sprint Contains all other Scrum Events Sprint Planning, Daily Scrums, Sprint Review and Sprint Retrospective Fixed length iteration A new Sprint starts immediately after the conclusion of the previous Sprint Creates the product value committed to during planning Scope can be clarified and renegotiated with the Product Owner as more is learned No changes are made that would endanger the Sprint Goal Timebox: Fixed length, 1 month of less

16. Sprint Planning Initiates the sprint by planning out the work to be performed Results in a defined Sprint Goal and a Sprint Backlog (the plan) Involves the entire Scrum Team Why is the Sprint valuable? Define the Sprint Goal What can be Done in the Sprint? Estimate work in detail and use capacity based on past performance Work in priority order until capacity is met How will the chosen work get done? Break down work into detailed tasks required complete work Timebox: A maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

17. The Daily Scrum Team meets daily to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed Produces an actionable plan for the next day of work The format of the meeting and techniques utilized are determined by the team Timebox: 15 Minutes

18. Sprint Review At the end of the Sprint, the Scrum Team and key stakeholders meet to review what happened during the sprint and the increment of functionality that was produced What was done, how much was done, how effectively it was done and the usefulness of the work New requirements, opportunities and challenges can arise during the Sprint Review Timebox: Maximum of 4 hours for a 1-month sprint. For shorter Sprints, the vent is usually shorter.

19. Sprint Retrospective At the end of the Sprint, the Scrum Team meets to formulate improvements based on what happed during the sprint Suggested topics: How well or poorly did the team members work together and why Did the team achieve more or less than forecast and why Whether the team has all the skills needed to do its job What the team thinks of using Scrum The team identifies the most helpful changes to improve its effectiveness Address the most impactful changes as soon as possible Even as soon as the next Sprint Timebox: Maximum of 3 hours for a 1-month Sprint. For shorter Sprints, the event is usually shorter.

20. References The 2020 Scrum Guide ( Scrum.org / Scruminc ) Alternate Release Burdown Chart (Mountain Goat Software) Project Management Metrics ( Attlassian ) Software In 30 Days by Ken Schwaber and Jeff Sutherland Charts by James Walmsley CSM, PSM I, PSK I www.linkedin.com /in/ jameswalmsleycsm