APMG-International AgilePM-Foundation Practice Exam Questions & Answers

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.

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.

In a free format Timebox, reviews should take place: B. Throughout the body of the Timebox3.

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.

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.

AgilePM Foundation Handbook

'Scrum: The Art of Doing Twice the Work in Half the Time' by Jeff Sutherland

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.

Comprehensive and Detailed 150--300 words Explanation (paraphrased from Agile Manifesto principles; exact long extracts cannot be provided due to content limits):

The Agile Manifesto values ''customer collaboration over contract negotiation.'' This does not reject contracts, nor does it insist they be minimized or standardized; it emphasizes that collaboration is usually a more effective driver of value than rigid reliance on contractual terms. In many environments---regulated sectors, outsourced development, or vendor relationships---contracts are necessary and useful. Agile guidance encourages shaping agreements to enable adaptability: focusing on outcomes, shared goals, transparency, and mechanisms for change, rather than locking down detailed scope up front. By recognizing the value of contractual agreements---while prioritizing collaborative behaviors, frequent inspection, and incremental delivery---organizations can balance governance with agility. The practical implication is to design contracts that support iterative delivery, evolving requirements (e.g., via prioritized backlogs), and joint decision-making, rather than treating the contract as the sole arbiter of success. Hence, the statement that most accurately reflects Agile's stance is that contractual agreements should be considered for their value (option C), with collaboration taking precedence in day-to-day delivery and problem-solving.