APMG-International Updated AgilePM-Foundation Exam Questions and Answers by presley

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.

Agility delivers the most benefit when uncertainty is high—when the problem is fuzzy, assumptions are unproven, stakeholders are still learning, and change is inevitable. In these contexts, iterative and incremental delivery, frequent feedback, and tight collaboration reduce risk by turning unknowns into knowns quickly. Timeboxing, continuous prioritization (e.g., MoSCoW), and demonstrable increments enable evidence-based decisions, allowing the team to pivot as understanding improves. Conversely, when the problem and solution are truly stable and well defined, predictive approaches can work adequately because variability is low. Likewise, heavy upfront research or a fully designed/contracted “optimal” solution implies a desire for certainty that may not exist; agile avoids over-investing in speculative plans by validating value early. Therefore, agility is most needed when discovery is paramount and adaptability is crucial—when the problem is unclear and change is inevitable.

According to the DSDM principle ‘Never Compromise Quality,’ the overall level of quality to be delivered within the solution should be agreed at the start of the project5. This principle ensures that quality is not compromised to recover from deviations; instead, the scope of the project will be dynamic6.

The DSDM process can indeed be configured and calibrated to cater for a range of projects, from those requiring light governance to those needing stronger governance1. This flexibility allows the DSDM process to be tailored to the specific needs of the project, ensuring that the right balance between control and agility is achieved1.