The Scrum Guide defines the Daily Scrum as a 15-minute time-boxed event: "The Daily Scrum is a 15-

minute event for the Developers of the Scrum Team." This duration is fixed regardless of Sprint

length, ensuring consistency and focus on synchronizing work and identifying impediments. Option A

refers to a scheduling practice, not the time-box. Option B is arbitrary and not Scrum-defined. Option

C is far too long and contradicts the Scrum Guide. Option E incorrectly suggests variability based on

Sprint length, which isn’t supported—15 minutes is the standard. Thus, D is the correct answer.

Reference: Scrum Guide (2020), Section: "Daily Scrum."

The Scrum Guide mandates that all work selected for a Sprint must meet the Definition of "Done":

"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." During Sprint Planning, the Developers forecast what they

can deliver as a "Done" Increment, committing to that scope. Option A reflects this accountability.

Option B suggests incomplete work carries over, which violates the Increment’s usability

requirement. Option C is too vague and not tied to "Done." Option D imposes a process Scrum

doesn’t require. Thus, A is correct.

Reference: Scrum Guide (2020), Sections: "Sprint Planning," "The Increment."

Scrum imposes no formal pre-conditions for Sprint Planning beyond the Sprint starting. The Scrum

Guide states: "Sprint Planning initiates the Sprint by laying out the work to be performed for the

Sprint."

A: A fully refined backlog isn’t required; refinement is ongoing.

B: Budget approval isn’t a Scrum concept.

C, D: The Sprint Goal is defined during, not before, Sprint Planning.

E: Some "Ready" items help, but it’s not mandatory; planning can refine items.

F: Correct—no pre-conditions exist; the team works with what’s available.

Exact Extract from Scrum Guide: "Sprint Planning is timeboxed to a maximum of eight hours for a

one-month Sprint... The Scrum Team may also invite other people to attend Sprint Planning to

provide advice." (Section: "Sprint Planning") No pre-conditions are listed.

Thus, F is correct.

Reference: Scrum Guide (2020), Section: "Sprint Planning."

The Daily Scrum is the Developers’ event, not the Scrum Master’s. The Scrum Guide states: "The

Daily Scrum is a 15-minute event for the Developers of the Scrum Team... The Scrum Master ensures

that the Developers have the meeting, but the Developers are responsible for conducting the Daily

Scrum." The Scrum Master’s role is to ensure it happens and is effective, not to attend mandatorily.

A: Documenting impediments is a support task, not a Daily Scrum requirement.

B: Facilitation is optional, only if requested.

C: Burndown charts aren’t mandated; this isn’t their purpose.

D: Correct—they ensure it occurs, not that they must be present.

Exact Extract from Scrum Guide: "The Scrum Master ensures that the Developers have the meeting,

but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches the

Developers to keep it within the 15-minute timebox." (Section: "Daily Scrum")

Thus, D is correct.

Reference: Scrum Guide (2020), Section: "Daily Scrum."

Success in Scrum is tied to value delivery, not internal metrics. Option B—frequent releases with KPI

updates—aligns with Scrum’s empirical nature: "Scrum is founded on empiricism and lean thinking."

Real-world feedback refines the Product Backlog, ensuring success.

A: Velocity is an internal capacity metric, not a success indicator.

C: Time variance is irrelevant to value.

D: Acceptance at Sprint Review is a step, but not the ultimate measure of market success.

Exact Extract from Scrum Guide: "The Sprint Review is a working session and the Scrum Team should

avoid limiting it to a presentation... The Product Owner discusses the Product Backlog as it stands."

(Section: "Sprint Review") B extends this to market validation.

Thus, B is correct.

Reference: Scrum Guide (2020), Sections: "Scrum Theory," "Sprint Review."

The Sprint Retrospective is an event for the entire Scrum Team, including the Scrum Master, to

inspect and improve their processes. The Scrum Guide explicitly states that the Scrum Master

participates as a peer: "The Scrum Master participates as a peer team member in the Sprint

Retrospective from the accountability over the Scrum Team’s effectiveness." This ensures a

collaborative review of the Sprint, including the Scrum Master’s facilitation role.

A: True—the Scrum Master is a full participant.

B: False—exclusion contradicts Scrum’s team focus.

Exact Extract from Scrum Guide: "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 Scrum

Master participates as a peer team member in the Sprint Retrospective from the accountability over

the Scrum Team’s effectiveness." (Section: "Sprint Retrospective")

Thus, A is correct.

Reference: Scrum Guide (2020), Section: "Sprint Retrospective."

The Scrum Guide defines an Increment as "a concrete stepping stone toward the Product Goal" that

is usable and meets the Definition of "Done": "Each Increment is additive to all prior Increments and

thoroughly verified, ensuring that all Increments work together." Option E captures this—new,

usable features that build on previous work. Option A (test suite) is a tool, not an Increment. Option

B (UML diagrams) is documentation, not working software. Option C (task decomposition) is

planning, not a product. Option D (UI design) isn’t necessarily usable software. Thus, E best describes

an Increment.

Reference: Scrum Guide (2020), Section: "The Increment."

The Product Owner has explicit accountability for product value. The Scrum Guide states: "The

Product Owner is accountable for maximizing the value of the product resulting from the work of the

Scrum Team."

A: The Scrum Master ensures Scrum effectiveness, not value.

B: Correct—value maximization is their role.

C, D: Execs and Developers support, but don’t own this.

Exact Extract from Scrum Guide: "The Product Owner is accountable for maximizing the value of the

product resulting from the work of the Scrum Team. How this is done may vary widely across

organizations, Scrum Teams, and individuals." (Section: "The Product Owner")

Thus, B is correct.

Reference: Scrum Guide (2020), Section: "The Product Owner."

Thank you for your visit.

The Definition of "Done" ensures quality and clarity. The Scrum Guide states: "The Definition of Done

is a formal description of the state of the Increment when it meets the quality measures required for

the product."

A: It ensures the Increment is usable/releasable: "In order to provide value, the Increment must be

usable."

B: It provides transparency by setting a shared standard: "The Definition of Done creates

transparency by providing everyone a shared understanding of what work was completed."

C: The Sprint Goal is separate, defined in Sprint Planning.

D: Unit testing is a practice, not a purpose of "Done."

Exact Extract from Scrum Guide: "The Definition of Done creates transparency by providing everyone

a shared understanding of what work was completed as part of the Increment... In order to provide

value, the Increment must be usable." (Section: "Definition of Done")

Thus, A and B are correct.

Reference: Scrum Guide (2020), Section: "Definition of Done."

The Product Backlog is managed solely by the Product Owner, not stakeholders. The Scrum Guide

explains: "The Sprint Review is a working session... The Product Owner discusses the Product Backlog

as it stands." Stakeholders provide feedback during the Sprint Review, which the Product Owner may

use to adjust priorities, but they don’t directly re-prioritize it.

A: False—stakeholders don’t have this authority.

B: Correct—the Product Owner retains control.

Exact Extract from Scrum Guide: "The Product Owner is one person, not a committee... For Product

Owners to succeed, the entire organization must respect their decisions." (Section: "The Product

Owner")

Thus, B is correct.

Reference: Scrum Guide (2020), Section: "Sprint Review."