Free Practice Questions for APMG-International AgilePM-Foundation Exam

Statement 1: Correct. Actively responding to contributions fosters a sense of inclusion and appreciation, which is crucial for engagement and trust during change.

Statement 2: Incorrect. Decisions during change often involve emotional as well as rational considerations, as people’s behaviors and attitudes are not purely logical.

Key AgilePM Concepts Referenced:

Engaging Stakeholders Emotionally: AgilePM Handbook, Chapter 4, Section 4.3.

Comprehensive and Detailed 150–300 words Explanation (paraphrased from Scrum & AgilePM practice):

When multiple teams build a single product within one project, effective backlog ownership and value alignment are critical. Scrum practice—and AgilePM when combined with Scrum—supports one Product Owner for the product, even when several teams deliver increments in parallel. A single Product Owner preserves a single ordered Product Backlog, unified priorities, and consistent acceptance criteria, minimizing conflicts and dependency churn. Each team may have its own Scrum Master to optimize facilitation and impediment removal locally, but the essential management mechanism for cross-team coherence is shared product ownership (one Product Owner) paired with lightweight cross-team planning and frequent integration. Splitting into two separate projects (with separate roles) for one product typically fragments value flow and complicates governance. Likewise, mandating different Business Visionaries per team dilutes accountability for the product outcome. Hence, the preferred and most effective approach is that both teams share the same Product Owner to maintain a single value and prioritization voice.

Statement 1: Correct. Rich communication channels, such as face-to-face conversations or video calls, are necessary for active engagement as they allow for two-way interaction and emotional connection.

Statement 2: Correct. Leaner channels, like emails or memos, are appropriate when the message is straightforward and unlikely to be misinterpreted.

Key AgilePM Concepts Referenced:

Effective Communication Channels: AgilePM Handbook, Chapter 4, Section 4.3.

The Post-Project phase in AgilePM is crucial for evaluating the project’s success in terms of the business benefits realized3. It is conducted after the project is completed and focuses on assessing whether the expected benefits outlined at the start of the project have been achieved

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.

The role that normally facilitates the Daily Stand-up in AgilePM is the Team Leader5. The Team Leader ensures that the meeting is focused on progress toward the iteration goal and facilitates effective decision-making during the stand-up.

Statement 1: Correct. Diverse teams bring varied perspectives, which enhances creativity and innovation. AgilePM highlights the importance of leveraging diversity for better outcomes.

Statement 2: Correct. Diverse teams approach problems from multiple angles, resulting in more thorough decision-making. However, this often requires additional time to align perspectives.

Key AgilePM Concepts Referenced:

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

Within the Solution Development team, it is not required for all members to be multi-skilled experts1. While a diverse set of skills is beneficial, DSDM emphasizes collaboration and the effective use of individual strengths rather than expecting every team member to be an expert in all areas1.

The stated benefits of using DSDM include the business being better able to direct development, the reduced risk of building the wrong solution, and a smoother deployment process2. These benefits stem from DSDM’s iterative approach and close collaboration with stakeholders2.

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.