A Vision of DevOps Requirements Change Management Standardization
Muhammad Azeem Akbar, Arif Ali Khan, Sajjad Mahmood, Saima Rafi

TL;DR
This paper proposes a maturity model for managing requirements change in DevOps within global software development, addressing communication and coordination challenges to improve process effectiveness.
Contribution
It introduces the DevOps-RCMIMM, a new maturity model tailored for GSD environments to enhance requirements change management in DevOps.
Findings
Initial results from a systematic literature review
Development of a preliminary DevOps-RCMIMM framework
Identification of key factors impacting change management
Abstract
DevOps (development and operations) aims to shorten the software development process and provide continuous delivery with high software quality. To get the potential gains of DevOps, the software development industry considering global software development (GSD) environment to hire skilled human resources and round-the-clock working hours. However, due to the lack of frequent communication and coordination in GSD, the planning and managing of the requirements change process becomes a challenging task. As in DevOps, requirements are not only shaped by development feedback but also by the operations team. This means requirements affect development, development affects operations and operations affect requirements. However, DevOps in GSD still faces many challenges in terms of requirement management. The purpose of this research project is to develop a DevOps requirement change management…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSoftware Engineering Techniques and Practices · Software System Performance and Reliability · Technology Assessment and Management
