MENU
Business stakeholders of an agile project frequently skip the review meetings. What should the agile practitioner do?
Suggested Answer: D
Get Premium PMI-ACP Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
40 comments · newest first
AR
Ardella
11 months ago
Not sure if just notes will really change their minds.
LA
Lauran
11 months ago
I think convincing them to attend is the best approach.
SA
Sabrina
12 months ago
Wait, why are they skipping the meetings in the first place?
RE
Rex
12 months ago
Totally agree, they need to stay in the loop.
LA
Larae
1 year ago
Sending meeting notes is a must!
RE
Reuben
1 year ago
I recall a similar question where we talked about the role of the product owner. Maybe asking them to communicate progress could work, but I’m not entirely convinced it’s the best approach.
DO
Dorian
1 year ago
I think including results in information radiators is a good idea, but I wonder if that alone will get them to show up.
MY
Myra
1 year ago
I feel like sending meeting notes could help, but it might not really encourage them to attend next time. It seems a bit passive.
LE
Lewis
1 year ago
I remember we discussed how important stakeholder engagement is in agile. I think convincing them of the benefits might be key, but I'm not sure if that's enough.
JE
Jeannetta
1 year ago
I'm a bit unsure about this one. The options seem similar, but I'll try to analyze the nuances and pick the most appropriate response.
SH
Shawnda
1 year ago
Ah, I've dealt with this before. I'm pretty confident I can identify the most effective solution for the agile practitioner.
JA
Janey
1 year ago
Hmm, this is a common issue in agile projects. I think I know the right way to handle this, but I'll double-check the options just to be sure.
SH
Sharee
1 year ago
This seems like a tricky one. I'll need to think through the different options carefully to make sure I pick the best approach.
LE
Lenita
1 year ago
I'm a bit confused by the variable costs being described as "immaterial." Does that mean I can ignore them in my calculations? I'll need to think through how that affects the analysis.
MA
Malcolm
1 year ago
Okay, let's see. The type attribute is on the Name element, and the document has a namespace declaration for "urn:sample". I'm thinking the answer is A, but I'll double-check the other options just to be sure.
CR
Cristal
1 year ago
I'm a bit confused on this one. The options all look like they could be relevant, but I'm not sure which one is the right answer. I'll need to think it through carefully.
MI
Mitsue
1 year ago
This seems straightforward enough. I'll just need to plug the numbers into the decision tree and see which option has the higher expected profit. Shouldn't be too difficult.
MO
Mozelle
1 year ago
Okay, I think I've got this. The key is to identify the items that would cause a difference between earnings and comprehensive income for a non-specialized industry. I'll go through each option and evaluate them.
GA
Galen
1 year ago
I've seen that if DTMF isn't negotiated at all, it leads to problems with key presses being recognized. Option D feels likely here.
AV
Avery
1 year ago
Option C is the way to go. Information radiators are like the agile version of the 'If you build it, they will come' motto. Stakeholders can't ignore what they can't avoid!
HE
Helaine
1 year ago
A) Ask the product owner to inform all stakeholders about the project's progress. That's the product owner's job, and they should be the ones keeping everyone updated.
DA
Dana
1 year ago
C) Include the results of the review meetings in the information radiators.
KR
Kristine
1 year ago
B) Send meeting notes to all stakeholders after each review meeting.
GE
Georgene
1 year ago
A) Ask the product owner to inform all stakeholders about the project's progress.
AR
Arlen
1 year ago
C) Include the results of the review meetings in the information radiators.
JE
Jeannine
1 year ago
B) Send meeting notes to all stakeholders after each review meeting.
CA
Casandra
1 year ago
A) Ask the product owner to inform all stakeholders about the project's progress.
CL
Clarinda
2 years ago
I'd go with B) Send meeting notes to all stakeholders after each review meeting. It's the least intrusive approach, and stakeholders can stay in the loop without actually showing up.
SO
Sommer
1 year ago
Sending meeting notes is a great way to keep stakeholders engaged without requiring their physical presence.
YO
Yolando
1 year ago
I agree. It's a good way to ensure stakeholders are aware of the project's progress.
DA
Darell
2 years ago
That's a good point. Sending meeting notes can keep everyone informed.
BR
Britt
2 years ago
D) Convince the stakeholders of the benefits of attending the review meetings. Getting their buy-in is crucial for the long-term success of the project.
AS
Ashlyn
1 year ago
Getting stakeholders on board will lead to better outcomes.
CH
Chanel
1 year ago
We should emphasize the benefits of their active participation.
DI
Dianne
1 year ago
Maybe we can highlight how their input can improve the project.
HA
Hayley
1 year ago
It's important to show stakeholders the value of attending review meetings.
AN
Annette
2 years ago
C) Include the results of the review meetings in the information radiators. This way, even if stakeholders don't attend, they can still stay informed about the project's progress.
DO
Donte
2 years ago
I think sending meeting notes to all stakeholders after each review meeting could also help keep them informed and engaged.
GO
Goldie
2 years ago
I agree with Audrie. It's important for stakeholders to be kept in the loop, even if they can't attend the review meetings.
AU
Audrie
2 years ago
I think the agile practitioner should ask the product owner to inform all stakeholders about the project's progress.