Free Practice Questions for APMG-International AgilePM-Practitioner Exam

Here the task is to identify which AgilePM principle is most significantly compromised in each case, based on the behavior or concern described.

1. Lee Tan is skeptical about agile ways of working and dismisses Sprint Reviews as a waste of time, creating tension and hindering collective alignment.

Answer: G — Communicate continuously and clearly

Sprint Reviews are a core mechanism for transparency, feedback, shared understanding, and alignment. If Lee dismisses them and creates tension around them, the biggest principle being undermined is continuous and clear communication .

Why not just Collaborate ?

That is also affected, but the most direct issue here is rejection of a structured communication and feedback forum. Sprint Reviews exist to keep business and delivery aligned through ongoing communication.

So the most significantly compromised principle is:

1 → G

2. Priya insists that all aspects of the aromatherapy oil, including packaging and marketing, must be fully defined before development, causing concern among teammates.

Answer: F — Develop iteratively

This directly conflicts with AgilePM’s belief that not everything must be fully detailed upfront. AgilePM supports evolving detail over time through learning, feedback, and iteration.

Priya’s position reflects a predictive mindset: define everything first, then build. AgilePM instead encourages starting from sufficient understanding and refining as the team learns more.

So the most significantly compromised principle is:

2 → F

3. Lee Tan is reluctant to release operational staff to act as Business Advisors for the Spa’s booking system, prioritizing short term efficiencies. He assumes business requirements are obvious and Developers can proceed without direct business input.

Answer: A — Focus on the business need

This is a strong violation of the principle of focusing on the business need . AgilePM depends on active business involvement to ensure that what is delivered genuinely meets operational and strategic needs.

If operational staff are not made available as Business Advisors, the team risks building a solution based on assumptions rather than real business understanding. That undermines the ability to ensure the solution is fit for business purpose.

Why not Collaborate ?

That is involved too, but the core failure is the assumption that delivery can proceed without direct business input. That most fundamentally threatens alignment to the real business need.

So the most significantly compromised principle is:

3 → A

4. Many Delivery Team members in Spa operations, marketing, and IT are part-time and their daily responsibilities are taking priority over project roles. Their limited availability raises concerns about meeting Sprint commitments.

Answer: B — Deliver on time

This concern most clearly threatens the AgilePM principle of delivering on time . If part-time participation and competing priorities reduce team capacity, Sprint commitments become unreliable and timeboxes are put at risk.

AgilePM places strong emphasis on protecting time and using prioritization and commitment to ensure timely delivery. If people are not sufficiently available, timely delivery becomes difficult.

Why not Demonstrate control ?

That could also be affected, but the scenario explicitly points to concern about meeting Sprint commitments, which most directly maps to delivery timeliness.

So the most significantly compromised principle is:

4 → B

5. IT developers worry that testing critical booking system integrations can only happen at the end of the Project Increment, rather than being embedded within each iteration.

Answer: D — Never compromise quality

This most directly undermines never compromise quality . AgilePM expects quality to be built in throughout delivery, not deferred until the end. Leaving critical integration testing until the end increases the risk of defects, surprises, rework, and unstable delivery outcomes.

Testing should be integrated into the iterative process so that quality is assessed continuously and problems are found early.

Why not Develop iteratively ?

Iterative development is also relevant, but the main concern here is not iteration itself. It is that quality assurance, especially critical integration testing, is being postponed. That most clearly violates the principle of protecting quality.

So the most significantly compromised principle is:

5 → D

The correct answer is A .

AgilePM supports progressive estimation , and relative estimation is one of the best ways to do that. It allows the Developers to provide useful estimates early without pretending to have a level of precision that is unrealistic at this stage.

Why A is correct:

Relative estimation is well suited to AgilePM because it supports early forecasting .

It accepts uncertainty while still giving the project enough information for planning.

Estimates can then be refined later as more detail emerges.

This fits AgilePM’s balance between:

planning and adaptability,

usefulness and realism,

and early direction without false precision.

Why the other options are incorrect:

B is incorrect because estimating everything in precise hours and days too early creates false certainty and is not consistent with AgilePM’s iterative approach.

C is weaker because although higher-priority work often gets more attention, AgilePM still needs a workable overall view of scope and effort. Ignoring lower-priority items entirely is not the best guidance.

D is incorrect because AgilePM does not say estimation is impossible in uncertain environments. It says estimation should be practical, transparent, and proportionate.

So the best answer is A .

The correct answers are B and C .

