In Dynamics 365 implementations, there are many business processes involved containing several scenarios and potentially many requirements per scenario. Also, there exists some relationship/connection among the requirements. In order to closely manage these many-to-many requirements relationships, formulating the comprehensive network of requirements for a process is a must for project success.

One easy way of remembering could be this definition: RTM is a single repository/document that collects all the requirements, their relationship with other requirements, their role in business processes, all pertinent information related to solution, development, and Go Live.

It is one live matrix that should be kept up to date throughout the life cycle of project and is often used by the project manager to re-baseline the project plan as needed.

We would like to suggest an end-to-end goal of requirements collection, analysis, and closure with the following diagram:

The preceding diagram shows the goals described as requirements belonging to a process/subprocess and influencing the solution analysis.

Solution acceptance becomes easier when an RTM is used. Also, stakeholders can validate and confirm whether each identified requirement meets the solution being delivered, leveraging the RTM and solution artifacts.

Let's now learn how to collect, define, and scope the requirements in your initiative in the next section.