APMG-International AgilePM Foundation Exam - Topic 4 Question 63 Discussion

Actual exam question for APMG-International's AgilePM Foundation exam

Question #: 63
Topic #: 4

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?

ADuring the pre-project phase

BDuring the Feasibility phase

CDuring the Foundations phase

DDuring the Development Phase

Show Suggested Answer

Suggested Answer: C

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.

by Ronnie at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium AgilePM Foundation Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Penney

3 days ago

I’m surprised this isn’t more straightforward!

upvoted 0 times

...

Jin

8 days ago

Wait, isn't it too late to prioritize in Development?

upvoted 0 times

...

Ora

13 days ago

Agreed, Foundations is key for setting priorities.

upvoted 0 times

...

Brandon

18 days ago

I think pre-project phase makes more sense.

upvoted 0 times

...

Milly

24 days ago

Definitely during the Foundations phase!

upvoted 0 times

...

Annmarie

29 days ago

I'm going with C) During the Foundations phase. That's when the team can really hash out the details and make sure everyone is on the same page.

upvoted 0 times

...

Art

1 month ago

Haha, I bet the project manager is just going to flip a coin to decide the priorities. Might as well do it during the Development Phase (D)!

upvoted 0 times

...

Filiberto

2 months ago

Definitely A) During the pre-project phase. That's the time to get everyone on the same page and set the foundation for the project.

upvoted 0 times

...

Maynard

2 months ago

B) During the Feasibility phase seems like the best option. That's when the team can really dive into the details and set the stage for the rest of the project.

upvoted 0 times

...

Kimbery

2 months ago

I think the answer is C) During the Foundations phase. That's when the project team should discuss and agree on the criteria for prioritizing requirements.

upvoted 0 times

...

Katlyn

2 months ago

I thought we agreed that the Development Phase is too late to prioritize requirements, but I’m not confident about the earlier phases.

upvoted 0 times

...

Louann

3 months ago

I feel like the Feasibility phase could also be a good time to set those criteria, but I can't recall the specifics we covered.

upvoted 0 times

...

Whitney

3 months ago

I remember a practice question that emphasized the importance of the pre-project phase for aligning on requirements. That might be the right answer.

upvoted 0 times

...

Carline

3 months ago

I think we discussed prioritizing requirements during the Foundations phase, but I'm not entirely sure if that’s the best time.

upvoted 0 times

...

Arlyne

3 months ago

Ah, this is a good one. I'd say the Foundations phase is the ideal time to discuss and agree on the criteria for prioritizing the Could Have and Should Have requirements. That way, everyone's on the same page from the start.

upvoted 0 times

...

Karma

3 months ago

Oof, this is a tough one. I can see arguments for a few of the options here. I think I'm leaning towards the Foundations phase, but the Feasibility phase could work too. Gotta make sure we get those definitions locked down early on.

upvoted 0 times

...

Art

3 months ago

I feel pretty confident about this one. The question is asking when the team should discuss the prioritization criteria, and that seems like it would fit best in the Foundations phase, when you're really nailing down the requirements and how they'll be handled.

upvoted 0 times

...

Leonor

4 months ago

Hmm, I'm a little unsure about this one. The definition of Could Have and Should Have requirements can be tricky, so I think it's important to get that sorted out early on. Maybe the Feasibility phase would be a good time to hash that out?

upvoted 0 times

...

Flo

4 months ago

This one seems pretty straightforward. I'd say the best time to discuss the criteria is during the Foundations phase, when the project team is really getting into the details of the requirements.

upvoted 0 times

...