During the Foundations phase in AgilePM, the goal is not to fully specify everything in exhaustive detail. Instead, the aim is to establish enough shared understanding, scope, priorities, feasibility, and estimating confidence so the project can proceed sensibly.

Why B is correct

“Host a stakeholder workshop to prioritize integrating the Spa into the resort experience.”

This is strongly aligned with AgilePM because Foundations emphasizes:

collaboration,

shared understanding,

business engagement,

and early prioritization.

A stakeholder workshop helps clarify what matters most, align the increment with the business vision, and ensure the work is focused on delivering value.

Why C is correct

“Develop high-level estimates of effort and cost for Spa facilities and IT systems.”

This also aligns well with AgilePM. In Foundations, estimates should be:

useful,

proportionate,

and appropriate to the current level of knowledge.

High-level estimates are exactly what AgilePM expects at this stage. They help planning and viability assessment without pretending to offer premature precision.

Why the other options are not the best answers

A is incorrect because it pushes toward a fixed, fully analyzed specification, which is not AgilePM’s approach.

D may be useful in a general sense, but it is not as directly aligned with defining and estimating work as B and C.

E is too detailed for Foundations. Work should be defined enough to begin sensibly, but not fully elaborated into detailed design-ready form across everything.

So the best answers are B, C .

The correct answer is C .

In AgilePM, estimation is important, but it is understood that estimate precision evolves as the project progresses . Early in the project, there is less information available, so estimates are naturally broader. As delivery continues and more is learned, estimates can be refined and become more reliable.

This reflects a core AgilePM idea:

estimates should be fit for purpose ,

based on the information currently available,

and improved progressively as understanding increases.

Why C is correct:

AgilePM does not reject estimation.

AgilePM does not expect perfect certainty at the start.

AgilePM accepts that early estimates may be less precise, but they must still be honest, useful, and as accurate as reasonably possible .

Why the other options are incorrect:

A is incorrect because AgilePM does not avoid estimates. Estimation is needed for planning, prioritization, forecasting, and decision-making.

B is incorrect because AgilePM does not require maximum detail from the start. That would waste effort and conflict with iterative learning.

D is incorrect because estimates should be revisited when understanding changes, not only when stakeholders object.

So the best AgilePM answer is C .

The correct answers are C and E .

This is a classic business availability and decision-latency risk in AgilePM. The problem is not just that Brinda is absent. The bigger issue is that the Business Visionary input is missing at a time when strategic adjustments are affecting delivery decisions . That creates a real risk of:

misalignment with the project vision,

unnecessary assumptions,

frustration in the Delivery Teams,

and costly rework.

AgilePM relies heavily on active business involvement . When a key business role becomes unavailable, the right response is to restore decision-making guidance quickly and protect the teams from working blindly on uncertain items .

Why C is correct

“Hira should engage other business stakeholders to assume Brinda Vyas ' responsibilities to ensure the Delivery Teams receives strategic guidance.”

This aligns strongly with AgilePM.

Hira, as Project Manager, should act to restore the missing business guidance by coordinating with suitable business stakeholders who can temporarily support or cover the gap. AgilePM does not encourage leaving teams without access to strategic direction. It also does not assume that work should continue normally when a key business authority is unavailable.

This response is good because it:

maintains business engagement,

reduces decision delays,

protects alignment with the vision,

and helps the Delivery Teams continue with informed guidance.

In AgilePM, if a critical role is unavailable, the project should adapt so the necessary business input remains accessible.

Why E is correct

“The Delivery Teams should focus on backlog items with clear business direction and pause tasks that require Brinda Vyas ' input until guidance is available.”

This is also very AgilePM-aligned.

It is a practical risk response that avoids reckless progress based on guesswork. Teams should keep moving where the direction is already clear, but they should avoid pushing ahead on items that depend on missing strategic clarification.

This balances:

maintaining momentum,

avoiding unnecessary delay across all work,

and reducing the risk of rework on unclear items.

That is exactly the kind of sensible, adaptive delivery behavior AgilePM supports.

Why the other options are incorrect

A. Continue increment work based on the backlog, assuming adjustments can be made when Brinda Vyas returns.

This is not a good AgilePM response because it normalizes working with outdated or incomplete strategic guidance. If recent strategic changes have not been communicated, continuing as normal increases the risk of building the wrong thing.

B. Mira Bachar and the Delivery Teams should document assumptions behind decisions and continue progress without validation.

Documenting assumptions is better than ignoring them, but continuing without validation is still too risky in this scenario. AgilePM values transparency, but it does not support knowingly progressing on uncertain strategic assumptions when better escalation and stakeholder engagement are possible.

