Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scrum Exam PSM-II Topic 2 Question 79 Discussion

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

True or False: During the Sprint Review of a scaled development effort, every Scrum Team should demonstrate its individual Increment separately.

Show Suggested Answer Hide Answer
Suggested Answer: D

The best way to determine if the Product Owner is interacting with the Developers enough throughout a Sprint is to observe whether both parties are satisfied with the Increment.The Increment is a concrete stepping stone toward the Product Goal1.It must be usable and meet the Definition of Done1.The Product Owner is accountable for maximizing the value of the product resulting from the work of the Developers1.The Developers are accountable for creating a valuable, useful, and potentially releasable Increment every Sprint1. Therefore, if both the Product Owner and the Developers are happy with the quality and value of the Increment, it means that they have communicated and collaborated effectively throughout the Sprint.

Some reasons why the other options are not correct are:

A: The Developers should determine the percentage of time the Product Owner is required to be present and monitor whether the Product Owner's average presence is around this figure. This option is not correct because it implies that there is a fixed or optimal amount of time that the Product Owner should spend with the Developers, which may not be true. The Product Owner's interaction with the Developers may vary depending on the context, complexity, and uncertainty of the product and the Sprint.The Scrum Guide does not prescribe any specific time or frequency for the Product Owner's involvement with the Developers1.The Product Owner should be available to provide guidance and feedback to the Developers as needed, but not interfere with their self-organization and autonomy1.

B: Check the Daily Scrum reports to see whether the Product Owner was present at the majority of the Daily Scrum meetings. This option is not correct because it assumes that the Daily Scrum is a meeting where the Product Owner should be present, which is not true.The Daily Scrum is an event for and by the Developers12, not for reporting or accountability to anyone else.The Product Owner may attend as an observer or a collaborator, but only if invited by the Developers12. The presence or absence of the Product Owner at the Daily Scrum does not indicate how much they interact with the Developers throughout the Sprint.

C: Observe whether the Developers need to ask the Product Owner questions at times other than during the Daily Scrum. This option is not correct because it implies that asking questions is a sign of insufficient interaction, which may not be true. Asking questions is a natural and healthy part of communication and collaboration between the Product Owner and the Developers. It shows that they are engaged, curious, and willing to learn from each other. It also helps them to clarify requirements, expectations, and feedback, and to resolve any ambiguities or conflicts. Asking questions does not necessarily mean that there is a lack of interaction, but rather that there is a need for more information or clarification.


What is an Increment? | Scrum.org

What Is a Daily Standup? | A Guide to Running Effective Standup Meetings | Atlassian

Contribute your Thoughts:

Chanel
29 days ago
Wait, are we sure the Scrum Teams aren't supposed to do some kind of synchronized dance routine during the Sprint Review? That would be way more entertaining.
upvoted 0 times
Dylan
3 days ago
True
upvoted 0 times
...
Hillary
4 days ago
Haha, that would definitely make the Sprint Review more interesting!
upvoted 0 times
...
Maile
5 days ago
B) False
upvoted 0 times
...
Pamella
17 days ago
A) True
upvoted 0 times
...
...
Tamera
1 months ago
Definitely false. The teams should be collaborating, not putting on their own little shows. I bet the product owner would be so confused if they had to hop between teams.
upvoted 0 times
Monte
10 days ago
False
upvoted 0 times
...
Stephaine
12 days ago
True
upvoted 0 times
...
...
Tatum
2 months ago
Haha, what is this, a middle school science fair? We're talking about professional software development here, not individual projects.
upvoted 0 times
Ricki
12 days ago
True
upvoted 0 times
...
Kaitlyn
12 days ago
True
upvoted 0 times
...
Shenika
15 days ago
B) False
upvoted 0 times
...
Dortha
23 days ago
A) True
upvoted 0 times
...
Dorothea
23 days ago
I agree, it does seem a bit elementary to have each team demonstrate separately.
upvoted 0 times
...
Lashawna
1 months ago
B) False
upvoted 0 times
...
Luis
1 months ago
A) True
upvoted 0 times
...
...
Fatima
2 months ago
Hmm, I thought the whole point of a scaled effort was to have the teams work together. Demonstrating their increments separately seems counterintuitive.
upvoted 0 times
...
Bulah
2 months ago
I'm pretty sure this is false. In a scaled development effort, the Scrum Teams should present their work collectively during the Sprint Review.
upvoted 0 times
Dorothea
25 days ago
Yes, that's correct. It helps to ensure alignment and collaboration across the teams.
upvoted 0 times
...
Alonso
1 months ago
I agree, it's false. The Scrum Teams should present their work collectively.
upvoted 0 times
...
Ashley
1 months ago
B) False
upvoted 0 times
...
Pamella
2 months ago
A) True
upvoted 0 times
...
...
Gilberto
3 months ago
But in a scaled development effort, it makes sense for each Scrum Team to demonstrate their individual Increment separately to ensure transparency and alignment.
upvoted 0 times
...
Edmond
3 months ago
I disagree, I believe the answer is B) False.
upvoted 0 times
...
Gilberto
3 months ago
I think the answer is A) True.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77