The Delivery Plan defined by DSDM has a planning horizon that includes the end of the project 7 . This plan looks towards the future, often months or years ahead, to guide the incremental delivery of the project’s outcomes.

Comprehensive and Detailed Explanation (paraphrased from AgilePM planning/prioritization guidance):

AgilePM expects teams to establish objective MoSCoW criteria and decision rules during Foundations . Foundations is where the delivery approach, governance, Business Case, scope boundaries, quality expectations, and planning baselines are agreed. Clarifying how Should and Could items will be interpreted (e.g., business value thresholds, regulatory constraints, UX standards, operational readiness factors) avoids later ambiguity, speeds trade-off decisions inside timeboxes, and protects the Business Case. While Feasibility assesses whether proceeding makes sense, and Development executes the timeboxed work, Foundations is the optimal moment to set shared prioritization rules, acceptance criteria structures, and change control protocols so that delivery can proceed predictably while flexing scope responsibly. Hence, C is the correct choice.

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 .

A Facilitated Workshop provides an interactive environment where all key players can contribute to the outcome 3 . It is a practice within Agile and DSDM that encourages collaboration and active participation from all stakeholders to shape the project’s direction and solutions.

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

AgilePM’s MoSCoW prioritization is always applied within a defined timeframe (e.g., a release or timebox). A requirement can be a Must Have for a specific delivery window while being a Should/Could when viewed across the whole product roadmap. Timeboxing, dependency considerations, and the need to deliver a coherent, usable increment by a certain date mean that priority is inherently time-contextual . While budget and resources influence overall planning, AgilePM fixes time and cost to provide predictability and flexes scope to protect quality; thus, the most legitimate driver for a requirement’s priority to change is the timeframe to which MoSCoW is applied. As delivery horizons shift (e.g., near-term release vs. later release), the same requirement’s priority may be re-appraised to ensure the Business Case and Product/Release Goals are met. Therefore, Different timeframe is the correct reason that explains variations in backlog priority.

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.

Supporting and Influencing Local Staff : Line leaders play a vital role in translating the change vision into action at the team level. They understand the specific needs and concerns of their teams and can act as a bridge between staff and senior management.

Other Options :

A : Local decision-making authority is beneficial but not their primary role.

B : Leaders are often deeply impacted by change.

D : Line leaders often juggle multiple responsibilities.

Key AgilePM Concepts Referenced :

Role of Line Leaders : AgilePM Handbook, Chapter 5, Section 5.6.

Line Leaders as Key Stakeholders : If line leaders are not fully engaged, they can create barriers to change implementation due to their influence on frontline staff. Providing them with privileged access ensures alignment and reduces resistance.

Other Options :

A : Seniority is irrelevant; engagement depends on roles and influence.

B : Authorization may not always be needed for every change.

C : Information access should be strategic, not indiscriminate.

Key AgilePM Concepts Referenced :

Engaging Stakeholders : AgilePM Handbook, Chapter 5, Section 5.4.

Timeboxing is the technique that allows for testing the achievability of objectives. This approach involves setting a fixed period (the Timebox) during which specific tasks or objectives must be completed. By focusing on what can be achieved within the set time frame, Timeboxing helps teams test and validate whether their objectives are realistic and attainable. This iterative approach ensures continuous assessment and adaptation, promoting efficient project management.

Certainty in Neuroscience : The brain seeks predictability and stability, which is supported by delivering change in small, incremental stages. This approach aligns with Agile ' s iterative and incremental delivery, providing clarity and reducing stress for individuals undergoing change.

Other Options :

B : Delegated decision-making relates to empowerment but does not directly address certainty.

C : Group social events foster connection, not certainty.

D : Public praise boosts morale but doesn’t satisfy the need for predictability.

Key AgilePM Concepts Referenced :

Iterative and Incremental Delivery : AgilePM Handbook, Chapter 3, Section 3.6.