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

Supporting and Influencing Local Staff: Line leaders play a vital role in translating the change vision into action at the team level. They understand the specific needs and concerns of their teams and can act as a bridge between staff and senior management.

Other Options:

A: Local decision-making authority is beneficial but not their primary role.

B: Leaders are often deeply impacted by change.

D: Line leaders often juggle multiple responsibilities.

Key AgilePM Concepts Referenced:

Role of Line Leaders: AgilePM Handbook, Chapter 5, Section 5.6.

Simple: The Cynefin framework classifies situations where cause and effect are obvious as "simple," requiring straightforward solutions based on best practices.

Other Options:

Multifaceted: Not a recognized category in Cynefin.

Complex: Refers to situations where cause and effect are not immediately apparent.

Chaotic: Refers to situations with no apparent relationship between cause and effect.

Key AgilePM Concepts Referenced:

Cynefin Framework for Complexity: AgilePM Handbook, Chapter 3, Section 3.3.

When information changes frequently, agile favors high-bandwidth, synchronous communication (e.g., video/teleconferences, facilitated sessions) that enables rapid clarification, shared understanding, and immediate adjustment. Static written documents become quickly outdated, encourage lag between change and consumption, and invite misinterpretation without fast feedback loops. Even email, while asynchronous, can be used for rapid, lightweight updates—but it still lacks the immediacy and richness of dialogue. AgilePM stresses visible progress, collaborative workshops, and frequent reviews to keep everyone aligned as facts evolve. Therefore, in a high-change context, a written document is typically the least effective mechanism to keep stakeholders synchronized, whereas live conversations and demonstrations better support timely inspection and adaptation.

Agile principles assert that the most efficient and effective method of conveying information within a development team is face-to-face conversation. This emphasizes rich, synchronous communication—co-location where possible, or high-fidelity remote collaboration (video, whiteboarding, pair/mob work) when not. Face-to-face dialog accelerates shared understanding, reduces rework caused by misinterpretation, and shortens feedback loops so issues are surfaced and resolved quickly. While transparency, collaboration, and continuity are vital cultural qualities, the principle specifically calls out face-to-face as the preferred communication mode. AgilePM operationalizes this through facilitated workshops, daily coordination, frequent reviews/demos, and visible artifacts that support immediate discussion. Even in distributed teams, the intent is preserved by using communication tools and practices that approximate face-to-face bandwidth, ensuring decisions are grounded in common understanding and enabling rapid inspection and adaptation.

Discovery: The Continuous Change Management Cycle starts with understanding the current situation, challenges, and opportunities. Discovery ensures that subsequent steps are informed and targeted.

Other Options:

A: Ideas come after discovery.

B: Prioritization occurs after potential solutions are identified.

D: Action follows the planning and prioritization phases.

Key AgilePM Concepts Referenced:

Continuous Change Management Cycle: AgilePM Handbook, Chapter 6, Section 6.6.

The Terms of Reference is identified as a governance product in DSDM because it may be used for purposes such as the prioritization of a project within a portfolio2. It provides a high-level definition of the overarching business driver and top-level objectives of the project.

AgilePM’s control philosophy fixes Time (via timeboxing) and Cost (via stable team size and duration), and protects Quality (it must never be compromised). To keep delivery predictable while remaining responsive to change, contingency is placed in Scope, i.e., Features. Using MoSCoW prioritization, Must Haves are capped, while Shoulds and Coulds provide the controlled flexibility needed to absorb change, manage uncertainty, and still meet deadlines and budgets at the agreed quality level. This approach turns scope into the adjustable “knob,” enabling teams to make informed trade-offs as learning emerges, without eroding the Definition of Done or slipping time/cost constraints. Hence, contingency belongs in Features.

Timeboxing is the technique that allows for testing the achievability of objectives. This approach involves setting a fixed period (the Timebox) during which specific tasks or objectives must be completed. By focusing on what can be achieved within the set time frame, Timeboxing helps teams test and validate whether their objectives are realistic and attainable. This iterative approach ensures continuous assessment and adaptation, promoting efficient project management.

Instrumental Success Factors (ISFs) in DSDM are crucial as they position projects for a successful outcome. ISFs are the critical elements that must be in place for a DSDM project to succeed. They provide a foundation for effective project management and delivery, ensuring that all necessary conditions are met to support the project's objectives and deliverables.

Statement 1: Incorrect. Engaging people in change is complex and requires tailored strategies. It’s not a simple or routine task.

Statement 2: Incorrect. Change situations vary greatly, and no single formula works universally. Agile emphasizes context-specific approaches.

Key AgilePM Concepts Referenced:

Engagement Strategies: AgilePM Handbook, Chapter 4, Section 4.2.