Scrum Guide Vocabulary Flashcards

Comprehensive vocabulary flashcards covering the key terms, empirical pillars, values, roles, events, artifacts, and commitments defined in the 2020 Scrum Guide.

Scrum

A lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

Empiricism

A foundational theory of Scrum asserting that knowledge comes from experience and making decisions based on what is observed.

Lean Thinking

A foundational concept of Scrum that reduces waste and focuses on the essentials.

Transparency

An empirical Scrum pillar requiring that the emergent process and work must be visible to those performing the work as well as those receiving the work.

Inspection

An empirical Scrum pillar requiring Scrum artifacts and progress toward agreed goals to be inspected frequently and diligently to detect potentially undesirable variances or problems.

Adaptation

An empirical Scrum pillar requiring immediate adjustments to a process or product when deviations exceed acceptable limits or the product is unacceptable.

Scrum Values

Five fundamental values—Commitment, Focus, Openness, Respect, and Courage—that give direction to the Scrum Team regarding their work, actions, and behavior.

Scrum Team

A cohesive unit of professionals focused on one objective at a time (the Product Goal), consisting of one Scrum Master, one Product Owner, and Developers.

Developers

The people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint.

Product Owner

The Scrum Team role accountable for maximizing the value of the product resulting from the work of the Scrum Team and for effective Product Backlog management.

Scrum Master

The Scrum Team role accountable for establishing Scrum as defined in the Scrum Guide and for enabling the Scrum Team's effectiveness.

Sprint

A fixed-length event of one month or less that serves as a container for all other Scrum events, where ideas are turned into value.

Sprint Planning

A timeboxed event of a maximum of eight hours for a one-month Sprint that initiates the Sprint by laying out the work to be performed.

Daily Scrum

A 15-minute event for the Developers of the Scrum Team held at the same time and place every working day to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.

Sprint Review

A timeboxed event of a maximum of four hours for a one-month Sprint where the Scrum Team presents results to key stakeholders to inspect the outcome and determine future adaptations.

Sprint Retrospective

A timeboxed event of a maximum of three hours for a one-month Sprint that concludes the Sprint by reflecting on the last Sprint and planning ways to increase quality and effectiveness.

Product Backlog

An emergent, ordered list of what is needed to improve the product, serving as the single source of work undertaken by the Scrum Team.

Product Backlog Refinement

The ongoing activity of breaking down and further defining Product Backlog items into smaller, more precise items by adding details such as description, order, and size.

Product Goal

The commitment for the Product Backlog describing a future state of the product that serves as a long-term target for the Scrum Team.

Sprint Backlog

A highly visible plan created by and for the Developers composed of the Sprint Goal (why), selected Product Backlog items (what), and an actionable plan for delivering the Increment (how).

Sprint Goal

The commitment for the Sprint Backlog that serves as the single objective for the Sprint, providing flexibility regarding the exact work needed to achieve it.

Increment

A concrete, usable stepping stone toward the Product Goal that is additive to all prior Increments and thoroughly verified.

Definition of Done

The commitment for the Increment that formally describes the state of the Increment when it meets the quality measures required for the product.

What are the five SCRUM values?

Commitment, Focus, Openness, Respect, and Courage

How big are Scrum teams?

10 or fewer people

What is Scrum Team responsible for?

The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else
that might be required.

What are the Developers responsible for?

● Creating a plan for the Sprint, the Sprint Backlog;
● Instilling quality by adhering to a Definition of Done;
● Adapting their plan each day toward the Sprint Goal; and,
● Holding each other accountable as professionals

What is the Product Owner responsible for?

● Developing and explicitly communicating the Product Goal;
● Creating and clearly communicating Product Backlog items;
● Ordering Product Backlog items; and,
● Ensuring that the Product Backlog is transparent, visible and understood.

How does the Scrum Master serve the Scrum Team?

● Coaching the team members in self-management and cross-functionality;
● Helping the Scrum Team focus on creating high-value Increments that meet the Definition of
Done;
● Causing the removal of impediments to the Scrum Team’s progress; and,
● Ensuring that all Scrum events take place and are positive, productive, and kept within the
timebox.

How does Scrum Master serve the Product Owner?

● Helping find techniques for effective Product Goal definition and Product Backlog management;
● Helping the Scrum Team understand the need for clear and concise Product Backlog items;
● Helping establish empirical product planning for a complex environment; and,
● Facilitating stakeholder collaboration as requested or needed.

How does the Scrum Master serve the

How long are sprints?

A month or less. A new Sprint starts immediately at the end of the previous Sprint

What events happen within sprints?

Sprint Planning, Daily Scrums, Sprint
Review, and Sprint Retrospective

What questions do Sprint Planning address?

Why is this Sprint valuable?, What can be Done this Sprint?, How will the chosen work get done?

Each artifact has a commitment that enhances transparency. What are they?

Product Backlog: The Product Goal

Sprint Backlog: The Sprint Goal

Increment: The Definition of Done

Who does the Spring Backlog?

The Developers

Who does the Product Backlog?

The Scrum Team