Free Scrum PSM I Exam Braindumps (page: 24)

Select two ways in which technical debt impacts transparency. (Choose two.)

  1. When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.
  2. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.
  3. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.
  4. It enhances transparency for the Product Owner as a Development Team is not allowed to do additional feature development in a Sprint as long as there is technical debt.

Answer(s): B,C

Explanation:

The correct answers are B and C, because technical debt impacts transparency in these ways. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint, as it may contain hidden defects or incomplete functionality. It also results in future work being slowed down in unpredictable ways, as development progresses and code is added, the system becomes more difficult to stabilize and maintain.



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."






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

PSM I Exam Discussions & Posts