AgilePM-Foundation Agile Project Management (AgilePM v3) Foundation Exam v3 update Questions and Answers

Dissatisfaction with the Status Quo: The change formula includes dissatisfaction as a key driver for change. Without sufficient dissatisfaction, the motivation to change is diminished.

Other Options:

B, C, and D: These factors, while important, are not explicitly part of the Beckhard and Harris change formula.

Key AgilePM Concepts Referenced:

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

Comprehensive and Detailed 150–300 words Explanation (paraphrased from AgilePM/DSDM guidance):

In AgilePM, the Business Sponsor is the project’s ultimate decision-maker and the role accountable for ensuring continued business justification. This includes owning the investment decision, securing and sustaining funding, and maintaining senior-level commitment to the business opportunity. A lack of commitment represents a threat to the viability of the Business Case; managing and mitigating that risk sits squarely with the Sponsor. The Sponsor establishes clear objectives, champions the initiative across the organization, removes high-level impediments, and ensures that governance supports timely decisions. While the Business Visionary articulates and safeguards the solution vision and value outcomes, that role does not control organizational commitment or funding at the enterprise level. Similarly, Business Advisors provide specialist input but do not own commitment or investment risk. Therefore, where commitment to the business opportunity is wavering or unclear, the Business Sponsor is responsible for intervening—reconfirming the Business Case, rallying stakeholder support, and aligning investment, scope and timescales—so the project remains justified and deliverable.

Transparency: Sharing the rationale and timeline for change ensures openness and builds trust among stakeholders. Transparency is fundamental to managing expectations and mitigating resistance.

Other Options:

Inclusivity: Focuses on ensuring all voices are heard.

Connectivity: Refers to fostering relationships.

Empathy: Relates to understanding others’ feelings, not information sharing.

Key AgilePM Concepts Referenced:

Transparent Communication: AgilePM Handbook, Chapter 4, Section 4.2.

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.

Actively Involve Line Managers: Change management frameworks highlight the importance of involving line managers to support individuals through the emotional phases of the change curve. Line managers can offer guidance, listen to concerns, and provide the reassurance needed to navigate uncertainty.

Why the Other Options Are Incorrect:

B: Negative emotions are a normal part of the change curve and should not automatically be seen as mismanagement.

C: Discouraging discussion can create further resistance and disengagement.

D: Assuming individuals will adapt over time neglects the need for proactive engagement and support.

Key AgilePM Concepts Referenced:

Navigating the Change Curve: AgilePM Handbook, Chapter 6, Section 6.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

Comprehensive and Detailed Explanation (concise, policy-compliant):

Scrum rests on empiricism and lean thinking. Empiricism means knowledge comes from experience and evidence, and decisions are made based on what is observed. Scrum implements empiricism through iterative and incremental delivery: short Sprints create frequent opportunities to inspect a usable Increment and adapt the plan based on real results rather than speculation. Iteration reduces risk by enabling rapid learning, early validation of assumptions, and continuous refinement of the Product Backlog. Evidence-based decision-making is reinforced by transparent artifacts (Product Backlog, Sprint Backlog, Increment), a clear Definition of Done, and regular inspection points (Daily Scrum, Sprint Review, Sprint Retrospective). Together, these ensure that planning and prioritization are continuously informed by what has actually been delivered and learned. Therefore, both statements—Scrum is iterative and decisions are evidence-based—are true.

The Business Visionary is responsible for interpreting the needs of the Business Sponsor and communicating these to the team1. This role represents the Business Sponsor by communicating the vision of the project and ensuring that the team understands the sponsor’s requirements1.

Financial: A measurable increase in sales reflects improved financial performance, making it a financial metric. Financial views in a change delivery scorecard often include profitability, revenue growth, and ROI—all of which are influenced by sales increases.

Customer, Internal, Learning & Growth: These are equally important views but do not directly relate to sales performance. For instance:

Customer View: Focuses on customer satisfaction and loyalty.

Internal View: Addresses process efficiency.