D. Hira should escalate to Sarah Lark, the Business Sponsor, to replace Brinda Vyas with another qualified Business Visionary.

This may become necessary if the absence is prolonged or the project is materially threatened, but it is too strong as the best immediate response here. AgilePM would first look to restore business guidance through practical engagement and controlled work selection before moving to formal replacement.

AgilePM perspective

AgilePM expects:

active and timely business input,

collaborative response to risks,

continued delivery where direction is clear,

and escalation or substitution when critical decision-making is missing.

So the best way to handle this risk is to:

restore business guidance through other suitable stakeholders , and

limit work to items that have clear direction until ambiguity is resolved .

Therefore, the correct answers are:

C, E

The correct answer is C .

The key issue here is alignment with the business vision . The Eco-Spa is positioned as a natural, sustainable, mineral-rich wellness experience closely connected to the environment. Adding chlorine may solve one problem, but it risks undermining the core guest promise and the natural quality of the hydrotherapy experience.

Why C is correct:

It recognizes that hygiene and safety matter.

It also recognizes that the proposed solution may conflict with the intended product vision.

AgilePM expects the team to balance business need, user value, technical feasibility, quality, compliance, and vision alignment .

Therefore, rather than immediately accepting chlorination as a Must Have, the team should explore alternative hygiene methods that preserve the natural mineral experience.

Why the other options are incorrect:

A sounds plausible, but it assumes chlorination is the right answer before exploring whether it fits the vision or whether acceptable alternatives exist.

B is too absolute. Not all spa pools must necessarily use chlorine in the same way, and AgilePM would not support such blanket reasoning without considering context and alternatives.

D is clearly wrong because hygiene cannot be deferred until after launch if it affects safety or compliance.

AgilePM perspective:

AgilePM emphasizes fitness for business purpose . A requirement is not truly valuable if it damages the very experience the project is meant to create. The correct response is to preserve both:

guest safety and hygiene,

and the Eco-Spa’s natural, sustainable identity.

So the best answer is C .

B does not align with AgilePM’s MoSCoW prioritization.

In AgilePM, Must Have requirements are the ones that are absolutely essential. If a Must Have is missing, the solution is not viable because it may be unusable, unsafe, non-compliant, or fail to deliver its core purpose.

A Should Have requirement is important, but it is not mandatory for the increment to be considered successful . It adds significant value, and the team aims to deliver it if reasonably possible, but the solution can still be successful without every Should Have being included.

Why the other options align:

A is correct because it accurately describes a Must Have.

C is correct because Could Haves are desirable but only delivered if time and capacity permit.

D is correct because Won’t Have this time items are deliberately excluded from the current increment and may be revisited later.

AgilePM perspective:

MoSCoW is used to protect delivery confidence and business clarity. It helps teams and stakeholders distinguish between:

what is essential,

what is important,

what is desirable,

and what is deferred.

The error in B is that it treats Should Have as if it were equivalent to Must Have , which is not how AgilePM defines the category.

So the correct answer is B .

The correct answers are C and E .

AgilePM estimation should be:

collaborative,

proportionate,

realistic,

and open to refinement.

Why C is correct

“Allow flexibility and accept uncertainty in estimates that may be refined later.”

This is central to AgilePM. Estimates are expected to evolve as understanding improves. Early estimates are not fixed promises; they are informed forecasts based on current knowledge.

Why E is correct

“Use team-based estimation techniques as collective knowledge will improve accuracy.”

This also aligns strongly with AgilePM. Estimation benefits from the combined knowledge of the team because different people understand different aspects of the work, risks, and dependencies.

Why the other options are incorrect

A is too detailed and heavy for the likely stage and context.

B is wrong because Planning Poker supports relative/team-based estimation, but not “precise” early certainty.

D is contrary to agile estimation. Estimates are not meant to be fixed and artificially precise.

So the best answers are C, E .

B is correct.

In AgilePM, planning is most effective when it includes the people closest to delivery. Delivery Team Leaders bring practical insight into:

current progress,

risks and blockers,

dependencies between teams,

feasibility of commitments,

and likely delivery impacts.

That makes their attendance appropriate and useful in a Project Sprint Planning Event.

Why the others are not best:

A is too strong. AgilePM supports collaboration, but it does not “mandate” joint decision-making in that exact wording.

C is incorrect because planning is part of effective delivery, not separate from it.

D is incorrect because excluding Team Leaders would reduce transparency and planning quality.

AgilePM favors collaborative planning with the right delivery voices present, so B is the best answer.