Pretty sure it's C. Regularly reprioritizing the backlog after every iteration is exactly how agile teams adapt to changes and keep user stories aligned with business priorities. D sounds more like a coding practice, not a change management approach. Anyone see it differently?
Q: 2
A project manager is working on an agile project in a changing business environment. The project
sponsor is worried about benefits realization
and asks the project manager to pay attention to changes that can affect the project.
Which action should the project manager take to identify changes that may affect the product?
Options
Discussion
C . Revisiting and reprioritizing the backlog after every iteration is classic agile, makes sure business value stays high. D sounds tempting but reacting mid-iteration isn’t typical, more of a trap here.
C/D? Option C matches agile best practices, but D is tempting as a distractor for being responsive.
B for me here. I thought stopping the iteration fast if something critical changes is a good way to handle huge impacts. Maybe I'm overthinking risk though, not sure.
C/D? Saw a similar question in an exam report, can't decide which matches sponsor's concern best here.
I don’t think D is right here. C is what matches agile, since mid-iteration changes are usually a trap option.
Had something like this in a mock, and it's definitely C.
Yeah, it's C here.
Yeah, C works here. Regular backlog reprioritization is how you spot those changing requirements.
C vs D, both mention responding to change but I think D is more immediate.
Be respectful. No spam.
Question 2 of 35