Learning & Growth View: Pertains to employee development and organizational innovation.

Key AgilePM Concepts Referenced:

Scorecard and Value Metrics: AgilePM Handbook, Section 2.5.3.

Comprehensive and Detailed Explanation (paraphrased from AgilePM/Agile standards; exact long extracts cannot be provided):

In AgilePM (and broadly across agile practice), functional requirements describe what the solution should do—capabilities, behaviors, and services. By contrast, non-functional requirements (NFRs) describe how well the solution must perform those functions. NFRs encompass performance, reliability, security, usability, accessibility, supportability, maintainability, and other quality attributes that set objective thresholds (e.g., response times, availability targets, encryption standards). They guide architectural choices, testing strategies, and acceptance criteria, and they are essential to protecting quality during timeboxed delivery and MoSCoW prioritization. Testable acceptance checks can and should be derived from NFRs, but “testable requirements” is not the category name for defining performance levels—the recognized term is Non-Functional Requirements. Therefore, the correct option is B.

 The Delivery Plan defined by DSDM has a planning horizon that includes the end of the project7. This plan looks towards the future, often months or years ahead, to guide the incremental delivery of the project’s outcomes.

Statement 1: Correct. Identifying stakeholders involves analyzing who will be impacted by the change and their level of influence.

Statement 2: Correct. Stakeholder mapping is a tool used to visualize and prioritize stakeholders based on their influence and interest.

Key AgilePM Concepts Referenced:

Stakeholder Mapping and Identification: AgilePM Handbook, Chapter 5, Section 5.5.

In DSDM, it is true that one DSDM role does not necessarily mean one person. This allows for flexibility in assigning roles based on the project’s needs and the individuals’ skills and capacities. It is possible for one person to hold multiple roles or for a role to be shared among several people, depending on what is most effective for the project.

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.

The role that should ideally be independent of the outcome to be achieved in a Facilitated Workshop is the Workshop Facilitator4. This role manages the processes and dynamics of the workshop and should remain neutral and impartial4.

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.

The strategy for Iterative Development should be considered during the Foundations phase. This phase establishes a firm foundation for the project, ensuring that only the right projects are started and that they are set up correctly, considering aspects such as feasibility and business case1. It’s crucial to have a clear strategy for Iterative Development at this stage to guide the subsequent phases of the project effectively.

The Project Approach Questionnaire (PAQ) is a diagnostic tool in AgilePM used to surface approach-based risks early and throughout the project. It examines dimensions such as organizational culture, leadership behaviors, stakeholder engagement, governance expectations, team empowerment, and technical/environmental readiness against AgilePM principles and practices. By assessing these areas, the PAQ highlights misalignments (e.g., low business involvement, decision latency, rigid change control, insufficient empowerment) that could undermine agile delivery. The output informs targeted mitigations—coaching needs, governance adjustments, facilitation plans, risk responses, and communications—embedded into the project approach. It is not a one-off retrospective instrument (contra option C); it is used iteratively to steer the approach. Nor does it “ensure agreement” and “eliminate the need” for other controls (contra option B); instead, it supports informed governance and continuous improvement. Finally, it does not focus solely on technical risks (contra option D); it explicitly covers culture and leadership alongside process and technical considerations.

The Pre-Project phase is the stage where it is decided which projects are started, based on a clearly defined objective1. This phase ensures that only the right projects are initiated and that they are set up correctly, aligning with the DSDM philosophy that the best business value emerges when projects are aligned to clear business goals1.

Statement 1: Incorrect. Having more data doesn’t guarantee better results; quality and relevance of data matter more.

Statement 2: Correct. External data can provide fresh perspectives and reduce internal biases.

Key AgilePM Concepts Referenced:

Using Data for Insights: AgilePM Handbook, Chapter 7, Section 7.6.

