Where can we start to collect and document requirements? What kind of requirements need to be collected? How do we ensure that all the requirements are collected?

You might be wondering about the previous questions, which are common for all ERP implementations. For a successful project, laying down a strong foundation right from the start is needed and collecting accurate and documented requirements is one such activity.

Even before engaging a solutions partner/advisor, a lot of organizations internally come up with a requirements list for their business transformation. The size of the organization, the businesses involved in the transformation, and the future state goals all play a significant role in driving requirements, and it is a project in itself. In any implementation methodology, exhaustive requirement collection and analysis is a must to be successful.

The focus of requirements collections should cover all the aspects of the existing business processes, as well as the future state of business processes. The requirement-gathering and understanding process is a highly scientific approach that needs niche expertise and the ability to pay attention to important details.