Introduction
Good requirements are essential to a Microsoft Dynamics 365 project. The key benefits that good requirements provide include:
A clear description of what needs to be done to allow a consultant to implement the solution.
Identification of exceptions and how they'll be handled to ensure that primary and secondary scenarios are addressed.
Acceptance criteria to help clarify when the requirement is satisfied.
A defined requirement, which can help reduce project scope creep.
Different projects will have different levels of formality in managing requirements. Smaller projects might use informal specification and management of requirements. For example, you could document a small, planned change with a meeting, the resulting whiteboard drawing, and a list of changes that will be completed. Alternatively, a larger project would be more formal, with well-defined requirements that are documented, reviewed, and prioritized for implementation.