The Agile Manifesto values “working software over comprehensive documentation,” but does not reject documents; it promotes fit-for-purpose documentation that adds value. AgilePM echoes this with lightweight, high-value artifacts (e.g., Business Case, Foundations summary, acceptance criteria) to support clarity and governance “without excessive bureaucracy.” Therefore (1) is true: create documents when they add value. (3) is true: documents must be visible and understood by those who use them to collaborate and decide; transparency is essential. (4) is also true: high-level documents early (vision, scope boundaries, approach) support planning, alignment, and later refinement. (2) is false: agile does not prohibit contracts; it values customer collaboration over contract negotiation, yet recognizes contracts may be necessary and useful when framed to enable change. Consequently, the correct set is 1, 3, and 4, i.e., C.

The Foundations phase is when it is established how quality will be assured4. This phase builds upon the preliminary investigation from the Feasibility phase to establish a fundamental understanding of the business rationale for the project and how the development and delivery of the solution will be managed, including quality assurance measures4.

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.

A Facilitated Workshop provides an interactive environment where all key players can contribute to the outcome3. It is a practice within Agile and DSDM that encourages collaboration and active participation from all stakeholders to shape the project’s direction and solutions.

The Project Manager is responsible for the delivery of the project from Foundations through to Deployment1. This role involves high-level coordination of the project, ensuring that both business and technical delivery aspects are managed effectively from the initial phases through to the final deployment1.

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.

DSDM acknowledges that change is inevitable and that projects operate within a changing world5. The methodology is designed to embrace change and harness its benefits, rather than resist it.

Timeboxing: Fixed time periods, such as sprints, are used to focus efforts and deliver outcomes within a predefined timeframe. This helps teams remain disciplined and maintain momentum while working iteratively.

Other Options:

A: Minimum viable product relates to the initial version of a product with essential features.

C: Full transparency refers to visibility into the process.

D: Frequent delivery is broader and does not imply fixed time periods.

Key AgilePM Concepts Referenced:

Timeboxing: AgilePM Handbook, Chapter 3, Section 3.4.

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.

Statement 1: Incorrect. Communication plans should be tailored to the specific context of each change initiative, as a one-size-fits-all approach does not work.

Statement 2: Correct. The scale and complexity of change will dictate the content and level of detail in the communication plan.

Key AgilePM Concepts Referenced:

Tailored Communication Plans: AgilePM Handbook, Chapter 4, Section 4.3.

Productivity Dip: A temporary drop in productivity is common when employees are being trained on new processes or systems. This cost is critical to account for in planning and managing change effectively.

Other Options:

Safety & Wellbeing: Relates to physical and emotional health, not productivity.

Reputational: Refers to external perception of the organization.

Opportunity: Refers to lost potential from alternative courses of action.

Key AgilePM Concepts Referenced:

Assessing Change Impact: AgilePM Handbook, Chapter 7, Section 7.3.

Agile delivery expects each increment to be usable, meet the agreed quality bar (Definition of Done), and move the product toward its goal. AgilePM’s incremental, timeboxed approach stresses that every slice should be demonstrably valuable or verifiable, with acceptance criteria satisfied and quality never compromised. However, increments in an evolving solution are typically additive and cumulative; they build upon prior work to extend capability. Requiring that an increment be independent of all others is unnecessary and often impractical for integrated solutions. What matters is that it is coherent, tested, and acceptable to stakeholders within the agreed standards. Thus, options A, C, and D describe standard expectations for an increment in AgilePM/Scrum-aligned practice, whereas B does not. Therefore, B is the correct “NOT” choice.

Assessing Effectiveness: The measurement methodology helps determine whether communication efforts are achieving their intended goals. Metrics such as engagement levels and feedback are used to refine strategies.

Other Options:

B: Focuses on testing rather than communication.

C: Relates to impact assessment, not methodology.

D: Ensuring understanding is an objective, not a methodology.

Key AgilePM Concepts Referenced:

Communication Effectiveness: AgilePM Handbook, Chapter 4, Section 4.5.

