An agile team discovers a new risk and identifies that its impact may be severe. What should an agile practitioner recommend?
Suggested Answer: B
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
MA
Maurine
11 months ago
I agree with B, but we should also consider the severity of the risk.
AL
Alyssa
12 months ago
Wait, are we really just going to keep going with the plan? Sounds risky!
DO
Dorothy
12 months ago
A solid risk register update is crucial, so D is a good choice.
CA
Carlee
1 year ago
Definitely not C! Ignoring the risk is a bad idea.
PO
Portia
1 year ago
I think option B makes the most sense. Balance is key!
ET
Ettie
1 year ago
I recall something about maintaining velocity, but if the risk is severe, I wonder if option C is really the best approach.
KE
Kerrie
1 year ago
I think we had a practice question about risk management where updating the risk register was key. So, option D sounds familiar.
PE
Penney
1 year ago
I’m not sure, but I feel like adding a goal to the current iteration could be too much pressure. Maybe option A isn't the best?
HU
Huey
1 year ago
I remember we discussed how important it is to balance risk and value in agile practices. I think option B might be the right choice.
AD
Adelina
1 year ago
Wait, I'm confused. Should we just update the risk register and get a specialist involved? That seems like it might slow things down. Maybe option B is the safest bet to keep things moving while addressing the risk.
GA
Galen
1 year ago
Hmm, I'm a bit unsure here. Should we really just continue with the current plan to maintain velocity, or is that too risky? I'm leaning towards option B to balance things out, but I'll have to think it through more.
EM
Emily
1 year ago
This seems like a straightforward question about how to handle a new severe risk in an agile context. I think the key is to balance risk reduction and value-adding activities, so I'd recommend option B.
VE
Verda
1 year ago
Okay, I've got this. The agile approach is to be responsive to changes, so adding a goal to the current iteration to mitigate the risk is the way to go. Option A is the clear choice here.
TW
Twana
1 year ago
Hmm, I'm a bit unsure about this one. Moving the work to the next stage seems like it could be a reasonable solution, but I'm not sure if that's the best approach. I'll need to re-read the question and think it through.
NA
Natalie
1 year ago
Okay, the key here seems to be understanding the different states of the storage pools and what that means for their management in HPE OneView. I think I've got a good handle on this, so I'll give it my best shot.
ST
Stephaine
1 year ago
I'm a bit confused by this question. I thought testing was more of a later stage activity, not part of requirements gathering. But now that I think about it, validating the requirements through testing does seem relevant. I'll have to review my notes to be sure.
JU
Juliann
1 year ago
I'm feeling pretty confident about this one. The question provides a lot of useful information about the current environments, so I should be able to identify the best steps to take.
GW
Gwenn
2 years ago
Option B is the way to go, unless of course, the risk involves a herd of angry llamas. Then all bets are off!
AR
Arminda
1 year ago
D) Update the risk register and seek direction from a risk specialist.
AD
Adolph
1 year ago
C: Unless those llamas are involved, then we might need a different plan!
ST
Staci
1 year ago
B) Balance risk reduction and value adding activities in the next iteration.
CH
Chauncey
1 year ago
B: Definitely, that seems like the best approach.
JO
Jolanda
1 year ago
B) Balance risk reduction and value adding activities in the next iteration.
CH
Charlette
1 year ago
A: We should balance risk reduction and value adding activities in the next iteration.
AM
Amina
2 years ago
A) Add a goal to the current iteration to fully mitigate or control the risk.
EV
Eveline
2 years ago
Option C? Are you kidding me? Maintaining velocity at the expense of addressing a severe risk? That's just plain reckless.
EL
Elfrieda
2 years ago
I'm leaning towards Option A. Dedicating an entire iteration to mitigating the risk seems like the most proactive approach.
HE
Helga
2 years ago
Option D sounds like the prudent choice. Updating the risk register and seeking guidance from a risk specialist is the responsible thing to do.
JE
Jesus
1 year ago
D) Update the risk register and seek direction from a risk specialist.
DE
Devorah
1 year ago
A) Add a goal to the current iteration to fully mitigate or control the risk.
CR
Cruz
2 years ago
D) Update the risk register and seek direction from a risk specialist.
BA
Barb
2 years ago
A) Add a goal to the current iteration to fully mitigate or control the risk.
AU
Audra
2 years ago
I think updating the risk register and seeking direction from a risk specialist would be a good idea too.
TH
Thomasena
2 years ago
I agree with Tracey, it's important to address the severe impact of the risk.
PR
Precious
2 years ago
I think Option B is the way to go. Balancing risk reduction and value-adding activities is crucial in an agile environment.
AF
Afton
1 year ago
So, we should go with both options B and D to effectively manage the new risk.
AN
Anthony
1 year ago
Yes, that's a good point. We need to make sure we have expert advice on how to handle the risk.
VA
Valentin
1 year ago
But shouldn't we also update the risk register and seek direction from a risk specialist?
NA
Naomi
2 years ago
I agree, balancing risk reduction and value-adding activities is key.
TR
Tracey
2 years ago
I think we should add a goal to mitigate the risk in the current iteration.