APMG-International Updated AgilePM-Foundation Exam Questions and Answers by vihaan

In Agile Project Management (AgilePM/DSDM), the control philosophy recognizes that you cannot fix time, cost, quality, and features simultaneously. Governance is achieved by fixing time and cost (and protecting quality through standards and the Definition of Done) while flexing scope using MoSCoW prioritization. This ensures predictability of delivery cadence and budget, while allowing the team to vary the amount of functionality delivered to meet the agreed constraints. Hence, some contingency must exist in at least one of the four variables—most commonly features—so that the project can respond to emerging information without compromising delivery dates or overspending. The AgilePM Handbook explicitly states: “It is unrealistic to expect all four… can be fixed and controlled… allow flexibility in at least one.” This approach enables incremental delivery, continuous negotiation of scope, and controlled change, ensuring that value is maximized within the agreed time and cost boundaries while maintaining quality. Therefore, the correct completion is “at least one of these variables.”

Line Leaders as Key Stakeholders: If line leaders are not fully engaged, they can create barriers to change implementation due to their influence on frontline staff. Providing them with privileged access ensures alignment and reduces resistance.

Other Options:

A: Seniority is irrelevant; engagement depends on roles and influence.

B: Authorization may not always be needed for every change.

C: Information access should be strategic, not indiscriminate.

Key AgilePM Concepts Referenced:

Engaging Stakeholders: AgilePM Handbook, Chapter 5, Section 5.4.

Comprehensive and Detailed Explanation (paraphrased from Agile Project Management guidance):

Agile thinking emphasizes customer value, empirical evidence, collaboration, and transparency. Option A reflects progressive elaboration and just-in-time refinement—good agile practice. Option B suggests a typical, lightweight cadence for readiness (often the Sprint prior), which is acceptable when driven by context and team capacity rather than rigid rule. Option C captures the essence of flow through small, frequent, validated increments. Option D, however, bypasses value-based prioritization, team forecasting, and collaborative decision-making by selecting the next Sprint’s work purely on sponsor preference. Agile approaches (e.g., MoSCoW prioritization, product goals, acceptance criteria) rely on shared, objective value measures, not unilateral authority, to maximize outcomes. Therefore, D does not demonstrate agile thinking.

Encourages Users: Change management focuses on equipping people to adopt and use new ways of working effectively, which maximizes the realization of benefits.

Other Options:

B: Avoiding dis-benefits is part of risk management.

C: Accountability lies with the sponsor, not change management alone.

D: Change management supports outcomes but doesn’t directly produce them.

Key AgilePM Concepts Referenced:

Role of Change Management in Benefits Realization: AgilePM Handbook, Chapter 7, Section 7.4.