Scrum Master Practice Flashcards

Vocabulary flashcards based on Scrum Master exam prep questions and answers, covering accountabilities, events, artifacts, and core theories.

Empiricism

The foundation of the Scrum framework along with Lean Thinking; it asserts that knowledge comes from experience and making decisions based on what is observed.

The Three Pillars of Empiricism

Transparency, Inspection, and Adaptation.

Scrum Values

Commitment, Focus, Openness, Respect, and Courage.

Scrum Team

The fundamental unit of Scrum; a small, cross-functional and self-managing team consisting of one Scrum Master, one Product Owner, and Developers.

Cross-functional Team

A team whose members have all the skills necessary to create value each Sprint.

Self-managing Team

A team that internally decides who does what, when, and how.

Scrum Team Size

Typically $10$ or fewer people.

Developers

The people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint and managing the progress toward the Sprint Goal.

Product Owner

A single person accountable for maximizing the value of the product and for effective Product Backlog management.

Scrum Master

Accountable for the Scrum Team's effectiveness and for establishing Scrum as defined in the Scrum Guide; a true leader who serves the Scrum Team and the larger organization.

Sprint

A fixed-length event of one month or less that serves as a container for all other events and is used to create a Done Increment.

Sprint Planning

An event that initiates the Sprint by laying out the work to be performed, addressing why the Sprint is valuable, what can be done, and how it will be done.

Daily Scrum

A $15$-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.

Sprint Review

An event held at the end of the Sprint to inspect the outcome of the Sprint and determine future adaptations; it has a timebox of $4$ hours for a one-month Sprint.

Sprint Retrospective

The final event of the Sprint where the Scrum Team inspects itself and plans improvements to increase its quality and effectiveness; timeboxed to $3$ hours for a one-month Sprint.

Product Backlog

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

Sprint Backlog

Composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how).

Increment

A concrete stepping stone toward the Product Goal, representing the sum of all Product Backlog items completed during a Sprint and all previous Sprints.

Product Goal

The commitment for the Product Backlog; it describes a future state of the product which can serve as a target for the Scrum Team to plan against.

Sprint Goal

The commitment for the Sprint Backlog; the single objective for the Sprint that provides guidance to the Developers on why they are building the Increment.

Definition of Done

The commitment for the Increment; a formal description of the state of the Increment when it meets the quality measures required for the product.

Product Backlog Refinement

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

Cone of Uncertainty

A tool used to shed light on how much is known about the product over time and the evolution of the amount of uncertainty.

Burndown Chart

A tool used to visualize the progress of work by showing how much work remains until the end of the Sprint.

Impediment Removal

A primary responsibility of the Scrum Master to cause the removal of obstacles that hinder the Scrum Team's progress.

Sprint Cancellation Authority

Only the Product Owner has the authority to cancel a Sprint, which happens if the Sprint Goal becomes obsolete.