While the definition of a Must Have requirement is clearly defined, the definition of Could Have and Should Have requirements can be less clear.
When, ideally, should the project team discuss and agree some objective criteria for how these requirements will be prioritized?
Comprehensive and Detailed Explanation (paraphrased from AgilePM planning/prioritization guidance):
AgilePM expects teams to establish objective MoSCoW criteria and decision rules during Foundations. Foundations is where the delivery approach, governance, Business Case, scope boundaries, quality expectations, and planning baselines are agreed. Clarifying how Should and Could items will be interpreted (e.g., business value thresholds, regulatory constraints, UX standards, operational readiness factors) avoids later ambiguity, speeds trade-off decisions inside timeboxes, and protects the Business Case. While Feasibility assesses whether proceeding makes sense, and Development executes the timeboxed work, Foundations is the optimal moment to set shared prioritization rules, acceptance criteria structures, and change control protocols so that delivery can proceed predictably while flexing scope responsibly. Hence, C is the correct choice.
Filiberto
6 days agoMaynard
11 days agoKimbery
16 days agoKatlyn
22 days agoLouann
27 days agoWhitney
1 month agoCarline
1 month agoArlyne
1 month agoKarma
2 months agoArt
2 months agoLeonor
2 months agoFlo
2 months ago