Scrum PSM I Exam Questions
Professional Scrum Master I (Page 11 )

Updated On: 24-Feb-2026

Which of these may a Development Team deliver at the end of a Sprint?

  1. Failing unit tests, to identify acceptance tests for the next Sprint.
  2. An increment of software with minor known bugs in it.
  3. An increment of working software that is "done".
  4. A single document, if that is what the Scrum Master asked for.

Answer(s): C

Explanation:

The correct answer is C, because a Development Team should deliver an increment of working software that is "done" by the end of a Sprint. The Scrum Guide states that "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'."



How much of the Sprint Backlog must be defined during the Sprint Planning event?

  1. Just enough tasks for the Scrum Master to be confident in the Development Team's understanding of the Sprint.
  2. The entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting.
  3. Enough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.
  4. Just enough to understand design and architectural implications.

Answer(s): C

Explanation:

The correct answer is C, because the Scrum Guide states that "the Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment. Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less. The Development Team self-organizes to undertake the work in the Sprint Backlog, both during Sprint Planning and as needed throughout the Sprint." Therefore, enough work should be defined during the Sprint Planning event so that the Development Team can create its best forecast of what it can do, and to start the first several days of the Sprint.



Who is responsible for managing the progress of work during a Sprint?

  1. The Scrum Master.
  2. The Development Team.
  3. The Product Owner.
  4. The most junior member of the Team.

Answer(s): B

Explanation:

The correct answer is B, because the Development Team is responsible for managing the progress of work during a Sprint. The Scrum Guide states that "the Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal. By tracking the remaining work throughout the Sprint, the Development Team can manage its progress."



A Development Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what "Done" means. (Choose two.)

  1. All work the Development Team is willing to do.
  2. Ready for integration.
  3. No work left from the definition of "Done".
  4. Whatever the Product Owner defines as quality.
  5. All work to create software that is ready to be released to end users.

Answer(s): C,E

Explanation:

The correct answers are C and E, because these statements explain what "Done" means. No work left from the definition of "Done" means that all Product Backlog items selected for a Sprint meet the quality criteria agreed upon by the Scrum Team. All work to create software that is ready to be released to end users means that the Increment is potentially releasable at any time during the Sprint.



What two factors are best considered when establishing the Sprint length? (Choose two.)

  1. The organization has mandated similar length sprints.
  2. The level of uncertainty over the technology to be used.
  3. The frequency at which team formation can be changed.
  4. The risk of being disconnected from the stakeholders.

Answer(s): B,D

Explanation:

The correct answers are B and D, because the length of the Sprint should be chosen based on the level of uncertainty over the technology to be used and the risk of being disconnected from the stakeholders. The Scrum Guide states that "Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month.
When a Sprint's horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase."






Post your Comments and Discuss Scrum PSM I exam dumps with other Community members:

Join the PSM I Discussion