Roadmap for mapping business Requirements to Technical in ERP Projects
Ippili, Goutham (2025)
2025
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2025052616287
https://urn.fi/URN:NBN:fi:amk-2025052616287
Tiivistelmä
ERP systems require no introduction in the industrial landscape. The boom started in early 80’s, by implementing it majority of companies have streamlined their operations, improved agility and transparency in working. Every ERP implementation is unique and cannot apply same success formula to next implementation, because of two reasons 1. nature of business and 2. the geographic diversity it operates vary from organization to organization. The ERP consultant who implements needs to understand the entire client business from scratch, their history till present and provide comprehensive solution in ERP system. Majority of cases, there will be less emphasis given for initial stages of implementation like planning, requirement gathering and mapping, and more time spent of development ERP system. This is one of the reasons for failure in ERP implementation. Therefore, there is a need to develop a framework which gives the ERP stakeholders a much clarity, transparency, and control over requirement gathering and mapping process to streamline the development process smoothly thus reducing implementation failure.
The case company mentioned in the thesis is an IT consulting firm, in which the thesis researcher worked as developer, ERP functional consultant, and system analyst. The thesis followed a case study approach, for the thesis three case projects were considered where thesis researcher worked personally on these projects in the past, which is one of the reasons for choosing them.
The study of this thesis conducted in three phases; the first stage is to conduct a current state analysis on the three case projects to understand their practices towards requirement gathering a mapping. Second phase is to read and understand the best practices from various books, and articles about requirement mapping in ERP projects. The last and third phase is about proposing an initial framework and validating it.
The outcome of this thesis is a proposed roadmap based on three elements, 1. stakeholder identification and requirements elicitation, 2. requirement analysis and governance policy, 3. stakeholder engagement and sign-off. By combination of these elements ERP implementer could achieve their goal for mapping business to technical in ERP system.
The case company mentioned in the thesis is an IT consulting firm, in which the thesis researcher worked as developer, ERP functional consultant, and system analyst. The thesis followed a case study approach, for the thesis three case projects were considered where thesis researcher worked personally on these projects in the past, which is one of the reasons for choosing them.
The study of this thesis conducted in three phases; the first stage is to conduct a current state analysis on the three case projects to understand their practices towards requirement gathering a mapping. Second phase is to read and understand the best practices from various books, and articles about requirement mapping in ERP projects. The last and third phase is about proposing an initial framework and validating it.
The outcome of this thesis is a proposed roadmap based on three elements, 1. stakeholder identification and requirements elicitation, 2. requirement analysis and governance policy, 3. stakeholder engagement and sign-off. By combination of these elements ERP implementer could achieve their goal for mapping business to technical in ERP system.