As Sprint 5 comes to an end, the Infrastructure Delivery Team is facing delays due...

A is correct.

In AgilePM, MoSCoW prioritization is used to protect the timebox and preserve delivery of the most important outcomes. A Should Have is important, but it is not essential in the same way as a Must Have . If delivery risk increases, it is valid to reclassify or defer a Should Have, especially where a workable alternative still supports the business outcome.

Why A is best:

it reduces delivery risk,

protects the timebox,

and still preserves some outdoor guest experience through the River Pool Patio workaround.

Why the others are weaker:

B is too broad. Dependencies alone do not automatically justify removal.

C is too restrictive. A Should Have may be deferred when needed to protect time and viability, not only when a Must Have is directly threatened.

D is incorrect because workarounds are not automatically poor practice; they can be sensible agile trade-offs.

So the most AgilePM-aligned answer is A .