Free APMG-International AgilePM-Practitioner Practice Exam with Questions & Answers | Set: 5

D is correct.

In AgilePM, thinking about how benefits will be realized should not be postponed until the final Sprint. Realization planning should be considered early, as part of the project’s business justification and ongoing business thinking, so the solution is built with adoption and benefit delivery in mind from the start.

Why D is correct:

benefit realization should be planned early,

post-launch alignment with guest demand is part of achieving business value,

and waiting until the final Sprint is too late and increases risk.

Why the others are not best:

A is incorrect because Delivery Teams should not ignore realization considerations until the end.

B is incorrect because final-Sprint-only realization planning is too late for AgilePM.

C is partly tempting, but too absolute. Business roles are central to realization, yet delivery teams also contribute. The main issue is timing, not only ownership.

So the best AgilePM answer is D .

==========================

D is correct.

AgilePM emphasizes visible delivery of value , not just activity or effort. Reporting based mainly on effort can create the illusion of progress even when little usable value has actually been delivered.

Why D is correct:

effort does not equal outcome,

stakeholders need visibility of delivered, testable, usable features,

and value-based reporting gives a truer picture of actual progress.

Why the others are incorrect:

A is wrong because effort tracking alone does not create meaningful transparency.

B is wrong because AgilePM values delivery and outcomes more than workload reporting.

C is incorrect because the statement itself is flawed; effort-based reporting does not measure value generated.

In AgilePM, progress should be reported through delivered features, outcomes, and business value, so D is the best answer.

A. Yes, because this will allow the Solution Development Team to focus on the quality of the Solution Development Timebox ' s deliverable as a whole, in order to keep focus on the business need.

Rationale:

Setting acceptance criteria for the overall deliverables of a timebox is a key practice in Agile to ensure that the work meets the business objectives and quality expectations. It helps the Solution Development Team to understand what is required for the deliverables to be considered complete and acceptable. This aligns with the Agile principle of delivering quality and maintaining a constant pace of development. It also ensures that all team members are aligned on the goals and can focus on delivering value in line with business needs.

The correct answer is C .

In AgilePM, VUCA-based risks are those driven by external volatility, uncertainty, complexity, or ambiguity in the environment. New legislation is a classic example of this because it originates outside the project and can force reprioritization, redesign, resource shifts, and rapid adaptation.

In this scenario, the new food hygiene laws are:

external to the project ,

time-bound , since they take effect in six months,

and capable of creating unplanned work , such as kitchen remodeling and resource diversion.

That makes this a VUCA-based risk , not an approach-based one.

Why C is correct:

The key reason is that the trigger is new legislation , which is an environmental change outside the project team’s control. AgilePM recognizes that such external changes can emerge during delivery and require the project to remain adaptable.

The possible impact here includes:

reassessing scope,

reassigning Infrastructure Team capacity,

reviewing compliance obligations,

and potentially adjusting delivery priorities.

That is exactly the kind of situation where AgilePM’s flexibility is valuable.

Why the other options are incorrect:

A. Approach-based, because past Project Increment planning failed to account for regulatory change, causing lack of contingency and resource risks.

This is not the best answer because the scenario does not say the team negligently ignored a known requirement. The key issue is the emergence of new laws , which is primarily an external uncertainty rather than a failure of method.

B. Approach-based, because Sukra Aroon should have tracked evolving legislation from the start to mitigate the risk.

This is also not the best answer. Even though compliance awareness is important, the fundamental source of the risk is still the external regulatory change , not simply Sukra’s handling of it.

D. VUCA-based, because gaps in internal compliance cause uncertainty in responding to changing regulations.

This is weaker than C because it shifts the cause toward an internal gap. The scenario itself emphasizes the introduction of new food hygiene laws , which is the main source of uncertainty and disruption.

AgilePM perspective:

AgilePM is designed to help teams respond to changing external conditions without losing focus on business value. Regulatory changes often require:

rapid reassessment,

collaborative decision-making,

flexible reprioritization,

and attention to compliance without abandoning the overall project goals.

Since this risk is caused by external legislation , the correct classification is VUCA-based .

Therefore, the best answer is C .

B does not align with AgilePM role responsibilities.

Brinda Vyas, as the Business Visionary , is responsible for ensuring the evolving solution remains aligned with the business vision, business need, and expected value. She is an important stakeholder in discussions where compliance, quality, and investment choices may affect viability or business outcomes.

However, AgilePM does not make the Business Visionary personally accountable for financial governance and regulatory governance in the way option B states. Those concerns are shared across other roles, such as:

the Business Sponsor for investment and business justification at the highest level,

the Project Manager for governance coordination and control,

and specialist roles such as Wanida Anong for compliance expertise.

Why the other options are appropriate:

A is appropriate because Brinda should help ensure decisions remain aligned with strategic direction and value.

C is appropriate because Brinda should confirm that compliance and quality expectations do not undermine business viability.

D is appropriate because attending helps Brinda maintain alignment among business stakeholders as the solution evolves.

So the statement that does not provide an appropriate justification is B .

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 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 .

The correct answer is C .

In AgilePM, information radiators such as dashboards are very useful, but they are not sufficient on their own for senior governance and strategic decision-making , especially for a role like the Business Sponsor .

Sarah, as the Business Sponsor , is accountable for ensuring that the project remains viable, aligned with business objectives, and worthy of continued investment. That means she needs more than raw or near-real-time status information. She also needs:

interpretation of what the information means,

context behind risks and issues,

insight into business impact,

understanding of trade-offs,

and confidence that the project is still aligned to strategic goals.

