New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Scrum PSM-II Exam - Topic 1 Question 64 Discussion

Actual exam question for Scrum's PSM-II exam
Question #: 64
Topic #: 1
[All PSM-II Questions]

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.

Show Suggested Answer Hide 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:

0/2000 characters
Submit Cancel
Tijuana
3 months ago
Wow, I can't believe they thought the progress was fine!
upvoted 0 times
...
Soledad
3 months ago
Transparency is key, so option A sounds right to me.
upvoted 0 times
...
Kattie
3 months ago
Not sure if the team can really hit that velocity again.
upvoted 0 times
...
Aliza
4 months ago
I think option B makes the most sense!
upvoted 0 times
...
Dorethea
4 months ago
Marian's estimate was based on old data.
upvoted 0 times
...
Kristin
4 months ago
I vaguely recall a practice question about prioritizing work in Scrum. It feels like option A might be a bit risky since it suggests setting aside work, which could lead to more complications later on.
upvoted 0 times
...
Cecil
4 months ago
I feel like option C could work too, especially if the team can maintain a high level of completion. But what if they can't keep up with both the new work and the undone tasks?
upvoted 0 times
...
Candra
4 months ago
I think option D makes sense because it directly addresses the issue of the Increment not being releasable. But I wonder if Marian would really be okay with delaying new features for the sake of catching up on testing.
upvoted 0 times
...
Toshia
5 months ago
I remember we discussed the importance of transparency in Scrum. Option B seems to emphasize that, but I'm not sure if the Scrum Master should really have the authority to cancel the project.
upvoted 0 times
...
Viola
5 months ago
I think option A makes the most sense here. The developers should set aside the unfinished work to be done in additional release sprints. Marian needs to manage stakeholder expectations on the impact to the release date.
upvoted 0 times
...
Delmy
5 months ago
Whoa, this is a mess. The developers need to be upfront about the true state of the work, and Marian needs to decide whether to continue or cancel the project. Option D seems like the most transparent approach.
upvoted 0 times
...
Edelmira
5 months ago
Okay, let me see here. Looks like the developers have been underperforming and there's some untested work that needs to be accounted for. I'm leaning towards option C - keeping the team focused on getting the work fully done each sprint.
upvoted 0 times
...
Valentine
5 months ago
Hmm, this is a tricky one. I'll need to carefully review the details and think through the options. The key seems to be addressing the gap between the expected and actual velocity.
upvoted 0 times
...
Solange
5 months ago
Okay, let's see. The management plane is for managing and configuring network devices, so I'm guessing Secure Shell and HTTPS would be good options here.
upvoted 0 times
...
Belen
5 months ago
Okay, let me think this through. We need to verify the room availability when the request is made, so it's not going to be in-browser programming. And it's not just a static check, so functional programming isn't the right answer either. I'm going to go with server-side programming.
upvoted 0 times
...
Louvenia
9 months ago
Hold up, is this a Scrum exam or a comedy show? These Devs need to get their act together and stop trying to game the system. Option D is the only way to go - time to face the music.
upvoted 0 times
...
Elenor
9 months ago
I vote for option A. Let's just shove all that messy testing work into the release Sprints and call it a day. Marian can deal with the fallout, right? That's what POs are for, right?
upvoted 0 times
...
Lamar
9 months ago
Haha, looks like the Devs were a bit too eager to hit that velocity target, eh? Option C seems like a good compromise - keep chipping away at the backlog and stay transparent about the unfinished work.
upvoted 0 times
...
Jaclyn
9 months ago
Hmm, I think option D is the way to go. Being upfront about the lack of releasable Increment and re-estimating the remaining work is the responsible thing to do. Marian needs to know the full picture.
upvoted 0 times
William
8 months ago
Marian will have to carefully consider the Developers' estimates before deciding the next steps.
upvoted 0 times
...
Zita
8 months ago
The Developers should definitely prioritize completing the past work before moving on to new features.
upvoted 0 times
...
Beata
8 months ago
Yes, it's important for Marian to have all the information to make informed decisions.
upvoted 0 times
...
Alpha
8 months ago
I agree, being transparent about the progress is crucial.
upvoted 0 times
...
...
Lawrence
10 months ago
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
Carmelina
9 months ago
C) In 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.
upvoted 0 times
...
Sue
9 months ago
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.
upvoted 0 times
...
...
Lonny
11 months 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
11 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
11 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
...

Save Cancel