Exam PMP topic 1 question 100 discussion

An iterative approach makes sense, so understand the rationale, but "initiate the number of iterations" makes no sense. What does that mean? It's either bad sentence structure or just misleading on purpose.

"Initiating iterative cycles to reduce change requests" means starting multiple rounds of evaluation and continuous improvement to ensure that the product or project meets the requirements from the outset. This approach minimizes the need for change requests later on, helping the project proceed more smoothly while reducing potential costs and delays.

Weird wording, but the use of iterative development allows for continuous feedback and adjustments throughout the project. By breaking the project into iterations, the project manager can incorporate changes more smoothly and efficiently, reducing the need for a large number of change requests. Option A suggests reducing the number of approvers, which might not address the root cause of the challenges. Option B proposes requiring sponsor approval for all change requests, which might slow down the project and hinder its adaptability to uncertainties. Option D involves adding a fixed number of change requests to the project baseline, which may not be suitable for innovation projects with high uncertainty.

And they're like, ", Agile is so flexible!"

Looks like C is the anwser but the wording is bad. D is plausible as well but placing limits can be problematic.

"Initiate the number of iterations" -WTF does this even mean?

All answers sound wrong, but I feel like D is the best

C, "Initiate the number of iterations to reduce the number of change requests."

Option c is the only correct

C, "Initiate the number of iterations to reduce the number of change requests." Innovation projects often involve a high level of uncertainty, and it can be challenging to accurately define all requirements and details upfront. In such cases, the project manager can adopt an iterative approach to manage the project effectively. By breaking the project into smaller, manageable iterations, the team can focus on delivering incremental results while continuously learning and adapting based on feedback and changing requirements. Through iterations, the project team can gather valuable insights, test assumptions, and refine the project's direction. This can potentially lead to a reduction in the number of change requests over time as the project evolves based on the gained knowledge and experience.

C. Initiate the number of iterations to reduce the number of change requests

I vote for C

The best answer is C..

Choose C. You can mixed C and D, apply a fixed number of CR in each iteration.

In my opinion, the project manager cannot limit the change requests because that could go against the product value, however, the PM can control the behavior that lead to random changes.

Why C??

Somehow D sounds plausible to me. If somebody is randomly throwing requests in you should limit them to really only get the prioritized change requests but maybe I am wrong here. Answer C I don't understand in regards to the wording "Initiating the number of iterations" ...what does that even mean