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

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

DSDM differs from most other Agile approaches because it focuses on the entire project lifecycle 4 5 6 . This includes pre-project, feasibility, foundations, development, and deployment phases, ensuring a comprehensive approach to project management.

AgilePM emphasizes lightweight but effective planning that maintains control without bureaucracy . Core planning concepts include timeboxing (fixed-duration delivery windows), MoSCoW prioritization (flexing scope to protect time/cost/quality), incremental and iterative delivery (frequent demonstrations and review), and rolling-wave planning (planning at multiple horizons). Together these techniques ensure transparency, predictable cadence, and early value while avoiding heavyweight documentation or rigid stage gates. Plans are living forecasts refined through continuous feedback and empirical evidence from delivered increments. Governance focuses on outcomes and fitness for purpose rather than exhaustive upfront detail. This is why the guidance often summarizes that AgilePM planning “keeps projects on track ,” enabling teams to respond to change, surface risks early, and align stakeholders around real progress. Options A, C, and D capture fragments of agile practice, but they understate the project-level intent. The correct completion is “projects on track.”

In a DSDM project, contingency is typically managed by varying the features to be delivered 6 . This approach aligns with the DSDM principle of delivering the most critical work first and using the MoSCoW prioritization to adjust the scope of delivery as needed.

Minimum Viable Product (MVP) : An MVP allows early customers to use a product and provide valuable feedback, which is then incorporated into subsequent iterations. This is central to Agile practices, emphasizing incremental delivery and responsiveness to user needs.

Other Options :

B : Full transparency relates to visibility into processes and progress, not product development.

C and D : These refer to team dynamics, not product delivery.

Key AgilePM Concepts Referenced :

Incremental Delivery : AgilePM Handbook, Chapter 3, Section 3.7.

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.

Business roles are critical in a DSDM project as they guide the evolution of the solution at a detailed level 6 . They provide day-to-day business direction and ensure that the solution being developed aligns with the business needs and objectives.

Comprehensive and Detailed Explanation (verified, paraphrased from AgilePM principles):

AgilePM promotes incremental and iterative delivery , aiming to deploy usable increments early and often . Regular deployment and demonstration validate fitness for purpose, expose risks sooner, and provide empirical feedback for planning. Early release of increments also tests assumptions about value with real users and stakeholders, informing prioritization (e.g., MoSCoW) and shaping subsequent increments. This approach supports continuous learning, sharper benefits focus, and stronger financial governance, because funding and scope decisions can be based on evidence from working solution slices rather than predictions. Hence, both statements accurately reflect agile project delivery.

Small Incremental/Iterative Releases : Delivering change in smaller increments allows for immediate feedback and adaptation, embodying the concept of ' Minimum Viable Change Practice. '

Other Options :

A : Big Bang involves a single, large-scale rollout, unsuitable for iterative practices.

B : Phased rollouts involve sequential implementation but may not emphasize iteration.

C : Voluntary Adoption doesn’t inherently align with iterative releases.

Key AgilePM Concepts Referenced :

Iterative Delivery Strategies : AgilePM Handbook, Chapter 3, Section 3.7.

Autonomy, Mastery, and Purpose : As outlined by Daniel Pink, these three factors drive motivation in knowledge work, which relies on creativity and engagement. Agile practices support autonomy through self-organizing teams, mastery through continuous learning, and purpose through shared goals.

Other Options : These reflect traditional or outdated models of motivation and do not align with Pink’s framework.

Key AgilePM Concepts Referenced :

Motivating Teams : AgilePM Handbook, Chapter 5, Section 5.7.

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.

Solution increments are created during the Evolutionary Development phase.  This phase is where the solution is developed iteratively, building on the firm foundations laid out in the previous phases 1 . It involves creating increments of the product through time-boxed iterations, ensuring that the solution evolves in line with the project’s objectives and business needs.

Principle 8 - Demonstrate Control requires the transparency of all work being performed by the team 5 .  This principle ensures that plans and progress are visible to all and that progress is measured through the delivery of products rather than completed activities 5 .

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

