APMG-International Updated AgilePM-Practitioner Exam Questions and Answers by zak

The Facilitator should invite the following two individuals to participate in the Workshop:

D. IT Operations Manager (Solution Development Team) E. Marketing Director (Business Visionary)

The rationale for this selection is that the disagreement is between the Marketing Director, who wants the reservation system to have professional photos and video tours (which impacts how the system will be used by potential customers and affects marketing strategy), and the IT Operations Manager, who is concerned with the system ' s technical limitations and maintenance. Both of these individuals are key to resolving the issue at hand, as they represent the conflicting requirements that need to be reconciled for the project to move forward.

The correct answers are A and E .

In AgilePM, effective risk management depends on shared responsibility, continuous awareness, and proactive behaviour across the whole team. Risk is not something handled only by one role, one document, or one event. It is woven into the way the team works every day.

Why A is correct

“Team members should adopt a collaborative mindset, sharing responsibility for identifying and mitigating risks.”

This aligns strongly with AgilePM. Risks emerge from many areas:

business priorities,

technical feasibility,

compliance,

dependencies,

stakeholder engagement,

and delivery constraints.

Because of that, the best way to manage risk is for the team to work collaboratively and raise concerns early. Different people see different risks:

Mira may see value or prioritization risk,

Sukra may see architecture or integration risk,

Hira may see coordination or dependency risk,

Wanida may see compliance risk,

Developers may see delivery feasibility risks.

AgilePM encourages a culture where risks are surfaced openly and addressed together rather than left to a single person.

Why E is correct

“Risk management should be proactive and part of daily activities, not a separate process.”

This is also a core AgilePM principle. Risk management is most effective when it is:

continuous,

visible,

built into team discussions,

and handled as part of normal delivery activity.

That means risks should be considered during:

planning,

backlog discussions,

reviews,

daily collaboration,

dependency conversations,

and stakeholder feedback.

AgilePM does not treat risk as something only reviewed in occasional formal meetings. The team should be alert to emerging issues and respond before they become major problems.

Why the other options are incorrect

B. Hira should have sole responsibility for managing all risks with clear accountability.

This is incorrect. Hira, as Project Manager, has an important role in coordinating risk management, but AgilePM does not place all risk responsibility on one person. Risk management is shared across business, technical, and delivery roles.

C. Developers should resolve all risks collaboratively and promptly without escalation.

This is incorrect because some risks should be escalated. AgilePM encourages teams to resolve issues at the right level, but not to avoid escalation when broader decisions, sponsorship, governance, or cross-team intervention are needed.

D. Sukra Aroon should handle all technical risks independently to ensure the solution is fit for purpose.

This is incorrect because even technical risks often require collaboration. Sukra contributes architectural leadership, but technical risks may affect priorities, cost, compliance, usability, and business outcomes, so they should not be handled in isolation.

AgilePM perspective

AgilePM supports team behaviour where:

everyone is alert to risk,

risks are discussed early,

people collaborate across roles,

escalation happens when needed,

and risk thinking is part of everyday delivery.

So the two statements that best describe appropriate team behaviour for effective risk management are:

A, E

The correct answer is E .

This option best aligns with AgilePM because the Foundations phase is specifically intended to build a shared understanding of the project’s vision, scope, priorities, feasibility, and approach before detailed delivery progresses. AgilePM strongly encourages early collaboration among key business, technical, and delivery stakeholders so that everyone understands what the project is trying to achieve and what success looks like.

In this scenario, the workshop’s purpose was to define and align on what would be available for guests at the end of Project Increment 4 . That is exactly the kind of outcome AgilePM supports through collaborative workshops in Foundations. Co-creating the vision is appropriate because it helps ensure:

the business vision is understood consistently,

delivery expectations are realistic,

technical feasibility is considered early,

stakeholder perspectives are incorporated,

and the teams gain commitment to shared goals.

Why E is correct:

AgilePM places high value on:

active business involvement ,

facilitated workshops ,

collaboration between business and technical roles ,

and shared ownership of understanding , even when accountability for the vision sits with specific business roles.

Brinda, as the Business Visionary , is responsible for setting and safeguarding the vision. But AgilePM does not mean she should define everything in isolation. Instead, the vision should be socialized, explored, clarified, and aligned collaboratively so the wider team understands how to translate it into delivery.

This is particularly important here because the Eco-spa initiative spans:

infrastructure,

guest operations,

wellness experiences,

sustainability,

local traditions,

and service delivery.

A workshop involving business and delivery roles is therefore fully in line with AgilePM.

Why the other options are incorrect:

A. Mira Bachar ' s attendance was valid, because the Product Owner ensures Delivery Teams deliver value and stay on schedule.

This is not the best answer. Mira’s attendance was indeed valid, but the explanation is weak because “staying on schedule” is not the core reason. Her primary contribution is around value, priorities, and business alignment, not schedule control. Also, option E is broader and more fundamentally aligned with AgilePM principles.

B. Mira Bachar ' s attendance was valid, because the Product Owner resolves technical and design conflicts.

Incorrect. Technical and design conflicts are not primarily the Product Owner’s responsibility. Those matters are more aligned to the Solution Architect and technical contributors.

C. Sukra Aroon ' s attendance was unnecessary, because the Solution Architect is only needed during development.