A dashboard can show progress, risks, and actions, but it usually does not fully provide the narrative, business context, rationale, escalations, and decision support that an executive stakeholder needs. AgilePM values transparency, but transparency is not the same as complete understanding.

Why C is correct:

A real-time dashboard is helpful as a supporting mechanism, but it does not fully meet Sarah’s needs because:

strategic stakeholders need context , not just data,

they often need explanation of why something matters ,

they need help understanding whether intervention is required,

and they require communication tailored to business decisions, not just operational tracking.

So the dashboard is useful, but not enough by itself .

Why the other options are incorrect:

A. Yes, because she will have access to progress updates, removing all meeting dependency.

This is incorrect because AgilePM does not suggest that dashboards replace all direct engagement. Communication with senior stakeholders still matters. Meetings, conversations, reviews, and decision forums remain important for clarifying implications and making timely decisions.

B. Yes, because she can rely solely on the dashboard for all her updates.

This is also incorrect. “Solely” is the problem. In AgilePM, relying on only one communication channel is risky, particularly for a sponsor role. Sponsors need summaries, discussions, escalations, and interpretation in addition to visible status information.

D. No, because she will need Hira to compile and present the data in a physical report for sharing.

This is incorrect because AgilePM does not require formal physical reporting as the preferred solution. AgilePM favors timely, transparent, and fit-for-purpose communication , not unnecessary documentation. The problem is not the absence of a physical report; the problem is the need for decision-making context.

From an AgilePM perspective:

AgilePM encourages rich communication , stakeholder engagement, and visible progress tracking. Dashboards are excellent for transparency and ongoing awareness, but executive roles such as the Business Sponsor need communication that supports governance and strategic control. That often includes:

regular reviews,

exception-based escalation,

discussions on risk exposure,

alignment to business case and priorities,

and recommendations from the Project Manager and key business roles.

In this scenario, Hira has done something valuable by introducing a real-time dashboard. However, to truly meet Sarah’s needs, Hira should combine the dashboard with targeted sponsor communication , highlighting key decisions, risks, dependencies, and whether the increment remains aligned to business objectives.

Therefore, from an AgilePM viewpoint, C is the best answer because dashboards support transparency, but they do not on their own provide the full context and insight required for strategic decision-making.

The correct answer is A .

This is an approach-based risk because the core problem is not external uncertainty or unpredictable market behavior. The problem is that the project appears to have delivered the Spa experience, but did not adequately plan for realization of benefits through guest awareness and communication .

In AgilePM, success is not only about building and launching a solution. It is also about ensuring that the delivered capability can generate the intended business value. If guests were unaware the Spa experiences existed, then the issue lies in how the rollout, communication, and benefit realization were planned and executed.

Why A is correct:

The scenario points to a communication failure , not a changing external environment.

Guests did not reject the Spa; many simply did not know it was available .

That means the project should have included clearer realization planning , especially around how guests would be informed, guided, and encouraged to use the new service.

In AgilePM terms, this is a failure in the project approach to enabling business outcomes after delivery.

This is exactly why A is the best answer: it identifies that the project should have planned how the new Spa offering would be communicated so the expected benefits could actually be realized.

Why the other options are incorrect:

B. Approach-based, because marketing and operations should have collaborated during the Foundations phase to ensure Spa experiences were promoted.

This is plausible, but it is not the best answer. It is too narrow and overly tied to the Foundations phase. AgilePM would see this more broadly as a realization planning issue, not just an early-phase collaboration issue. Promotion and guest communication must be actively planned as part of ensuring benefits are achieved, not assumed to be solved only in Foundations.

C. VUCA-based, because guest demographics or preferences change unpredictably making it difficult to predict engagement.

This is incorrect because the feedback does not indicate changing preferences or lack of interest. It specifically says many guests were unaware of the Spa experiences. That is a communication gap, not a VUCA-driven preference shift.

D. VUCA-based because external uncertainty affects how guests discover new services making it difficult to control.

This is also incorrect because the issue is not uncontrollable discovery behavior in general. The project had a direct opportunity to communicate the service more effectively. This points to an internal delivery-and-adoption gap, not an uncontrollable external uncertainty.

AgilePM perspective:

AgilePM emphasizes:

delivering business value , not just outputs,

involving the right stakeholders,

planning for deployment and benefit realization ,

and ensuring the solution is actually adopted and used.

A launched Spa that guests do not know about is a classic example of where the solution exists , but the business benefit is not being realized because the enabling communication and adoption activities were insufficient.

Therefore, the best answer is A .

The correct answer is D .

MoSCoW is specifically designed to manage expectations realistically . It distinguishes between what absolutely must be delivered and what is desirable but negotiable within time and resource constraints.

Why D is not appropriate:

In AgilePM, Must Haves are expected to be delivered.

Should Haves are important, but they are not guaranteed .

Assuming both Must and Should items will definitely be delivered undermines the whole purpose of MoSCoW.

This creates unrealistic business expectations and weakens delivery control.

Why the other options are appropriate:

A is correct because MoSCoW should be used to align backlog priorities with business needs.

B is correct because effective prioritization considers not just value, but also feasibility, dependencies, and risk.

C is correct because prioritization should be reviewed as the project evolves.

AgilePM perspective:

MoSCoW helps teams and stakeholders make informed trade-offs while protecting delivery confidence. It supports:

clarity,

transparency,

realistic expectation setting,

and controlled flexibility.

The inappropriate action is to treat Should Haves as guaranteed outcomes. That would blur the distinction between categories and reduce the usefulness of prioritization.

So the correct answer is D .