Scrum defines four events within the Sprint: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective . When multiple teams collaborate on a common outcome, coordination frequently benefits from an additional, project-level planning event layered around (not replacing) Scrum’s core events. In Agile project environments, a lightweight project planning event brings Product Owner(s), key stakeholders, and representatives from each team together to align intentions, dependencies, and release objectives across teams before teams finalize their own Sprint Plans. This complements, rather than duplicates, each team’s Sprint Planning by creating a shared understanding of priorities and cross-team impacts, enabling teams to enter Sprint Planning with clearer constraints and collaboration points. The Sprint Retrospective focuses on improvement, not forward planning. Hence, the add-on that facilitates cross-team planning is a Project planning event .

The MoSCoW technique is used for understanding and managing priorities 3 .  It helps teams prioritize features, user stories, and requirements by categorizing them into Must have, Should have, Could have, and Won’t have, ensuring that the most critical items are addressed first 4 .

Within the Solution Development team, it is not required for all members to be multi-skilled experts 1 .  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 areas 1 .

Engagement : Defined as the process of increasing employee and stakeholder involvement in organizational change, engagement ensures commitment and minimizes resistance. It is a key responsibility of change managers to foster this involvement, as outlined in AgilePM principles.

Other Options :

Change Agent : Refers to individuals or teams driving the change process, not the process itself.

Sponsor : Represents leadership roles advocating for change but is not a mechanism for involvement.

Line Leader : Plays a supportive role in change but does not define engagement itself.

Key AgilePM Concepts Referenced :

Employee Engagement : AgilePM Handbook, Chapter 3, Section 3.2.

Qualitative Measures : These provide insight into the underlying reasons, motivations, and emotions behind behaviors. Examples include interviews, open-ended surveys, and focus groups.

Other Options :

B : Quantitative measures focus on numerical data but lack context.

C : Leading indicators predict future performance but don’t explain behavior.

D : Lagging indicators reflect past performance, not the reasons behind it.

Key AgilePM Concepts Referenced :

Measurement and Analysis : AgilePM Handbook, Chapter 7, Section 7.5.

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.”

Comprehensive and Detailed 150 to 300 words Explanation From Exact Extract of Agile Project Management (paraphrased to avoid lengthy quotation):

In AgilePM (DSDM), the Team Leader role closely aligns with the facilitative, servant-leadership responsibilities commonly associated with a Scrum Master in Scrum. The Team Leader is accountable for enabling collaborative working, removing impediments, fostering continuous improvement, and protecting the team’s focus within timeboxes —all hallmarks of Scrum Mastery. While titles differ across frameworks, AgilePM explicitly positions Team Leader as the day-to-day lead for the Solution Development Team , emphasizing facilitation, coaching, and ensuring adherence to agreed practices (e.g., MoSCoW prioritization, Definition of Done/quality criteria). By contrast, a Project Manager in AgilePM is a project-level role focused on governance and business case stewardship; a Product Owner (AgilePM’s Business Visionary/Business Ambassador combination) prioritizes value and backlog—this is not a facilitation role; and a Developer focuses on building the solution. Therefore, when mapping roles between Scrum and AgilePM, the Team Leader most naturally substitutes for, or corresponds to, the Scrum Master responsibilities, ensuring servant leadership without shifting into command-and-control behavior.

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

AgilePM treats risk management as an intrinsic, continuous activity rather than a siloed function. It reduces uncertainty through short timeboxes, early and frequent validation, empowered cross-functional teams, and active business involvement. Collaborative practices—facilitated workshops, visible backlogs, daily coordination, and regular reviews—surface risks early and promote rapid mitigation through transparency. MoSCoW prioritization and incremental delivery protect time and quality, containing exposure while enabling trade-offs when new information emerges. Formal artifacts and governance still exist, but they are lightweight and outcome-oriented, supporting timely decisions instead of creating bureaucracy. Options B and C conflict with AgilePM’s integrated, collaborative stance by proposing rigid or separated processes. Option D contradicts agile values by elevating contracts over customer collaboration. Consequently, the accurate description is A : integrate risk thinking into everyday work, leveraging collaboration and transparency to manage uncertainty.

