AgilePM-Foundation Exam Dumps - APMG-International AgilePM Questions and Answers

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.

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.

The Product Owner is value steward and single ordering voice for the product backlog. Their accountability is to maximize value from the team’s work by clarifying outcomes, ordering backlog items, and ensuring transparency of goals, acceptance criteria, and readiness. They continuously engage customers and stakeholders, translate learning into backlog adjustments, and make scope trade-offs that protect time, cost, and quality. The Product Owner does not approve technical fitness (that sits with technical leadership and agreed quality criteria) nor manage a baselined delivery plan in a command-and-control sense; plans are living forecasts shaped by empirical evidence. Team effectiveness coaching belongs to the Scrum Master. By holding outcome accountability while collaborating closely with delivery and business roles, the Product Owner ensures increments align to strategy, benefits, and the evolving Business Case—precisely what option B states.

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.

Fairness: The SCARF model highlights the importance of perceived fairness in fostering trust and collaboration. Change managers must ensure that processes and decisions are perceived as just and equitable.

Other Options:

B: Faith is not a part of the SCARF model.

C and D: Fear and fight are reactions to stress, not SCARF elements.

Key AgilePM Concepts Referenced:

SCARF Model Application in Change: AgilePM Handbook, Chapter 5, Section 5.2.

In agile practice, a User Story is often framed by the “3 Cs”: Card, Conversation, and Confirmation. The Card captures just enough of the requirement to spark dialogue. The Conversation is the collaborative discussion among Product Owner (or Customer/Business), Developers, and other stakeholders that elaborates details and clarifies intent. The Confirmation element records the specific, testable acceptance criteria that will be used to verify the story delivers the intended outcome for its beneficiary (the user or customer). These acceptance criteria translate stakeholder expectations into objective checks—often articulated as scenarios or examples—that determine whether the story is fit for purpose and “Done.” Agile Project Management approaches (including AgilePM/DSDM and Scrum-aligned practices) emphasize that acceptance criteria belong with the story as its Confirmation, because that is what allows the team to assert value delivery, guide development and testing, and anchor Sprint Review demonstrations. Therefore, the appropriate place to record the concrete measures by which a user can successfully use the delivered capability is the Confirmation section of the User Story.

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

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.

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.