Please enable JavaScript.

Coggle requires JavaScript to display documents.

Scrum (Scrum Theory :star: (Adaptation. If any aspects of a process…

- - - - During the Sprint:
        
        No changes are made that would endanger the Sprint Goal
        
        Quality does not decrease
        
        The product backlog refined as needed, and
        
        Scope may be clarified and renegotiated with the Product Owner as more is learned.
        
        When a Sprint's horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase.
        Each Sprint may be considered a short project.
        To forecast progress can be used burn-downs, burn-ups, or cumulative flows.
        
        Daily Scrum
        The purpose of the Daily scrum is to inspect progress toward the Sprint Goal and adapt Sprint backlog as necessary, adjusting the upcoming planned work.
        Timeboxed - 15 min.
        If the PO and SM are actively working on items in the Sprint Backlog they participate as Developers to the Daily Scrum.
        The Developers can select whatever structure and technique they want.
        Daily Scrum improve communications, identify impediments, promote quick decision making and eliminate the need for other meetings.
        
        Sprint Review
        The purpose of the Sprint Review is to inspect the outcome and determine future adaptations. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and Scrum Team should avoid limiting it to a presentation.
        
        Sprint Retrospective
        The purpose is to plan ways to increase quality and effectiveness.
        The Scrum Team inspect how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.
        The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint**.
        Timeboxed max 3 hours.
        
        Sprint Planning
        This resulting plan is created by the collaborative work of the entire Scrum Team.
        The PO ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal.
        The Scrum Team may also invite other people to provide advice.
        Sprint Planning addresses the following topics:
        1. **The PO proposes how the product could increase its value and utility in the current Sprint. The whole Scrum team collaborate to define a Sprint Goal. The Sprint Goal must be finalized prior to the end of Sprint Planning**.
        2. Through discussion with the PO, the Developers select items from the Product Backlog to include in the current Sprint. The scrum Team may refine these items during this process.
        The more the Developers know about their past performance, their upcoming capacity and their definition of done, the more confident they will be in their Sprint forecasts.
        
        For each selected Product Backlog items developers plan the work to create an Increment. This process is at the sole discretion of the Developers.
        Sprint Backlog contains: The Sprint Goal, the Product Backlog items and the plan.
        Timeboxed - max 8 hours.
- - - - The Sprint Backlog is composed of the Sprint Goal, set of Product Backlog items an actionable plan for delivering the Increment. The Sprint Backlog is a plan by and for the Developers. It is a work that Developers plan to accomplish during the Sprint.
        The Sprint Backlog is updated throughout the Sprint as more is learned.
        
        Commitment: Sprint Goal
        The Sprint Goal is the single objective for the Sprint. The Sprint Goal also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives.
        The Sprint Goal created during Sprint planning and then added to the Sprint Backlog.
        If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint without affecting the Sprint Goal.
    - - The Product Backlog is an emergent, ordered list of what is needed to improve product. It is the single source of work undertaken by the Scrum Team.
        Sprint Backlog items selects after refining activities. This is an ongoing activity to add details, such as description, order and size. Developers responsible for sizing.
        PO may influence the Developers by helping them understand and select trade-offs.
        
        Commitment: Product Goal
        The Product Goal describes a future state of the product which can serve as a target. The Product Goal is in the Product Backlog.
        A product is a vehicle to deliver value.
        The Product Goal is a long term objective for the Scrum team. They must fulfill (or abandon) one objective before taking on the next.
    - - An increment is a concrete stepping stone toward the Product Goal. Each increment additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. The Increment must be usable.
        Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review. However, an Increment may be delivered to the stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.
        Work cannot be considered part of an Increment unless it meets the Definition of Done.
        
        Commitment: Definition of Done
        The moment a Product Backlog item meets the Definition of Done, an Increment is born.
        If a Product Backlog item does not meet the Definition of Done it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product backlog to future consideration.
        Definition of Done may be organizational standard, if not the Scrum Team must create a Definition of Done.
        The Developers required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same DoD.