Pass the APMG-International AgilePM AgilePM-Practitioner Questions and answers with CertsForce

The correct answer is A .

In AgilePM, early estimates are expected to contain uncertainty. The correct response to stakeholder challenge is not to act defensive, make the numbers appear fixed, or change them just to satisfy opinions. Instead, the Developers should explain that these are early estimates , based on current understanding, and that they will be refined progressively as the project learns more.

Why A is correct:

It sets the right expectation about estimation in AgilePM.

It reinforces that estimates are useful planning tools , not guarantees.

It helps stakeholders understand why refinement is normal and responsible.

Why the other options are incorrect:

B is incorrect because AgilePM does not treat early estimates as fixed commitments.

C is incorrect because estimates should not be manipulated to suit stakeholder preferences. They should reflect the team’s best judgment.

D is good practice and can be helpful, but it is not the strongest answer here. The immediate issue is stakeholder misunderstanding about the nature of early estimates, and A addresses that most directly.

So the best answer is A .

Dividing the work into smaller, well-defined component parts is a strategic approach when dealing with fixed-price contracts within an Agile framework. This method allows for greater flexibility and adaptability, as each component can be specified in detail, making it clear what the external web developer is responsible for delivering. This approach aligns with Agile principles by enabling incremental development and delivery, allowing for adjustments and refinements to be made as the project progresses and more information becomes available.

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.

For the XAN Insurance Company Web Project and considering the Agile Project Management approach, particularly the Dynamic Systems Development Method (DSDM) framework which emphasizes business value and active user involvement, the Business Case should justify the project in terms of cost, benefit, and risk.

Selected Statements for the Business Case:

D. The Sales Manager has calculated that the new coffee shop insurance product will increase revenues by 10% each week.

E. Market research shows that the number of coffee shop patrons taking legal action against retailers has increased by 200% over the past two years.

D. This statement provides a clear financial projection for the benefits of the project, which is a critical component of a Business Case. It quantifies the expected revenue increase, offering a tangible benefit to justify the project investment.

E. This statement outlines a market trend that necessitates the project, highlighting the increased demand for insurance due to rising legal actions against coffee shops. It underscores the relevance and timeliness of the project, adding to the justification for undertaking the project.

Why Other Statements Are Excluded:

A. While high-level functional and non-functional requirements are essential for project planning, they typically belong in project requirements documentation or the Project Brief, rather than the Business Case.

B. This statement provides market insight but does not directly justify the project from a cost-benefit-risk perspective. The relevance of selling Fairtrade products and alcohol to the insurance product project is tangential.

C. The request for a report on past sales provides background information but does not in itself justify the project investment. It might be used to inform the Business Case but is not a direct component of it.

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 .

The best answers are C and D .

C is correct because AgilePM promotes building quality and risk control into the work itself. Adding integration testing to acceptance criteria ensures that relevant items are not considered complete unless the integration risk has been addressed.

D is also correct because including explicit integration test scenarios in the Sprint Backlog makes the risk visible, actionable, and part of planned delivery rather than something left vague or deferred.

Why the others are weaker:

A is not AgilePM-aligned because timeboxes should not be casually extended.

B is too centralized; Sukra’s input matters, but risk handling should be collaborative and embedded in delivery.

E is too late and reactive; integration concerns should be addressed continuously, not saved for the end.

So the correct answers are C, D .

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 .