Statement 1 : Incorrect . Agile is rooted in adaptability and tailoring practices to fit the specific needs of a project. Taking a single framework and applying it persistently reflects rigidity, which contradicts the Agile principles of flexibility and continuous improvement. AgilePM advocates selecting and combining frameworks (e.g., Scrum, Kanban) based on the project environment rather than sticking to one rigidly.

Statement 2 : Correct . Resilience, flexibility, and a willingness to learn are central to Agile practitioners. They must adapt to challenges and new information to ensure continuous delivery of value. This aligns with Agile values of embracing change over following strict plans and the AgilePM philosophy of iterative improvement.

Key AgilePM Concepts Referenced :

Flexibility over Rigidity : AgilePM Handbook, Chapter 1, Section 1.4 ( " The Agile Mindset " ).

Iterative Development and Learning : Chapter 3, Section 3.5 (Iterative Principles).

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 approach 3 4 .  This role is crucial as it provides the strategic direction and controls the funding/budget for the project 1 .

Comprehensive and Detailed 150 to 300 words Explanation From Exact Extract of Agile Project Management (paraphrased with Scrum alignment):

Scrum defines a small set of events within the Sprint to implement empiricism: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective . Additionally, the Sprint itself is the overarching event —a fixed-length container that sets the cadence for inspection and adaptation, culminating in a usable Increment . By contrast, Sprint Goal is a commitment associated with the Sprint, guiding focus and coherence; Sprint Backlog is an artifact representing the plan for the Sprint; and Product Increment is an artifact representing the latest integrated outcome meeting the Definition of Done . Therefore, among the options, only Sprint is a Scrum Event .

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.

The stated benefits of using DSDM include the business being better able to direct development, the reduced risk of building the wrong solution, and a smoother deployment process 2 .  These benefits stem from DSDM’s iterative approach and close collaboration with stakeholders 2 .

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 portfolio 2 . It provides a high-level definition of the overarching business driver and top-level objectives of the project.

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 .

AgilePM requires continued business justification . The Business Sponsor owns the investment decision and ensures funding remains warranted by expected benefits, value, and risk. If, at any point, the Sponsor cannot justify further funding in business terms —for example, the benefits have diminished, risk has escalated beyond tolerance, or opportunity costs are too high— stopping the project (or pivoting) is sound financial governance . Reports of overspend, lateness, or team dysfunction (options C and D) are important signals, but they trigger re-planning and decision-making ; they are not, by themselves, the governance criterion. Architectural opinions (A) do not substitute for business justification. The decisive governance action is to halt funding when the Business Case no longer holds , safeguarding organizational resources.

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

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 .