In Microsoft D365FO implementations, there are many business processes involved that contain several scenarios and potentially many requirements per scenario. Also, a relationship/connection exists among them. To closely manage these many-to-many requirement relationships, formulating a comprehensive network of requirements for a process is a must for a project's success.

One easy way of remembering this could be by using the following definition: The RTM is a single repository/document that collects all the requirements, their relationship with other requirements, and their role in business processes – all pertinent information related to the solution, its development, and go-live.

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

The following is suggested as an end-to-end goal for requirements collection, analysis, and closure:

The preceding diagram shows the goals described as requirements belonging to a process/subprocess and how they influence the solution's 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 by leveraging the RTM and solution artifacts.

Now, let's learn how to collect, define, and scope the requirements.