Scrum PSM I Exam
Professional Scrum Master I (Page 8 )

Updated On: 26-Jan-2026

When a Development Team determines that it will not be able to finish the complete forecast, who has to be present when reviewing and adjusting the Sprint work selected? (Choose the best answer.)

  1. The Development Team.
  2. The Product Owner and all stakeholders.
  3. The Product Owner and the Development Team.
  4. The Scrum Master, project manager and Development Team.

Answer(s): C

Explanation:

When a Development Team determines that it will not be able to finish the complete forecast, both the Product Owner and the Development Team have to be present when reviewing and adjusting the Sprint work selected, as stated in [6]: "If there is not enough work remaining for all members of a Development Team then they can renegotiate scope with their Product Owner. If there is too much work remaining then they can also renegotiate scope with their Product Owner."



The IT manager asks a Development Team for a status report describing the progress throughout the Sprint.
The Development Team asks the Scrum Master for advice. The Scrum Master should:
(Choose the best answer.)

  1. Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review.
  2. Tell the Development Team to figure it out themselves.
  3. Tell the Development Team to fit the report into the Sprint Backlog.
  4. Create and deliver the report to the manager herself.
  5. Ask the Product Owner to send the manager the report.

Answer(s): A

Explanation:

The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review, as stated in [5]: "The Scrum Master should educate the IT manager about how Scrum works and how progress is measured. The Scrum Master should invite the IT manager to attend the Sprint Review where the Development Team demonstrates what was accomplished during the Sprint. The Scrum Master should also explain that status reports are not necessary in Scrum, as transparency is ensured by using artifacts such as Product Backlog, Sprint Backlog, and Increment."



When many Development Teams are working on a single product, what best describes the definition of "Done"? (Choose the best answer.)

  1. Each Development Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint.
  2. It depends.
  3. Each Development Team uses its own but must make their definition clear to all other teams so the differences are known.
  4. All Development Teams must have a definition of "Done" that makes their combined work potentially releasable.

Answer(s): D

Explanation:

When many Development Teams are working on a single product, the definition of "Done" must be shared by all Development Teams and make their combined work potentially releasable, as stated in [4]: "When multiple teams work together on one product they must mutually define and comply with the same Definition of Done. This makes sure all Increments adhere to a consistent quality level."



A Scrum Master is keeping a list of open impediments, but it is growing and they have been able to resolve only a small portion of the impediments.
Which two techniques would be most helpful in this situation?
(Choose two.)

  1. Discuss the impediments with the Development Team.
  2. Prioritize the list and work on them in order.
  3. Arrange a triage meeting with all project managers.
  4. Add each open impediment to the Product Backlog.

Answer(s): A,B

Explanation:

Two techniques that would be most helpful in this situation are to discuss the impediments with the Development Team, and to prioritize the list and work on them in order, as stated in [3]: "The Scrum Master should facilitate a discussion with the Development Team to identify and prioritize the impediments that are blocking their progress. The Scrum Master should then work with the

Development Team and other stakeholders to remove or mitigate these impediments as soon as possible."



If burndown charts are used to visualize progress, what does a trend line through a release burndown chart indicate?

  1. The evolution of the cost spent on the project.
  2. When all work will be completed to the Scrum Team can be released for other work.
  3. When the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.
  4. When the project will be over if the Product Owner removes work that is equal in effort to any new work that is added.

Answer(s): C

Explanation:

a burndown chart is a graphical representation of work left to do versus time. It is very useful for predicting when all of the work will be completed. It is often used in agile software development methodologies such as Scrum. However, burndown charts can be applied to any project containing measurable progress over time. A release burndown chart tracks progress across multiple Sprints towards a product release. It shows how much work remains in the Product Backlog at any given time during the release cycle. A trend line through a release burndown chart indicates when the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.



Viewing page 8 of 55
Viewing questions 36 - 40 out of 268 questions



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

Join the PSM I Discussion