Abstract
The importance of effective change control when developing software is well known throughout the Information Technology (IT) industry. Any software development project will deal with various forms of change throughout its lifetime, and without effective change control processes in place changes can lead to unforeseen, and often negative, consequences for an organization [8]. Yet despite this, change will almost always occur, and should therefore be anticipated. The change control processes in place on a software development project vary depending on the software development methodology being utilized [3]. Agile software development methodologies have become increasingly popular in recent years, with eighty-eight percent of respondents in a 2013 survey stating that their organization was practicing Agile [1]. According to Winter[1], Scrum is the most popular of the various Agile methodologies. A primary motivation for switching to Agile methodologies such as Scrum has been to better manage changes that were always inevitable, yet difficult to manage when utilizing traditional software development methodologies, such as the Waterfall methodology [4]. As more and more organizations transition to the Agile Scrum methodology, they must ensure processes are in place to properly control all forms of change. This includes changes that fall within the scope of a single project, as well as changes with a scope that extends across the enterprise. This paper explores various forms of change control and provides strategies and methods for effectively controlling and managing all forms of change on Agile software development projects.
Highlights
A critical aspect of successfully managing any software development project is effectively controlling change
When analyzing existing research on Agile methodologies, it is important to focus on the scope of the changes that are being discussed, as well as the individuals responsible for making decisions related to those changes
What is evident from analyzing the change control processes built into the Agile Scrum methodology is that processes to formally document and approve changes, such as the RFC and change control board (CCB) processes traditionally found when using the Waterfall methodology, do not exist
Summary
A critical aspect of successfully managing any software development project is effectively controlling change. When analyzing existing research on Agile methodologies, it is important to focus on the scope of the changes that are being discussed, as well as the individuals responsible for making decisions related to those changes. Focusing on the latter, Karlesky[10] describes the customer as the primary decision maker on an Agile project, making all decisions related to the project’s direction. Mangalaraj and Nerur[11] emphasize the importance of the customer in a project’s decision-making process, explaining that when utilizing Agile methodologies, most changes are Universal Journal of Management 4(1): 42-49, 2016 managed by a development team consisting of software developers and the customer. Design strategies are discussed that can be leveraged by development teams to create software that can accommodate and respond to change
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
