The risk profile of a project has increased beyond the upper threshold of tolerance. The product owner and project leader meet to discuss an approach for dealing with this. What should the team do next?
A.
Add risk mitigation tasks to the backlog, then prioritize in current and upcoming sprints
B.
Add risk mitigation time to each requirement
C.
Apply the 80/20 rule, reserving 20 percent of each sprint's capacity for risk mitigation
D.
Hold all risks until they become issues, then add issue resolution tasks to the product backlog
Option A.
Add risk mitigation tasks to the backlog, then prioritize in current and upcoming sprints. This aligns with the Agile principle of "Welcome changing requirements, even late in development" and the Agile practice of "Continuous planning and risk management." When risks exceed the upper threshold of tolerance, the team should add risk mitigation tasks to the product backlog and prioritize them alongside other product requirements. This approach enables the team to address risks in a proactive and ongoing manner, rather than waiting for risks to become issues. Additionally, prioritizing risk mitigation tasks helps the team to allocate resources effectively and focus on delivering the highest value product features while mitigating risks.
A is correct.
You never wait for risks to become issues. Once the risks are identified, a mitigation plan/response is put in place to avoid the risk from materializing, or you plan a mitigation strategy to reduce the impact of the risk. YOU NEVER WAIT FOR THE RISK TO MATERIALIZE; you try your best to come up with a strategy to reduce the probability of the risk.
And OfCourse, the team needs to prioritize the identified risks. You need to handle risks that will affect your sprint goal for the current sprint and then again for future sprints.
A is the answer, to brief the reason why : The product backlog is a tool for accommodating change within
the project. Being able to add changes to the product backlog and
reprioritize requirements regularly helps turn the traditional risk
associated with scope changes into a way to create a better
product.
Keeping the requirements and the priorities on the product backlog
current helps ensure that the development team works on the most
important requirements at the right time.
This section is not available anymore. Please use the main Exam Page.PMI-ACP Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
zvasanth1
Highly Voted 4 years, 2 months agoNervys
Most Recent 10 months, 2 weeks agoImrangoshi
1 year, 1 month agoPetrevski
1 year, 5 months agoMinhha3
1 year, 6 months agoSmokeyofficiial
1 year, 7 months agoInvisibleBeing
1 year, 9 months agoInvisibleBeing
1 year, 9 months agorichck102
2 years, 3 months agoJackNguyenvn
2 years, 7 months agoAlaaradwan
3 years, 3 months agoSARS
3 years, 8 months agosnow5
3 years, 11 months agotsangckl
4 years ago