Certified ScrumMaster (CSM) Scrum Artifacts and Transparency Syllabus

How many Sprint Goals can a Sprint have?

Exactly one. A Sprint has a single Sprint Goal.

Is the Sprint Goal fixed during the Sprint, and what about scope?

The Sprint Goal is committed and does not change during the Sprint, but the scope (specific items) may be renegotiated between the Product Owner and Developers as more is learned.

Why must the Developers (not the Product Owner) own the Sprint Backlog and its plan?

Because the Developers are the ones doing the work; they best understand how to plan and execute it, which builds accountability and accuracy.

How often is the Sprint Backlog updated?

Throughout the Sprint as more is learned; it is updated at least daily (e.g., at the Daily Scrum) to reflect progress toward the Sprint Goal.

What is an Increment in Scrum?

A concrete stepping stone toward the Product Goal; each Increment is additive to prior Increments and must be usable and verified to work.

When does work count as part of an Increment?

Only when it meets the Definition of Done. Work that does not meet the Definition of Done cannot be considered part of an Increment.

Can multiple Increments be created within a single Sprint?

Yes. Multiple Increments may be created within a Sprint, and their sum is presented at the Sprint Review.

Does delivering an Increment require waiting for the Sprint Review?

No. An Increment may be delivered to stakeholders at any time during the Sprint once it is 'Done'; the Sprint Review should not be a gate for releasing value.

Which artifact carries the commitment 'Definition of Done'?

The Increment carries the Definition of Done as its commitment.

What is the Definition of Done?

A formal description of the state of the Increment when it meets the quality measures required for the product; it defines what 'complete' means.

Who creates the Definition of Done?

If it is an organizational standard, all teams must follow it as a minimum; otherwise the Scrum Team must create one appropriate for the product.

What must Developers do if a Product Backlog item does not meet the Definition of Done?

It cannot be released or even presented at the Sprint Review; it returns to the Product Backlog for future consideration.

How does the Definition of Done relate to quality and transparency?

It creates transparency by giving everyone a shared understanding of what work is completed as part of the Increment, ensuring consistent quality.

List the three Scrum artifacts and their respective commitments.

Product Backlog → Product Goal; Sprint Backlog → Sprint Goal; Increment → Definition of Done.

What is the purpose of the commitments attached to each artifact?

They enhance transparency and focus, providing measures against which progress can be assessed.

What is transparency in the context of Scrum artifacts?

Emergent process and work must be visible to those performing the work and those receiving it; artifacts must have high transparency so decisions are based on their perceived state.

What happens when transparency in the artifacts is low or incomplete?

Decisions made to optimize value and control risk can be flawed, diminished, or increase risk; low transparency leads to poor decisions.

How does low transparency affect empiricism?

Empiricism relies on accurate observation; if artifacts have low transparency, the inspection that follows produces misleading information, undermining adaptation.

What are practices that reduce incomplete transparency in Scrum?

Following the commitments (Product Goal, Sprint Goal, Definition of Done), using the Scrum events to inspect, and learning over time as a Scrum Team raises transparency.

How do the Scrum events help reduce incomplete transparency?

Each event is a formal opportunity to inspect and adapt the artifacts; transparency enables inspection, and inspection without transparency is misleading or wasteful.

What are the three empirical pillars of Scrum?

Transparency, Inspection, and Adaptation.

How is transparency the foundation of the other two empirical pillars?

Inspection enables adaptation, but inspection without transparency is misleading; transparency must come first so inspection and adaptation are based on accurate information.

How does each artifact support the empirical pillars?

Each artifact is designed to maximize transparency of key information, so inspection (at the events) yields accurate signals that drive effective adaptation toward the goals.

Compare the Product Backlog and the Sprint Backlog by scope and ownership.

Product Backlog: whole-product scope, ordered by the Product Owner, owned by the Product Owner. Sprint Backlog: single-Sprint scope (selected items + plan), owned by the Developers.

Compare the Product Goal and the Sprint Goal.

Product Goal is a long-term objective for the product (in the Product Backlog); Sprint Goal is the single short-term objective for one Sprint (in the Sprint Backlog). Multiple Sprints work toward one Product Goal.

Why can the Sprint Backlog scope be renegotiated but the Sprint Goal cannot?

The Sprint Goal is the committed objective that gives the Sprint coherence; scope (the 'how/what') may be clarified or adjusted with the Product Owner as learning occurs, as long as the goal remains intact.

What distinguishes an Increment from a Product Backlog item?

A Product Backlog item is planned work; an Increment is completed, Done work that is usable and additive toward the Product Goal.

What is the relationship between the Increment and the Sprint Review?

The sum of the Sprint's Increments is presented at the Sprint Review to inspect progress and adapt the Product Backlog, but Increments may also be released earlier.

How does refinement improve transparency of the Product Backlog?

By adding detail, order, and size and breaking items down, refinement makes upcoming work clearer and more visible, improving the accuracy of planning and inspection.

Why is each Increment required to be 'usable'?

So it represents real, verified, working value toward the Product Goal—enabling empirical inspection of actual progress rather than untested or partial work.