Statement 1 : Correct . Leading by example is crucial for inspiring trust and alignment with the change vision. Symbolic actions by leaders play a significant role in fostering engagement.

Statement 2 : Incorrect . Change influence is not limited to leaders; team members and change agents can also drive and inspire change.

Key AgilePM Concepts Referenced :

Role of Leadership in Change : AgilePM Handbook, Chapter 6, Section 6.2.

In Scrum, a Product Backlog Item (PBI) is considered “ready” when it is sufficiently understood, appropriately sized, and clear enough that the Developers believe they can complete it within a single Sprint. PBIs that meet this threshold are suitable for selection during Sprint Planning because they have enough clarity of value, acceptance criteria, and implementation approach to be forecast as “Done” by the end of the Sprint. Readiness is typically achieved through ongoing Product Backlog refinement, where the Product Owner and Developers collaborate to add detail, order, and size. The key test is not whether an item appears on the backlog, is captured as a user story, or is merely chosen in the meeting; rather, it is whether the item is small and transparent enough to be completed within the Sprint’s timebox and to meet the Definition of Done. Therefore, option B best reflects the standard: a PBI is ready when it is small enough—and clear enough—to be completed (“Done”) within one Sprint.

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.

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

The DSDM philosophy emphasizes that the best business value emerges when projects are aligned to clear business goals, deliver frequently, and involve the collaboration of motivated and empowered people 1 .  The eight principles of DSDM support this philosophy and are brought to life by guiding the team in the attitude it must take and the mindset it must adopt to deliver consistently while remaining flexible 1 .  These principles are supported by process, people, products, and practices, which enable organizations to deliver best value business solutions collaboratively 1 .

The Pre-Project phase is the stage where it is decided which projects are started, based on a clearly defined objective 1 .  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 goals 1 .

Celebrating Short-Term Wins : Demonstrating early achievements builds confidence and reduces resistance by showing tangible progress. This is a key step in Kotter ' s model for leading change.

Other Options :

A : Building a coalition involves leadership but not reducing doubt.

B : Creating urgency addresses the need for change, not achievements.

C : Accelerating movement focuses on overall momentum.

Key AgilePM Concepts Referenced :

Kotter’s Change Model : AgilePM Handbook, Chapter 6, Section 6.2.

Action Phase : Breaking change actions into smaller, manageable tasks happens during the Action step, where detailed plans are implemented. This ensures smoother execution and tracking of progress.

Other Options :

Discovery : Focuses on understanding the current situation.

Ideas : Involves generating potential solutions.

Prioritization : Helps decide which tasks or changes to focus on.

Key AgilePM Concepts Referenced :

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

The Project Manager is responsible for the delivery of the project from Foundations through to Deployment 1 .  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 deployment 1 .

Maintenance is not one of the interest groups into which each DSDM role is grouped 1 .  The recognized interest groups are Business, Solution/Technical, and Management 1 . 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.

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.

It is during the Feasibility phase that it is first established whether further investigation of the project is justified 3 . This phase aims to determine if the proposed project is likely to be feasible from both a technical and business perspective.

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.

Comprehensive and Detailed Explanation (paraphrased from DSDM/AgilePM principles):

One of AgilePM’s eight guiding principles is “Never compromise quality.” Quality is fixed and protected: teams define the required level up-front via acceptance criteria, Definition of Done, and non-functional requirements, then manage scope with MoSCoW prioritization to ensure the agreed quality bar is always met. Time and cost are typically fixed through timeboxing and team sizing, while scope flexes to safeguard quality and predictability. This principle prevents trading away essential quality under delivery pressure and ensures increments are genuinely “fit for purpose.” Options A and C are good values but are not stated AgilePM principles, and D contradicts the ethos—agile does commit to quality by making it explicit, measurable, and non-negotiable. Therefore, B is correct.

