Scrum Guide

Scrum guide, agile, framework, project, product, management

Get Started. It's Free
or sign up with your email address
Rocket clouds
Scrum Guide by Mind Map: Scrum Guide

1. Theory

1.1. Transparency

1.2. Inspection

1.3. Adaptation

1.3.1. Sprint Planning

1.3.2. Daily Scrum

1.3.3. Sprint Review

1.3.4. Sprint Retrospective

2. Values

2.1. commitment

2.2. courage

2.3. focus

2.4. openness

2.5. respect

3. Team

3.1. Product Owner

3.1.1. Clearly expressing Product Backlog items;

3.1.2. Ordering the items in the Product Backlog to best achieve goals and missions;

3.1.3. Optimizing the value of the work the Development Team performs;

3.1.4. Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,

3.1.5. Ensuring the Development Team understands items in the Product Backlog to the level needed.

3.2. Development Team

3.2.1. 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;

3.2.2. Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment;

3.2.3. Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;

3.2.4. 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,

3.2.5. Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole

3.3. Scrum Master

3.3.1. Service to the Product Owner

3.3.1.1. Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;

3.3.1.2. Finding techniques for effective Product Backlog management;

3.3.1.3. Helping the Scrum Team understand the need for clear and concise Product Backlog items;

3.3.1.4. Understanding product planning in an empirical environment;

3.3.1.5. Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;

3.3.1.6. Understanding and practicing agility; and,

3.3.1.7. Facilitating Scrum events as requested or needed.

3.3.2. Service to the Development Team

3.3.2.1. Coaching the Development Team in self-organization and cross-functionality;

3.3.2.2. Helping the Development Team to create high-value products;

3.3.2.3. Removing impediments to the Development Team’s progress;

3.3.2.4. Facilitating Scrum events as requested or needed; and,

3.3.2.5. Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.

3.3.3. Service to the Organization

3.3.3.1. Leading and coaching the organization in its Scrum adoption;

3.3.3.2. Planning Scrum implementations within the organization;

3.3.3.3. Helping employees and stakeholders understand and enact Scrum and empirical product development;

3.3.3.4. Causing change that increases the productivity of the Scrum Team; and,

3.3.3.5. Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

4. Events

4.1. Sprint

4.1.1. No more than one-month of duration

4.1.2. No changes are made that would endanger the Sprint Goal;

4.1.3. Quality goals do not decrease; and,

4.1.4. Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

4.2. Sprint Planning

4.2.1. No more then eight hours for a one-month Sprint

4.2.2. What can be delivered in the Increment resulting from the upcoming Sprint?

4.2.3. How will the work needed to deliver the Increment be achieved?

4.3. Daily

4.4. Sprint Review

4.4.1. No most than a four-hour meeting for one-month Sprints

4.4.2. Attendees include the Scrum Team and key stakeholders invited by the Product Owner;

4.4.3. The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done";

4.4.4. The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;

4.4.5. The Development Team demonstrates the work that it has "Done" and answers questions about the Increment;

4.4.6. The Product Owner discusses the Product Backlog as it stands. He or she projects likely target and delivery dates based on progress to date (if needed);

4.4.7. The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;

4.4.8. Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,

4.4.9. Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.

4.5. Sprint Retrospective

4.5.1. No more than a three-hour meeting for one-month Sprints

4.5.2. Inspect how the last Sprint went with regards to people, relationships, process, and tools;

4.5.3. Identify and order the major items that went well and potential improvements; and,

4.5.4. Create a plan for implementing improvements to the way the Scrum Team does its work.

5. Artifacts

5.1. Product Backlog

5.2. Sprint Backlog

5.3. Increment

5.4. Artifact Transparency

5.5. Definition of Done

6. Definition

6.1. Lightweight

6.2. Simple to understand

6.3. Difficult to master