APMG Agile Foundation Practice Exam 2025 - Free Agile Foundation Practice Questions and Study Guide

In DSDM (Dynamic Systems Development Method), handling requirements that are not feasible to implement involves categorizing them appropriately based on their importance and practicality. By classifying them as "Should," it indicates that while these requirements are desirable and should be implemented if possible, they are not strictly essential. This approach allows teams to focus on delivering the most critical aspects of a project while recognizing that certain requirements might not fit within current constraints such as time, resources, or technology.

This classification method helps stakeholders maintain a clear understanding of priorities and makes it easier to make informed decisions about trade-offs during development. By emphasizing collaborative discussions about which requirements can realistically be met, DSDM promotes flexibility and responsiveness to changing circumstances.

In contrast, labeling them as "Must" would imply that they are essential and must be implemented, which is misleading given their infeasibility. Ignoring them entirely does not contribute to transparency or project clarity and could lead to misunderstandings within the team or with stakeholders. Classifying them as "Could" would suggest that they are low priority and only optional, which may not adequately reflect their importance in the context of the overall project goals.