SCRUM Guide Fragen

1. Research and identify
2. Develop products and enhancements
3. Release products and enhancements
4. Develop and sustain Cloud an oderh operational environements for product
5. Sustain and renew products

1. Transparency
2. Inspection
3. Adaptation

1. Sprint Planning
2. Daily Scrum
3. Sprint Review
4. Spring Retrospective

Significant aspects of the process must be visible to those responsible for the outcome. Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen.

Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.

If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted.

• Commitment
• Courage
• Focus
• Openness
• Respect

• Product Owner
• Development Team
• Scrum Master

• ... maximizing the value of the product resulting from work of the Development Team.
• ... the sole person responsible for managing the Product Backlog.

• 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.

The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.

• 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.

• Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint.
• Fewer than three Development Team members decrease interaction and results in smaller productivity gains. S
• maller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment
• Not more than nine members

The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.