Incorrect. The Solution Architect is highly relevant during Foundations. Early architectural and feasibility input is essential to avoid unrealistic assumptions and later rework.

D. Sukra Aroon ' s attendance was unnecessary, because technical discussions should be separate from solution planning to avoid overcomplicating.

Incorrect. AgilePM supports integrating technical insight into early planning and vision alignment, not separating it away. Business and technical collaboration is a core strength of the method.

F. Co-creating the vision was necessary, because AgilePM requires full solution design in Foundations.

Incorrect. AgilePM does not require full solution design in Foundations. Foundations is about establishing enough understanding and structure to proceed sensibly, not completing exhaustive design upfront. AgilePM favors evolving detail progressively.

G. Hira should NOT have facilitated, because Brinda Vyas should lead all project vision discussions.

Incorrect. While Brinda owns the business vision, Hira as Project Manager can absolutely facilitate workshops to help stakeholders collaborate effectively. Facilitation is a strong AgilePM behavior for a Project Manager.

H. Hira should NOT have facilitated, because a Project Manager only schedules and tracks progress.

Incorrect. This is contrary to AgilePM. A Project Manager in AgilePM does much more than scheduling and tracking. The role includes coordination, stakeholder engagement, governance support, facilitation, and helping maintain alignment across the project.

AgilePM perspective:

AgilePM encourages using workshops in Foundations because they:

accelerate shared understanding,

expose assumptions and risks early,

promote stakeholder buy-in,

support realistic scoping,

and connect business goals to delivery capability.

So the most AgilePM-aligned observation is not about excluding certain attendees or narrowing role boundaries too strictly. It is that co-creating the vision through early collaboration is appropriate and valuable .

Therefore, the correct answer is E .

The correct answer is C .

In AgilePM, the strongest way to combine agile leadership with practical delivery control is to create direct collaboration between the Delivery Teams around the work that must fit together. In this case, the Spa infrastructure team and the Spa operations/treatments team are working on interdependent outputs. The best way to keep those outputs aligned is for the teams to agree shared acceptance criteria for the items that depend on one another.

That makes C the best answer because it is both:

agile in leadership style , since it empowers the teams to collaborate and define quality expectations together, and

practical in execution , since shared acceptance criteria give both teams a concrete basis for building compatible deliverables.

For example, if a hydrotherapy treatment is planned, the infrastructure team and treatment team may need shared criteria covering:

space layout,

water systems,

safety controls,

guest flow,

environmental standards,

equipment readiness,

and operational usability.

Without this shared definition, one team could deliver something technically complete but not actually usable by the other.

Why C is correct from an AgilePM perspective:

AgilePM supports:

collaboration across roles and teams ,

shared understanding of requirements and outcomes ,

fitness for business purpose ,

early clarification of dependencies ,

and empowered teams working within a coordinated framework .

Shared acceptance criteria are a very effective mechanism because they:

turn vague alignment into clear, testable expectations,

expose dependency risks early,

reduce rework,

improve communication across teams,

and help ensure the integrated solution works as intended.

Why the other options are less suitable:

A. Empower Team Leaders to resolve dependencies, escalating major issues to Sukra for a solution-wide view if needed.

This is reasonable, but it is not the best answer. It relies on “Team Leaders” rather than direct team collaboration, and it focuses more on escalation management than on creating a shared working agreement. AgilePM prefers empowering the teams themselves and resolving dependencies through collaboration as close to the work as possible.

B. Empower Team Leaders to independently handle alignment through informal discussions, documenting key decisions for later review.

This is weaker because “informal discussions” alone are too loose for managing important inter-team dependencies. Alignment needs something more concrete than conversations that are only documented afterward.

D. Encourage Delivery Teams to define shared acceptance criteria for interdependent deliverables and Brinda approving.

This is close, but the addition of Brinda approving makes it less agile. Brinda, as Business Visionary, is important for vision and business alignment, but she should not be drawn into approving detailed inter-team acceptance criteria unless there is a specific business reason. This risks slowing down delivery and reducing team empowerment.

E. Hold a joint Retrospective after each Sprint to review alignment and identify remedial actions to ensure alignment.

Retrospectives are valuable, but this is mainly reactive . It helps improve after issues appear, whereas shared acceptance criteria help prevent misalignment before or during delivery.

F. Hold a joint Retrospective after each Sprint so Team Leaders can share learning and provide feedback.

Again, useful but not the strongest answer. It supports learning, but not direct practical alignment of interdependent deliverables.

G. Use hierarchical reporting where decisions would be documented collaboratively between Brinda Vyas, Mira Bachar, Hira and Sukra Aroon.

This is not very AgilePM-aligned because it introduces a more bureaucratic reporting structure. AgilePM favors collaboration and timely decision-making over hierarchical control.

H. Use hierarchical reporting where changes can be escalated and approved quickly allowing the Delivery Teams to progress.

This is also too command-and-control in style. Agile leadership aims to reduce unnecessary hierarchy and enable teams to work together effectively, not depend on approval chains as the main coordination mechanism.

AgilePM perspective:

This question is really about balancing two needs:

leadership through empowerment and collaboration , and

practical governance through clear quality expectations .

Option C does both. It avoids excessive control, but it also avoids vague coordination. It gives the teams a practical tool to align their work while maintaining agility.

Therefore, the best AgilePM answer is C .