Please enable JavaScript.

Coggle requires JavaScript to display documents.

SCRUM GUIDE - Coggle Diagram

- - - - Process + work must be visible to those performing + those receiving the work
      - Decision making based on perceived state of 3 artifacts: Product Backlog, Sprint Backlog, Increment
      - Transparency enables inspection
    - - Scrum artifacts + progress toward goals must be inspected frequently
      - Inspection in the form of 5 events
      - Inspection enables adaptation
    - - Need adaptation when a process deviate outside acceptable limits - or the resulting product is unacceptable
      - Need to adapt the moment anything new is learned thru inspection - People must be empowered and self-managing
- - - - Creating a plan for the Sprint, the Sprint Backlog
      - Adhering to a Definition of Done
      - Adapting their plan each day toward the Sprint Goal
      - Holding each other accountable
  - - - Developing and communicating the Product Goal
      - Creating and commuincating Product Backlog items
      - Ordering Product Backlog items
      - Ensuring the Product Backlog is transparent, visible and understood
  - - - Coach team members in self-management and cross-functionality
      - Help the ST focus on creating high-value Increments that meet the DoD
      - Remove impediments to the ST's progress
      - Ensure all Scrum events take place, positive, productive, within timebox
    - - Help find techniques for effective Product Goal definition and Product Backlog mgt
      - Help the ST understand the need for clear and concise Product Backlog items
      - Help establish empirical product planning for a complex environment
      - Facilitate stakeholder collaboration
    - - Lead, train, coach Scrum adoption
      - Plan, advise Scrum implementations within the org
      - Help employees and stakeholders understand and enact an empirical approach for complex work
      - Remove barriers between stakeholders and STs
- - - - No changes are made that would endanger the Sprint Goal
      - Quality does not decrease
      - Product Backlog is refined
      - Scope may be clarified and renegotiated with the PO as more is learned
  - - - Why is this Sprint valuable?
        
        PO propose how the product could increase its value in the current Sprint
        
        ST collaborates to define a Sprint Goal - must be finalized before the end of Sprint Planning
      - What can be Done this Sprint?
        
        Devs select items from the Product Backlog to include in the current Sprint - They can refine these items during this process
        
        Forecasting how much can be completed within a Sprint by using past performance data
      - How will the chosen work get done?
        
        For each PBI, the Devs plan the work to create an Increment that meets the DoD --> Decompose PBIs into smaller work of 1 day or less --> All decided by the Devs
- - - - The future state of the product, the target for the ST to plan against, long-term objective for the ST
      - Product Backlog defines what will fulfill the Product Goal
      - Product is a vehicle to deliver value:
        
        Can be a service, physical product, abstract product...
        
        Has clear boundary, known stakeholders, well-defined users/customers
      - ST must fulfill/abandon 1 objective before taking on the next
  - - - Single objective for the Sprint
      - Committed by Devs, but is flexible in terms of the exact work needed to achieve it
      - Create coherence and focus --> ST should work together, rather than on separate initiatives
      - Created during Sprint Planning --> Added to Sprint Backlog
      - Devs should keep Sprint Goal in mind during the Sprint
      - If the work is different from expected --> Negotiate the scope with PO without affecting Sprint Goal
  - - - Formal description of the state of the Increment when it meets the quality required for the product
      - Whenever a PBI meets DoD --> An Increment is born
      - Transparency - Shared understanding of what work was completed as part of the Increment
      - If PBI does not meet DoD --> Can't be released or presented at Sprint Reivew --> Returned to Product Backlog for future consideration
      - If DoD is organization standard --> Must follow as a minimum. If not --> the ST must create its own DoD
      - If multiple STs working together on a product --> All must define and comply with the same DoD