Scrum supplies the core framework (roles, events, artifacts) for empirically building products, but it is intentionally lightweight. AgilePM (based on DSDM) complements Scrum by offering a well-tested pool of practices, tools, and techniques that strengthen day-to-day delivery and governance without altering Scrum’s essence. Typical enhancements include MoSCoW prioritization to manage variable scope, timeboxing to protect cadence, facilitated workshops and modeling to accelerate shared understanding, and explicit roles for business involvement to improve decision flow. AgilePM also provides guidance on project-level controls—such as business cases, incremental release planning, and benefits focus—that sit outside Scrum’s product-delivery scope. For a Scrum Master, this combination is valuable: Scrum remains the engine of iterative delivery, while AgilePM offers practical methods to refine backlog refinement, clarify acceptance criteria, manage dependencies, and support predictable delivery against time and cost constraints. Thus, the pairing gives Scrum Masters a richer toolkit to coach teams, align stakeholders, and handle real-world project contexts where governance, prioritization, and incremental release structures are needed—precisely what option B describes.

Statement 1: Correct. The change curve describes typical emotional responses to change, including denial, resistance, exploration, and commitment.

Statement 2: Incorrect. The change curve applies to both positive and negative changes, as it reflects the adjustment process regardless of the perceived nature of the change.

Key AgilePM Concepts Referenced:

Emotional Responses to Change: AgilePM Handbook, Chapter 6, Section 6.3.

When using the Iterative Development technique, each cycle should include Thought, Action, and Control. These components ensure that the development process is systematic and reflective. Thought involves planning and considering the next steps, Action is the implementation of those plans, and Control is the evaluation and adjustment based on feedback and results. This iterative cycle helps in refining the product incrementally and ensures continuous improvement.

Maintenance is not one of the interest groups into which each DSDM role is grouped1. The recognized interest groups are Business, Solution/Technical, and Management1. These groups represent the different areas of focus within a DSDM project.

In DSDM, each role is grouped into interests such as Business, Solution/Technical, and Management. Maintenance is not one of the interests into which DSDM roles are grouped. The primary focus of DSDM roles is to ensure that the project is delivered successfully by balancing business needs, technical feasibility, and effective management practices.

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.

The DSDM process can indeed be configured and calibrated to cater for a range of projects, from those requiring light governance to those needing stronger governance1. This flexibility allows the DSDM process to be tailored to the specific needs of the project, ensuring that the right balance between control and agility is achieved1.

AgilePM distinguishes between increments in terms of what is actually delivered to stakeholders. The emphasis is on a Solution—the integrated outcome that delivers business value—not merely isolated technical outputs. As delivery progresses, teams create Solution Increments that accumulate into a releasable Product (the broader, user-facing capability). This distinction helps align day-to-day development with business outcomes: every increment should be a cohesive slice of the evolving solution that is demonstrably usable or verifiable, while the Product view ensures that increments collectively support release goals and benefits realization. AgilePM’s focus on MoSCoW prioritization and timeboxing supports this by ensuring each Solution Increment contains the right mix of Must/Should/Could features to satisfy acceptance and maintain momentum. In practice, reviews showcase the Solution Increment’s usability to business representatives, while release planning considers how these increments roll up into Product evolution. Therefore, the two types associated with what is delivered are best captured by Solution and Product, making option A the fit with AgilePM terminology and intent.

A Timebox Plan is updated at the Daily Start-ups. These daily meetings allow the team to review progress, discuss any issues, and make necessary adjustments to the plan. Regular updates ensure that the project stays on track and that any deviations are addressed promptly, facilitating smooth and efficient progress towards the Timebox objectives.

Realizing business value often depends on business change enablement—including user training, readiness, and adoption. In AgilePM, the Business Visionary owns the business vision and ensures the evolving solution will deliver the expected benefits in operational use. They coordinate with Business Ambassadors and other stakeholders to prepare the organization (e.g., training, process updates) so that increments translate into realized value. While a Project Manager may help plan logistics and the Scrum Master facilitates the team, accountability for ensuring the business side is prepared to exploit the product sits with the Business Visionary. The Business Sponsor owns investment and justification; they may support funding for training, but the Visionary leads aligning solution capabilities with people and practice changes needed for benefit realization.