APMG-International Agile Project Management Foundation AgilePM-Foundation Exam Practice Test

Answer : D

Performing Stage: In this stage, team members work cohesively towards achieving results. Roles and processes are clear, and collaboration is at its peak.

Other Stages:

Forming: Initial setup with limited collaboration.

Storming: Characterized by conflict and role clarification.

Adjourning: Focused on disbanding after tasks are completed.

Key AgilePM Concepts Referenced:

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

Answer : A

The Solution Architecture Definition is an evolutionary product that provides a high-level design framework for the solution2. It is intended to cover both business and technical aspects of the solution to a level of detail that makes the scope of the solution clear but does not constrain evolutionary development2. This ensures that the solution architecture supports the business direction and the solution under development will be fit for its intended purpose3

Answer : C

The purpose of the Foundations Summary in AgilePM is to provide enough information to decide whether the project is likely to deliver a return on investment. This document serves as a comprehensive overview of the project's viability, including a high-level understanding of the business case, objectives, scope, and risks. It ensures that all stakeholders have a clear understanding of the project's potential value and feasibility before significant resources are committed.

AgilePM Foundation Handbook

'Agile Project Management: Creating Innovative Products' by Jim Highsmith

Answer : C

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.

Answer : C

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.

Answer : B

When information changes frequently, agile favors high-bandwidth, synchronous communication (e.g., video/teleconferences, facilitated sessions) that enables rapid clarification, shared understanding, and immediate adjustment. Static written documents become quickly outdated, encourage lag between change and consumption, and invite misinterpretation without fast feedback loops. Even email, while asynchronous, can be used for rapid, lightweight updates---but it still lacks the immediacy and richness of dialogue. AgilePM stresses visible progress, collaborative workshops, and frequent reviews to keep everyone aligned as facts evolve. Therefore, in a high-change context, a written document is typically the least effective mechanism to keep stakeholders synchronized, whereas live conversations and demonstrations better support timely inspection and adaptation.

Answer : B

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.