Exam PMI-ACP topic 1 question 31 discussion

The high-risk and high-value features are prioritized and vice versa.

When prioritizing features to be delivered in an iteration, an agile team should defer work on low-risk and low-value items. This approach ensures that the team focuses on delivering the most valuable and impactful features first, while minimizing risk.

High value and high risk features should be prioritized, then high-value low-risk, finally low-value and low-risk.

B is correct

Option B aligns with Lean principles, specifically the concept of value stream mapping, which is used to visualize the steps involved in delivering value to the customer and identify opportunities for improvement. By reviewing the process value stream, the agile team can analyze the efficiency of the current process activities and identify areas where improvements can be made to enhance efficiency and effectiveness.

B is correct. "Defer work on all low-value features, especially those that are also high risk." https://www.linkedin.com/pulse/agile-planning-prioritization-desirability-borjan-petreski

B for sure

High Risk High value can't be deffered.

high risk means, making mistakes and learning if there is any challenge in it.

C is the Correct Answer

B. High-risk and low-value. Explanation: The goal in Agile is to deliver the most valuable features as early as possible and to tackle risks while doing so. Thus, features that are high-risk and high-value should not be deferred but tackled head-on. On the contrary, features that are high-risk and low-value don't provide enough value to justify the associated risk, so these should be deferred or even avoided. Low-risk and high-value features (Option D) are desirable as they give the team valuable output with minimal risk. Low-risk and low-value features (Option C) could be deferred or might be tackled as time and resources allow, but they wouldn't be a first priority. Remember, the goal is to provide the maximum value with minimal risk, and the team should focus on high-value work first. The risk is considered to ensure that potential problems are dealt with sooner rather than later.

When prioritizing features to be delivered in an iteration, an agile team should defer work on low-risk and low-value features. Therefore, the correct option is C. Low-risk and low-value. Agile teams should prioritize high-risk and high-value features to be delivered first, followed by low-risk and high-value features. Low-risk and low-value features should be considered for deferral to future iterations, as they are not critical to the success of the project and can be postponed to focus on more important items.

A = high priority - do first B = low priority - avoid / defer (correct) C = medium priority - do last D = medium priority - do second

C is correct. https://university.hygger.io/en/articles/2399041-value-vs-risk-model

C, low risk & low value = do last ==> defer It's not B because high risk & low value = avoid

I believe the correct answer is B. The item with the lowest value and high-risk is the worst in the product backlog. What it means is that there are many risks involved with the item, but the value earned is very little. It is not worth the risk, where value driven is less than what it costs to mitigate risks.

B High-risk and low-value