Requirement segmentation and ownership
During requirement gathering, an important aspect is to classify it. Classification plays a role in the lifecycle of a requirement and how it gets addressed downstream. An accurate classification of requirements helps project stakeholders to use it adeptly and see it 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 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 question WHEN:
- This classification is oriented to know when the requirement is needed so that it can be taken for solution and deployment...
