Please enable JavaScript.

Coggle requires JavaScript to display documents.

Scrum - Coggle Diagram

- - - - Attendees
        
        The entire scrum team
        
        Certain managers
        
        Stakeholders
        
        Customers
        
        Other developers
      - Tips and tricks
        
        Ensure that any outside stakeholders know where they need to be, when. Get the room prepeed!
        
        The Production team should not feel like they're defending their work. Prep to ensure they're able to shine.
        
        Capture actionable feedback as items in the backlog
  - - - Tips and tricks
        
        Encourage the team to discuss and negotiate each item related to the sprint goal
        
        Ensure the product backlog has been ordered and completed by the Product Owner before Sprint Planning begins.
      - Attendees
        
        The entire scrum team
  - - - Attendees
        
        Scrum Master
        
        Production Team
        
        Product Owner (optional but recommended)
      - Tips and tricks
        
        Don't allow people to point fingers and play the blame game
        
        Create a safe space for people to provide their honest feedback.
        
        Use games and different questions to mix things up and reduce monotony.
        
        Make sure any actionable suggestion is captured, assigned, and tracked.
  - - - Attendees
        
        Scrum Master
        
        Production Team
        
        Product Owner
        
        Outside Stakeholders (optional)
      - Tips and tricks
        
        Be sure the team can see each other.
        
        Don't let this meeting turn into a verbal status report.
        
        Encourage team members to get together after the daily scrum to discuss any items that require additional conversation
        
        Do not let this meeting go longer than 15 minutes.
- - - - Is a master, ordered list of what is needed to improve the product.
      - Who owns this product backlog
        
        Product owner
        
        Product manager
      - It contains
        
        Feature
        
        Requirements
        
        Enhancements
        
        Fixes that constitute the changes to be made to the product in the future releases
    - - Is the long-term objectives
  - - - Scrum artifacts represent work or value
      - They provide metadata points that give insights into the performance of a sprint
      - There are 3 main scrum artifacts and commitment along with
        
        Product backlog
        
        Sprint backlog
        
        Increment
  - - - Is composed of Sprint Goal, the set of product backlog selected for the Sprint, as well as an actionable plan for delivering the Increment.
      - Is a plan by and for the Developers
    - - Is a single objectives for a sprint. It also creates
        
        Coherence
        
        Focus
        
        Encouraging the scrum team to work together rather than on separate initiatives.
      - Is created during the Sprint Planning event and then added to the sprint backlog
  - - - Is a concrete stepping stone toward the Product Goal. Each increment is additive to all prior increments and thoroughly verified, ensuring that all increments work together.
        
        At the end of a Sprint, the new Increment must be “done”, which means:
        
        It must meet the scrum team’s definition of “done”
        
        It must be in usable condition regardless of whether the Product Owner decides to actually release
    - - The Definition of Done is a formal description of the state of the Increment when it meets the quality measures for the product.
      - If a Product Backlog items does not meet the Definition of Done, it cannot be release or present in Sprint Review
      - The developers are required to conform to the Definition of Done.