APMG-International AgilePM-Foundation Online Access

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

Qualitative Measures: These provide insight into the underlying reasons, motivations, and emotions behind behaviors. Examples include interviews, open-ended surveys, and focus groups.

Other Options:

B: Quantitative measures focus on numerical data but lack context.

C: Leading indicators predict future performance but don’t explain behavior.

D: Lagging indicators reflect past performance, not the reasons behind it.

Key AgilePM Concepts Referenced:

Measurement and Analysis: AgilePM Handbook, Chapter 7, Section 7.5.

Statement 1: Correct. Offering supportive feedback after moments of insight reinforces learning and helps individuals process change more effectively.

Statement 2: Incorrect. While talks from experts may inform, they are less impactful than engaging individuals directly.

Key AgilePM Concepts Referenced:

Neuroscience in Change Management: AgilePM Handbook, Chapter 6, Section 6.2.

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.