Pass the APMG-International AgilePM AgilePM-Foundation Questions and answers with ExamsMirror

AgilePM requires continued business justification. The Business Sponsor owns the investment decision and ensures funding remains warranted by expected benefits, value, and risk. If, at any point, the Sponsor cannot justify further funding in business terms—for example, the benefits have diminished, risk has escalated beyond tolerance, or opportunity costs are too high—stopping the project (or pivoting) is sound financial governance. Reports of overspend, lateness, or team dysfunction (options C and D) are important signals, but they trigger re-planning and decision-making; they are not, by themselves, the governance criterion. Architectural opinions (A) do not substitute for business justification. The decisive governance action is to halt funding when the Business Case no longer holds, safeguarding organizational resources.

Statement 1: Correct. Offering supportive feedback after moments of insight reinforces learning and helps individuals process change more effectively.

Statement 2: Incorrect. While talks from experts may inform, they are less impactful than engaging individuals directly.

Key AgilePM Concepts Referenced:

Neuroscience in Change Management: AgilePM Handbook, Chapter 6, Section 6.2.

Statement 1: Correct. Diverse teams leverage different perspectives, leading to higher creativity and innovation, as Agile encourages collaborative solutions.

Statement 2: Incorrect. Diverse teams typically take longer to reach consensus due to varying viewpoints and styles of communication, though the decisions they make are often more robust.

Key AgilePM Concepts Referenced:

Team Collaboration and Creativity: AgilePM Handbook, Chapter 5, Section 5.3.

Statement 1: Incorrect. While accountability is important, it should be addressed constructively, not by drawing attention to failures in a punitive way.

Statement 2: Incorrect. Constructive conflict is essential for innovation and problem-solving. Avoiding conflict entirely can lead to unresolved issues and reduced performance.

Key AgilePM Concepts Referenced:

Team Dynamics and Conflict Management: AgilePM Handbook, Chapter 5, Section 5.5.

Focus on Benefits: Highlighting the benefits of the change makes the desired end state more attractive, increasing buy-in and reducing resistance. This aligns with the Beckhard and Harris change formula, where the perceived benefits of change must outweigh the dissatisfaction with the status quo and the cost of change.

Other Options:

B: Burning platforms address urgency but don’t directly enhance desirability.

C and D: These are practical measures but don’t necessarily increase desirability.

Key AgilePM Concepts Referenced:

Change Formula Framework: AgilePM Handbook, Chapter 6, Section 6.5.

The missing word in the sentence is “Champion”. The Business Sponsor is known as the project Champion because they are committed to the solution and the delivery approach34. This role is crucial as it provides the strategic direction and controls the funding/budget for the project1.

Performing Stage: In this stage, team members work cohesively towards achieving results. Roles and processes are clear, and collaboration is at its peak.

Other Stages:

Forming: Initial setup with limited collaboration.

Storming: Characterized by conflict and role clarification.

Adjourning: Focused on disbanding after tasks are completed.

Key AgilePM Concepts Referenced:

Team Development Models: AgilePM Handbook, Chapter 5, Section 5.4.

 Quality during Evolutionary Development is ensured by continuous verification2. This involves iterative development, where all development processes, including testing, are repeated to ensure the output is complete and able to generate useful feedback2.

AgilePM’s lifecycle comprises Pre-Project, Feasibility, Foundations, Evolutionary Development (Development), Deployment, and Post-Project. Deployment is executed in the Deployment phase, but AgilePM expects deployment planning to be identified early and progressively elaborated as part of ongoing planning during Evolutionary Development. As timeboxes deliver verified increments, the team refines release content, readiness activities, and transition tasks (training, data migration, cutover, support). Embedding deployment activities into the plans during Development ensures that release preparation progresses continuously—not as a late-stage bolt-on—supporting predictable cadence and benefits enablement. While Foundations establishes the initial approach and high-level plans, the detailed, actionable deployment tasks and their scheduling are added and maintained within the Development phase planning cycles so the upcoming Deployment phase can execute smoothly. Hence, from the options provided, the correct choice is Development phase.

AgilePM advocates collaboration as a core value, stressing “working together towards a shared goal.” Competence in collaboration grows in cultures that remove fear, encourage learning, and align on purpose. A no-blame culture fosters psychological safety so issues surface early and teams can inspect and adapt without defensiveness. Asking for help is encouraged through active business involvement and empowered, multi-disciplinary teams; it reduces decision latency and improves quality. Setting clear goals—e.g., business outcomes, Definition of Done, and prioritized objectives—creates shared focus, enabling constructive cooperation and trade-offs. By contrast, rewarding individual efforts tends to optimize locally, fragment accountability, and discourage knowledge sharing; AgilePM favors team-based achievement and collective ownership. Agile guidance repeatedly links effective collaboration with facilitation, frequent reviews/demonstrations, and visible progress measures that are team-centered, not individualized. Therefore, the options that genuinely build collaboration are 2, 3, and 4, making D correct.