Research Paper: Software Solution: Development of SOP for Change Request Form by Using Spira Team as Change Request Management Tool

Market environments are evolving at an increasingly exponential rate. Technological breakthroughs, the internet, globalization, and the emergence of highly volatile and competitive markets have made managing a company more complex. Enterprise resource planning (ERP) systems support the successful management of businesses under these conditions. As market needs and expectations change, so do the requirements for ERP systems; new or altered requirements are implemented continuously. This paper explores how companies can become more time-efficient in their specification of change requests and whether methods from requirements engineering can be applied. There is a risk of approving and developing changes that are not fully understood. Unwanted side effects can harm the ERP system and require costly corrections later. The methods and procedures are taken from design science research. We intended to develop an artifact that supports companies in becoming more time-efficient in the process of describing, evaluating, and prioritizing change requests. The present research study, concluded through MIS system analysis in a company, found that some methods from requirements engineering can be applied in this context. These methods include: Usage of requirements specification templates, Quality criteria, Categorization of requirements. The primary result of this research is an artifact in the form of a Standard Operating Procedure (SOP) for change requests in the context of changing ERP systems. This SOP was applied in the automotive supplier's change request practice, where feedback on the artifact was also gathered. Here's a simply we used spira team as example of a change request management tool form that can be used as part of the SOP.