Comprehensive and Detailed Explanation (paraphrased from AgilePM governance guidance):

AgilePM’s financial governance relies on artifacts that demonstrate continuing business justification, predictable control, and informed decision-making. Core project artifacts include the Feasibility Assessment (early viability and value assessment), the Foundations Summary (establishes the Business Case, scope, approach, plans, and controls), and the Project Review Report (evidence-based assessments of progress, benefits, and risks). These directly support budget stewardship, investment decisions, and release planning. A Sprint Review Record is a Scrum team-level event output focused on inspecting increments and adapting the Product Backlog; it is not a defined AgilePM project artifact nor specifically a financial governance instrument. While insights from reviews inform governance, the formal artifacts tied to AgilePM’s project-level financial control are exemplified by options A, C, and D—hence B is the correct “NOT” choice.

AgilePM (based on DSDM) defines a clear set of project and solution delivery roles. At the project level: Business Sponsor (investment owner), Business Visionary (custodian of the business vision), and Project Manager (overall project management and governance). Within the Solution Development Team: Team Leader, Business Ambassador, Business Analyst, Solution Developer, Solution Tester, and technical governance via the Technical Coordinator role. Notably, AgilePM uses the title Technical Coordinator rather than “Solution Architect.” Although many organizations informally use “solution architect,” it is not an AgilePM role name; its responsibilities most closely map to the Technical Coordinator, who ensures technical coherence, manages technical risks, and upholds non-functional requirements and architectural guidelines. Therefore, among the options given, Solution Architect is the one that is not an AgilePM-defined project role, whereas Business Visionary, Project Manager, and Solution Developer are explicitly recognized roles in the AgilePM framework.

The DSDM product that describes how the benefits have actually accrued following a period in live operation is the Benefits Assessment 3 .  This product is used to assess the actual benefits realized after the solution has been in use 3 .

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

Agile leadership distributes authority and nurtures autonomy so that decisions can be made closest to the work. The principle that most clearly embodies empowerment, shared ownership, and accountability at every level is “Leadership lives everywhere in the organization.” This principle encourages leaders to create the conditions for others to lead—clarifying intent, aligning on outcomes, and then trusting teams to own decisions within clear boundaries. It contrasts with command-and-control models by fostering psychological safety, inviting initiative, and rewarding collaborative problem-solving. While feedback (B), meaning and purpose (C), and healthy engagement with emotion (D) are all important, they are supporting principles. The scenario described—empowering others and spreading accountability—maps directly to leadership as a shared organizational capability, not a title. This accelerates learning, reduces decision latency, and enables adaptive responses to change—hallmarks of agile organizations.

According to the DSDM principle ‘Never Compromise Quality,’ the overall level of quality to be delivered within the solution should be agreed at the start of the project 5 .  This principle ensures that quality is not compromised to recover from deviations; instead, the scope of the project will be dynamic 6 .

Adjourning : This stage occurs when a team disbands after achieving its objectives. Members reflect on their accomplishments and prepare to move on, often with a sense of closure and satisfaction.

Other Stages :

Forming : Initial stage where the team is being established.

Storming : Involves conflict as roles and expectations are clarified.

Performing : High-functioning stage focused on productivity.

Key AgilePM Concepts Referenced :

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

The Agile Manifesto explicitly values “individuals and interactions over processes and tools.” AgilePM fully aligns with this principle. While processes, tools, documentation, and contracts are important and often necessary (especially for governance, compliance, and clarity), they should not take precedence over effective collaboration, empowered teams, and rapid feedback. AgilePM’s practices—facilitated workshops, daily coordination, frequent reviews, and active business involvement—are designed to maximize human interaction to reduce waste, accelerate understanding, and improve quality. Even in regulated or contractual contexts, AgilePM recommends shaping processes and agreements to enable collaboration (e.g., clear roles, decision latency reduction, acceptance criteria, and incremental validation) rather than letting procedures dominate. Therefore, no listed circumstance justifies prioritizing processes and tools over individuals and interactions. The right choice is D. None of the above.