Scrum

Scrum

1. Uses

   • Research and identify viable markets, technologies, and product capabilities;
     • Develop products and enhancements
       • Release products and enhancements, as frequently as many times per day;
         • Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use
           • Sustain and renew products

2. What is?

   • Is a framework for developing, delivering, and sustaining complex products.
     • Lightweight Simple to understand Difficult to master

3. Theory

   • Empiricism
     • Pilars:
       • Tranpsarency
         • What is?
           • Significant aspects of the process must be visible to those responsible for the outcome.
       • Inspection
         • What is?
           • Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.
       • Adaptation
         • What is?
           • Adjust the process if the process is outside acceptable limits
     • What is?
       • asserts that knowledge comes from experience and making decisions based on what is known.

4. Values

   • Commitment, courage, focus, openness and respect

5. Team

   • What is?
     • The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
   • Product Owner
     • The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.
     • Development team
       • The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.
       • Scrum Master
         • Is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.

6. Events

   • What is?
     • All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened.
   • Sprint
     • A time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.
       • Goal
         • Is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog.
   • Sprint Planing
     • 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. Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.
     • Daily Sprint
       • The Daily Scrum is a 15 - minute time - boxed event for the Development Team . The Daily Scrum is held every day of the Sprint.. the Development Team plans work for the next 24 hours to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.
   • Sprint Review
     • A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed .the Scrum Team and stakeholders collaborate about what was done in the Sprint.. This is a t most a four - hour meeting for one - month Sprints.
     • Sprint Restrospective
       • Is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is at most a three - hour meeting for one - month Sprints.

7. Product Backlog

   • Product Backlog The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. A Product Backlog is never complete.
   • 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 . The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done”” Increment .