Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 39 of 494
Free Preview · 494 of 1,644 · questions 1–494 of 1,644 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
In a changing business environment, the project manager should continuously evaluate whether planned work still contributes to business value and expected benefits. In an agile project, reviewing and reprioritizing the backlog at iteration boundaries provides a regular feedback loop for incorporating market, regulatory, technological, stakeholder, or other external changes. This helps ensure that the team continues delivering the highest-value work rather than implementing backlog items that may no longer contribute to desired business outcomes.
In an Agile project, the product backlog is regularly reviewed and reprioritized based on changing business needs and expected benefits. After each iteration, the team and product owner can assess whether the user stories still provide value. A ❌ — Communication is important, but changing iteration objectives is not the primary way to evaluate product value. B ❌ — Stopping an iteration immediately is an excessive response. C ✅ — Regular backlog reprioritization ensures the product remains aligned with business value and benefits. D ❌ — Pair programming improves code quality but does not identify changes in business value. Therefore, the best answer is C.
In agile projects, the product backlog is a dynamic artifact that reflects the current understanding of business needs and priorities. To address a changing business environment and ensure benefits realization, the project manager should facilitate the continuous reprioritization of the product backlog. This activity, often done between iterations (sprints), involves the product owner and other stakeholders evaluating user stories against current business objectives. This process is the primary mechanism for identifying and adapting to changes, ensuring that the team is always working on the most valuable features, thereby directly supporting the sponsor's concern for benefits realization.