Implementing Microsoft Dynamics 365 for Finance and Operations

Summary

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

While sharing insights on various requirement gathering techniques, we highlighted the need to listen well, lead the discussion, and negotiate the must-have requirements. The answer to fundamental questions (why, what, when, where, who, and how) and ...