Please enable JavaScript.

Coggle requires JavaScript to display documents.

Scrum - Coggle Diagram

- - - - 1 month or less
  - - - Sprint Goal
        
        Identify prior to Sprint Planning
      - What can be done in this Sprint
        
        Developers select PBI for Sprint Backlog
      - How will the chosen work get done ?
        
        Developers plan the work --> create increment that meets DOD
    - - 8h/1 tháng
  - - - 15p daily
    - - Tracking progress
      - Adjust plan to meet Sprint's goal
    - - Developers
    - - What did I do yesterday ?
      - What am I going to do today ?
      - Is there any struggle ?
  - - - End of the Sprint, 4-hour lasting
    - - check Increment
      - determine future adaptation in PBI
      - receive feedback from stakeholders
    - - Scrum Team
      - Stakeholders
  - - - 3 hours or less
- - - - based on experience and make decision based on what is observed
    - - reduce waste, focus on the essentials
  - - - work & process are visible for those performing or receiving
      - E.g. Product Backlog is public on Jira/Trello
    - - Frequently tracking progress & commitment
      - E.g. In Sprint Review, stakeholder is presented 'Checkout order' function
    - - Make adjustments when changes needed
      - E.g. After review, stakeholder notices that the product hasn't has payment checkout function, Scrum Team will discuss then come up with adjustment.
- - - - List of work items need to be done to develop product
    - - Product Owner
    - - Frequently change, refinement
    - - Product Goal
  - - - Set of chosen PBIs for a Sprint
    - - Developers
    - - Sprint Goal
  - - - Developers