In this chapter, we explored scoping, defining requirements, and the RTM, along with their connection to business processes and subprocesses. While some implementations may consider a requirement document a good enough artifact to be able to continue with the project, we have seen that with a structured approach to documenting requirements, maintaining their traceability ensures that the entire project team has bonded with the goals they need to reach, which means there is a greater chance of achieving success.

While sharing insights of various requirement-gathering techniques, we highlighted the need to listen well, lead the discussion, and negotiate the must-have requirements. The answers to the fundamental business questions (why, what, when, where, who, and how) and requirement ownership ensures that a proper analysis is performed. This leads to selecting the right solution mapping, approaches, Independent Software Vendor (ISV) solutions, enhancements, and so on, thereby leading to the preparation of the solution blueprint, which is the backbone of the project.

The key deliverables from this chapter that we expect you to address are RTMs (comprising business processes and requirements), solution blueprints, and key decisions that are captured in a log.

In the next chapter, we will cover addressing configurations and data management by defining strategies and planning for them. You will also learn about golden configuration, various data management techniques, data cleansing, and quality validation recommendations. We will cover these topics from a solution perspective regarding data entities and data packages, the LCS configuration and data manager, Process Data Packages (PDP), and Azure DevOps/VSTS.