MENU
At the seventh Sprint Review, the stakeholders seem disappointed and angry. When asked about it, they say the product being built will not meet their needs and will cost more than they anticipated spending. What factors may have led to this?
(choose the best three answers)
Suggested Answer: E
Get Premium PSM-II Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
The Development Team owns the Definition of ''Done'' and is accountable for the quality of the Product Backlog items.
31 comments · newest first
MA
Mary
11 months ago
If changes weren't documented, that's a huge red flag!
MA
Ma
11 months ago
Wait, they weren’t allowed in the Daily Scrum? That seems off.
EM
Emilio
12 months ago
I think the PMO's role is often overlooked in these situations.
JO
Jolene
12 months ago
Totally agree, the Product Owner should be more involved!
MO
Moon
12 months ago
Sounds like a classic case of poor communication.
YU
Yuette
1 year ago
I vaguely recall a practice question about transparency in Scrum. If the Scrum Master didn't ensure that, it might have contributed to the stakeholders' frustration.
MA
Marvel
1 year ago
I feel like the Product Owner's role is crucial here. If they weren't communicating with stakeholders regularly, it could lead to disappointment.
NO
Noelia
1 year ago
I'm not sure, but I think if the PMO wasn't engaged, it might have caused some misalignment with the project goals. That could explain the cost issues.
AJ
Aja
1 year ago
I remember we discussed how important stakeholder engagement is during Sprint Reviews. If they weren't actively involved, that could definitely lead to misunderstandings about the product.
KE
Keena
1 year ago
I'm pretty confident the answer is B, the product structure file. That's where the detailed information about the components and quantities for a parent item would be stored, right?
FR
Freida
1 year ago
Hmm, I'm a bit confused by the question. Is the team struggling with the new technology or just having reduced velocity? I'll need to think this through carefully.
TH
Thersa
1 year ago
Man, I bet the Scrum Master was sweating bullets during that Sprint Review. Probably wishing they had a teleportation device to just disappear!
WI
Wilbert
1 year ago
Yikes, this sounds like a real dumpster fire. The Scrum Master dropped the ball on transparency, and the Product Owner is probably going to need to do some serious damage control with the stakeholders.
WI
William
1 year ago
E) The Product Owner has not been interacting frequently with the stakeholders and kept them aware of the progress of the project.
MO
Mose
1 year ago
D) The Scrum Master has not ensured transparency.
LU
Luther
1 year ago
A) The stakeholders have not been using the Sprint Reviews to actively engage, and inspect and evaluate progress.
JI
Jin
1 year ago
Haha, I bet the stakeholders are really regretting not showing up to those Daily Scrums. Maybe they thought they were just for the dev team, but boy were they wrong!
MA
Mattie
1 year ago
E) The Product Owner has not been interacting frequently with the stakeholders and kept them aware of the progress of the project.
LA
Laurel
1 year ago
B) The stakeholders were not allowed to enter the development area, or be present at the Daily Scrum.
DE
Deonna
1 year ago
A) The stakeholders have not been using the Sprint Reviews to actively engage, and inspect and evaluate progress.
GR
Gregoria
1 year ago
Oof, the PMO and change management issues definitely contributed to this mess. Sounds like a total communication breakdown. Someone should have been keeping a closer eye on the project plan.
ST
Stephane
1 year ago
F) Changes to the project plan were not adequately documented and shared. The change request procedure was not diligently followed.
IO
Iola
1 year ago
C) The Project Management Office (PMO) and its project managers have not been adequately engaged, causing the project plan to become inaccurate.
VI
Vince
1 year ago
A) The stakeholders have not been using the Sprint Reviews to actively engage, and inspect and evaluate progress.
JE
Jerilyn
2 years ago
Looks like a classic case of poor stakeholder engagement. The Scrum Master and Product Owner should have been more proactive in keeping the stakeholders informed and involved. I bet they felt left in the dark the whole time.
KA
Kanisha
1 year ago
Looks like a classic case of poor stakeholder engagement. The Scrum Master and Product Owner should have been more proactive in keeping the stakeholders informed and involved. I bet they felt left in the dark the whole time.
CO
Corrinne
1 year ago
E) The Product Owner has not been interacting frequently with the stakeholders and kept them aware of the progress of the project.
JA
Jade
1 year ago
A) The stakeholders have not been using the Sprint Reviews to actively engage, and inspect and evaluate progress.
GI
Gianna
2 years ago
I agree. Lack of transparency from the Scrum Master could also be a reason for the stakeholders' disappointment.
VA
Vallie
2 years ago
Yeah, and maybe the Product Owner not keeping the stakeholders informed enough.
SH
Shawnta
2 years ago
I think the stakeholders not actively engaging in Sprint Reviews could be a factor.