Scrum Exam PSM-II Topic 1 Question 64 Discussion

Actual exam question for Scrum's PSM-II exam

Question #: 64
Topic #: 1

Marian is a product Owner working on a Scrum Team on a new release for her product. Based on the average velocity of the previous release Marian estimated the project to take seven Sprints. Average velocity In the previous release was thirteen completed units of work per Sprint Development is three Sprints underway, with tour more Sprints to go until the release.

Product Backlog has been stable.

Over the first three Sprints, the Developers report their average velocity is nine, while not having fully tested all the delivered functionality. The Developers estimate that the unfinished testing would have required of a Sprints time. The Developers believe that the required

velocity of thirteen is within their reach. What is the most effective way to recover?

(choose the best answer)

A. The Developers set the open work aside to be performed in one or more release Sprints. They remind Marian to find funding for enough Release Sprints in which this remaining work can be done. up to one release Sprint per three development Sprints may be required, It is Marian's responsibility to inform users and stakeholders Of the impact on the release date.

B. Transparency needs to be restored by addng the undone work to the Product Backlog. The Developers must figure out a way to deliver in the upcoming Sprints a velocity of not only 13 units of new work, but also two additional points to catch up undone work. It is the Scrum Master's duty to assess whether such repair is possible. If not, the Scrum Master initiates a restart with a more reliable team Or cancels the project. The Scrum Master will have to inform Product Owner and the stakeholders.

CIn the next Sprints, the Developers keep making sure that all of the selected scope per Sprint is as done as possible, at least at the past level of 90%. In every Sprint the undone work of the previous Sprint is estimated and added to the Sprint Backlog. It comes on top of the expected forecast of 13 units, so it does not mess up progress on the product Backlog.

DThe Developers inform Marian that the progress she has perceived to date is not correct The Increment is not releasable. They give Marian their estimate of the effort it would take to get the past work done, and suggest doing that work first before proceeding with new features. The Developers also re-estimate the effort to complete the remaining backlog, including all testing. In the end, it is Marian's call to continue the project or to cancel.

Show Suggested Answer

Suggested Answer: A

When multiple Scrum Teams work from the same Product Backlog, they need to collaborate and coordinate their work to deliver a potentially releasable Increment that meets the Definition of Done. This requires minimizing dependencies between Scrum Teams, such as technical, functional, or organizational dependencies. Dependencies can cause delays, rework, waste, and lower quality.Scrum Teams should strive to be cross-functional and autonomous, and use techniques such as feature slicing, dependency mapping, and integration testing to reduce dependencies123.Reference:1: https://www.scrum.org/resources/blog/dependencies-between-scrum-teams2: https://www.scrum.org/resources/blog/feature-slicing-how-make-it-work3: https://www.scrum.org/resources/blog/integration-testing-scrum-projects

by Soledad at Apr 21, 2024, 03:45 AM

Limited Time Offer

25%

Off

Get Premium PSM-II Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lawrence

Oof, this is a tricky one. Looks like the Devs dropped the ball on testing, and now Marian's got a real mess on her hands. Time to buckle down and find a way to get this back on track.

upvoted 0 times

...

Lonny

28 days ago

I believe option D could also be a good approach. It's crucial to address the unreleasable increment and focus on completing the past work before moving on to new features. Ultimately, it's up to Marian to make the final decision.

upvoted 0 times

...

Clay

1 months ago

I agree with Troy. It's important to assess whether the repair is possible and if not, consider restarting with a more reliable team. We need to keep the stakeholders informed.

upvoted 0 times

...

Troy

1 months ago

I think option B is the best choice. Transparency is key in Scrum, and adding the undone work to the Product Backlog will help us catch up and deliver the required velocity.

upvoted 0 times

...