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

The two individuals most suitable for the role of Workshop Facilitator would be:

A. Team Leader E. Project Manager

The rationale for choosing these individuals is that both the Team Leader and the Project Manager are likely to have the necessary skills to facilitate a workshop effectively. They are typically trained to manage team dynamics, guide discussions, remain neutral, and drive towards a resolution. The IT Operations Manager and the Marketing Director are parties to the disagreement and thus would not be appropriate as facilitators due to the potential for bias. The Software Developer is likely to be more involved in the technical aspects rather than facilitation.

In applying Agile Project Management to the creation of an Outline Business Case in support of the Feasibility Assessment, the following two statements are most appropriate:

B. Enough description of the required refurbishment work should be provided to enable the Architecture Angels ' Finance Director to decide whether the project should proceed.

Agile approaches favor providing just enough detail to make informed decisions without going into unnecessary depth at early stages. This allows for flexibility and adaptation as more information becomes available.

C. During Feasibility, potential beneficiaries of the project should be involved when the Outline Business Case for the refurbishment is created.

Agile methodologies emphasize stakeholder engagement and user involvement early and throughout the project. This ensures that the project delivers value and meets the needs of those it is intended to benefit.

C. No, because by the end of Foundations the quality expectations and overall acceptance criteria for at least the first increment should have been set, and high-level acceptance criteria set for later increments.

Rationale:

In Agile Project Management, it ' s important to establish high-level acceptance criteria early in the project to guide development and ensure that the solution meets the business needs and quality expectations. The Foundations phase is when the project ' s scope, objectives, and methods are defined, including the acceptance criteria for the first increment and at a high level for subsequent increments. This ensures that everyone has a clear understanding of what " done " looks like before development begins, reducing the risk of misalignment and rework.

The correct answer is A .

AgilePM values estimation, but it also values proportionality . Estimating should help planning and decision-making, not become a heavy exercise that delays progress and creates unnecessary documentation.

Why A is correct:

Estimates should be accurate enough for the planning purpose at hand.

Teams should avoid excessive refinement when the extra effort gives little added value.

AgilePM encourages “just enough” detail, not exhaustive analysis.

This question highlights a common anti-pattern:

too much time spent estimating,

too much documentation,

and too little focus on actual delivery.

Why the other options are incorrect:

B is incorrect because trying to eliminate all uncertainty is unrealistic and contrary to AgilePM thinking.

C is incorrect because although early estimates may be broad, refinement is still useful later when more information becomes available.

D is incorrect because documenting every assumption in detail is excessive and not agile.

So the best answer is A .

The best answers are A and B .

A is correct because AgilePM depends on active business involvement . If Mira sees a mismatch between intended outcomes and delivered increments, she should increase her availability to clarify needs, answer questions, review progress, and provide timely feedback.

B is also correct because clear acceptance criteria and practical examples reduce ambiguity and help the Delivery Teams understand what “done correctly” looks like for each Backlog item.

Why the others are weaker:

C is too document-heavy and not aligned with AgilePM’s lightweight, collaborative approach.

D adds translation layers instead of improving direct collaboration and clarity.

E is about estimation, not about resolving misunderstanding between need and delivered outcome.

So the correct answers are A, B .

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 .

The correct answers are A and C .

Aromatherapy oil sales are a new idea outside the original scope , so AgilePM would handle this through collaborative assessment and prioritization , not automatic acceptance or unnecessary bureaucracy.

Why A is correct

“Hold a workshop to assess feasibility and document assumptions.”

This fits AgilePM very well because new ideas should be:

explored collaboratively,

assessed for feasibility and impact,

discussed across business and technical roles,

and understood before being committed.

A workshop is an agile way to bring together the right perspectives quickly.

Why C is correct

“Use MoSCoW prioritization to determine its importance against existing objectives.”

This is also fully aligned with AgilePM. Once the idea is understood, it should be assessed against:

current business goals,

existing priorities,

available time and capacity,

and the likely value it contributes.

MoSCoW is the right mechanism for deciding whether it belongs in the current increment or later.

Why the other options are incorrect

B is too hasty. Alignment with vision alone does not mean the item should be added immediately.

D is too heavyweight for this kind of incremental scope discussion.

E is too dismissive. AgilePM does not say new ideas must always wait until after delivery.

So the best answers are A, C .

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 statement that does NOT comply with AgilePM is H .

In AgilePM, the Project Manager does play an important coordination and leadership role, but reviewing Sprint Backlogs each Sprint to check and focus priorities is not the right expression of that responsibility. Prioritization is primarily driven by the business roles , and the detailed Sprint-level backlog is typically managed much closer to the Delivery Team level.

Why H is incorrect:

Priorities are not owned by the Project Manager alone. They are shaped by business need and value, usually through the relevant business ownership roles.

The Sprint Backlog is a detailed delivery artifact used by the team to organize and execute work during the Sprint.

Hira can support coordination, visibility, dependency management, and escalation, but she should not be positioned as the person who reviews Sprint Backlogs in order to “focus priorities” each Sprint as though that were her core responsibility.

That wording shifts too much control toward the Project Manager and away from the empowered team and business-led prioritization model that AgilePM supports.

Why the other options are compliant:

A. Brinda Vyas owns and communicates the project vision, ensuring everyone understands how they contribute to the business goals.

This aligns well with the Business Visionary role. AgilePM expects the vision to be clearly owned and communicated.

B. Brinda Vyas resolves business-related conflicts and needs to be sufficiently available so Delivery Teams can move forward without delay.

This is also aligned. Business leadership must be engaged and available enough to avoid delays in clarification and decision-making.

C. Developers collaborate with each other and Sukra Aroon who ensures technical integrity of the solution, that it meets agreed priorities.

This is broadly aligned. Developers collaborate on delivery, and the Solution Architect safeguards technical coherence and integrity. The “agreed priorities” part is driven by the wider project context, but the statement is still generally consistent with AgilePM collaboration.

D. Developers provide consensus-based estimates to support effective planning and prioritization.

This fits AgilePM well. Delivery teams are closely involved in estimating because they are best placed to judge effort and feasibility.

E. Mira Bachar ensures business needs are clear and prioritized so the Delivery Teams can deliver maximum value.

This is consistent with the Product Owner-style responsibility of clarifying and prioritizing business needs.

F. Mira Bachar collaborates with Brinda Vyas, Sukra Aroon, and Hira to balance business priorities, technical feasibility and delivery constraints.

This strongly aligns with AgilePM’s collaborative approach across business, technical, and management roles.

G. Hira ensures effective collaboration between everyone and removes blockers.

This is a good AgilePM description of the Project Manager’s facilitative role.

AgilePM perspective:

AgilePM promotes:

business-led prioritization

empowered delivery teams

facilitative project management

collaborative dependency handling

clear role boundaries

A Project Manager should support transparency and coordination, but not take over detailed Sprint backlog control in a way that weakens team empowerment or business ownership of priorities.

Therefore, the statement that does not comply with AgilePM is H .