SCRUM GUIDE

The Scrum Master serves the organization in several ways, including:

Leading and coaching the organization in its Scrum adoption; Planning Scrum implementations within the organization; Helping employees and stakeholders understand and enact Scrum and empirical product development; Causing change that increases the productivity of the Scrum Team; Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

The Product Owner is the sole person responsible for..

Managing the product backlog

During the Sprint:

No changes are made that would endanger the Sprint Goal; Quality goals do not decrease; Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned. Each Sprint may be considered a project with no more than a one-month horizon.

Development team size

Not less than 3, not more than 9

The Scrum Team consists of ...

Product Owner Development Team Scrum Master

Definition of scrum

Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum is: Lightweight Simple to understand Difficult to master

Development team characteristics

Scrum Teams are self-organizing and cross-functional The team model in Scrum is designed to optimize flexibility, creativity, and productivity. Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule; Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis; there are no exceptions to this rule; Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.

Scrum events

Sprint Planning Daily Scrum Sprint Review Sprint Retrospective

The Increment is..

The sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be "Done," which means it must be in useable condition and meet the Scrum Team's definition of "Done." It must be in useable condition regardless of whether the Product Owner decides to actually release it.

Sprint Planning answers the following:

What can be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved?

What questions should you ask yourself during a daily stand up ?

What did I do yesterday that helped the Development Team meet the Sprint Goal? What will I do today to help the Development Team meet the Sprint Goal? Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

Definition of "Done"

When a Product Backlog item or an Increment is described as "Done", everyone must understand what "Done" means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of "Done" for the Scrum Team and is used to assess when work is complete on the product Increment.

Scrum's artifacts represent

Work or value to provide transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that everybody has the same understanding of the artifact.

De 3 kernwaarden van SCRUM zijn:

1.Transparancy alles op tafel 2.Inspection kritisch kijken 3.Adaptation aanpassen waar nodig

The Daily Scrum is..

A 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.

The result of the Sprint Review is..

A revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.

The Sprint Retrospective is..

An opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches all to keep it within the time-box. The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process.

The Product Backlog is..

An ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering

The Sprint Review includes the following elements

Attendees include the Scrum Team and key stakeholders invited by the Product Owner; The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done"; The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; The Development Team demonstrates the work that it has "Done" and answers questions about the Increment; The Product Owner discusses the Product Backlog as it stands. He or she projects likely completion dates based on progress to date (if needed); The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning; Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.

Product Backlog management includes:

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 Ensuring the Development Team understands items in the Product Backlog to the level needed

The Scrum Master serves the Development Team in several ways, including:

Coaching the Development Team in self-organization and cross-functionality; Helping the Development Team to create high-value products; Removing impediments to the Development Team's progress; Facilitating Scrum events as requested or needed; Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.

The Scrum Master serves the Product Owner in several ways, including:

Finding techniques for effective Product Backlog management; Helping the Scrum Team understand the need for clear and concise Product Backlog items Understanding product planning in an empirical environment; Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value Understanding and practicing agility Facilitating Scrum events as requested or needed.

A Sprint Review is..

Held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.

The purpose of the Sprint Retrospective is to:

Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; Create a plan for implementing improvements to the way the Scrum Team does its work.