Please enable JavaScript.

Coggle requires JavaScript to display documents.

SCRUM Guide (Theory (Transparency, Inspection, Adaptation), Team (Product…

- - - - Clearly expressing Product Backlog items;
      - • Ordering the items in the Product Backlog to best achieve goals and missions;
      - • Optimizing the value of the work the Development Team performs;
      - • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
      - • Ensuring the Development Team understands items in the Product Backlog to the level needed
  - - - They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;
      - • Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment;
      - • Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;
      - • Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis; and,
      - • Individual Development Team members may have specialized skills and areas of focus, but
      - accountability belongs to the Development Team as a whole.
      - Individual Development Team members may have specialized skills and areas of focus, but
        accountability belongs to the Development Team as a whole.