Scrum

Scrum

1. Is a process framework that has been used to manage complex product development since the early 1990s

   • You can employ various processes and techniques

2. Pillars

   • Transparency
     • Significant aspects of the process must be visible to those responsible for the outcome.
   • Inspection
     • Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work.
   • Adaptation
     • If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted.

3. The Scrum Team

   • Scrum master
     • is responsible for ensuring Scrum is understood and enacted
     • The Scrum Master serves the Product Owner
     • The Scrum Master serves the Development Team
     • The Scrum Master serves the organization
   • Development team
     • consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.
       • They are self-organizing
       • Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment
       • Scrum recognizes no titles for Development Team members other than Developer
       • Scrum recognizes no sub-teams in the Development Team
       • Individual Development Team members may have specialized skills and areas of focus
   • Product owner
     • Is responsible for maximizing the value of the product and the work of the Development Team.
     • The Product Owner is the sole person responsible for managing the Product Backlog.
       • Clearly expressing Product Backlog items
       • Ordering the items in the Product Backlog to best achieve goals and missions
       • Optimizing the value of the work the Development Team performs
       • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next
       • Ensuring the Development Team understands items in the Product Backlog to the level needed

4. Scrum Events

   • sprint
     • Sprint, is a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created
   • sprint planning meeting
     • The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.
   • Daily scrum
     • is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.
   • sprint review
     • is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed
   • sprint retrospective
     • is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint

5. Scrum Artifacts

   • product backlog
     • is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product
   • sprint backlog
     • is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal