During requirement-gathering, an important aspect is to rightly classify them. Classification plays a vital role in the lifecycle of a requirement and how it's addressed downstream. Accurately classifying requirements helps project stakeholders use them adeptly and see them from various sides.
We recommend that you use the following techniques for classifying requirements and tailor-fit them based on the size, complexity, and business situation of your Dynamics 365 project:
- Ask the question What:
- What kind of requirement is this? For example, functional process-oriented, non-functional security, decision making, and so on.
- Impact on the business (must-have or good to have).
- Ask the question Why:
- This classification is oriented to weigh the importance of a requirement.
- Recommended usage values: must-have, good to have.
- Ask the...
