Your last project was released three months ago and used a risk-based approach. In production, a number of serious failures in low risk areas have occurred.
What is the most important lesson to be learned from this information? [2]
26 comments · newest first
CH
Charlette
5 months ago
D could help. Testing low-risk areas first might prevent failures.
PE
Pete
5 months ago
C makes sense. Stakeholders need to know potential issues.
MI
Mireya
6 months ago
I feel A is crucial. We should learn before going live.
MI
Mignon
6 months ago
I think B is key. More perspectives can catch risks.
TR
Trinidad
6 months ago
Lessons learned should happen after, not before!
AS
Ashleigh
6 months ago
Testing lower risk areas first seems like a no-brainer.
ER
Erinn
6 months ago
Surprised that low-risk areas failed so badly!
BE
Beata
6 months ago
I think setting stakeholder expectations is key here.
YA
Yaeko
7 months ago
Definitely need a broader team for risk analysis.
SH
Shonda
7 months ago
I bet the risk analysis team was just a bunch of coin-flippers.
CH
Cherelle
7 months ago
Haha, the project manager should have just used a crystal ball to predict the future!
EA
Earnestine
8 months ago
C) The project manager should have set stakeholder expectations for serious failures.
LE
Leonida
8 months ago
D) Future projects should test the lower risk areas first.
KA
Kanisha
8 months ago
B) A broader cross-functional team should contribute to the risk analysis.
AR
Arlean
8 months ago
I feel like C is important too, but setting expectations might not directly address the failures we saw. I wish we had more examples to clarify this.
BE
Beckie
8 months ago
I’m a bit confused; I thought the lessons learned session was crucial, so A might be the answer. But then again, it could be too late to do that after deployment.
HO
Hoa
8 months ago
I think D makes sense because testing lower risk areas first could prevent serious failures. I feel like we practiced a similar question on prioritizing testing.
NO
Noble
9 months ago
I remember discussing how risk analysis should involve more perspectives, so B seems relevant. But I'm not entirely sure if that's the most important lesson.
LO
Lorean
9 months ago
I think the answer is B. A broader cross-functional team could have provided more diverse perspectives and caught those low-risk failures during the risk analysis. The other options don't seem to address the core issue as directly.
SH
Sheron
9 months ago
I'm a bit confused. Why would testing the lower risk areas first be the solution? Wouldn't that just delay addressing the actual issues? I'm stuck between B and C, but I'm not sure which one is the best answer.
ER
Ernie
9 months ago
I feel pretty confident about this one. The most important lesson is that the project manager should have set better stakeholder expectations. The failures in low-risk areas show that the risk analysis was flawed.
ME
Meghan
9 months ago
Okay, let's think this through. The key seems to be that serious failures occurred in low-risk areas, even though a risk-based approach was used. I'm leaning towards option B - a broader team could have helped identify more risks.
EL
Elizabeth
10 months ago
Hmm, this is a tricky one. I'm not sure if I fully understand the question. Maybe I should re-read it a few times to make sure I'm not missing anything.
LO
Lou
3 months ago
I agree, a broader team could help spot issues earlier.
AD
Adelle
4 months ago
Yeah, low risk doesn't mean no risk!
CA
Carline
5 months ago
This really makes you think about risk assessment.