software project
Question
One of the instabilities of any software project is that somewhere during the development process, the project
will change. Designs may not be as strong as originally assumed, lines of code may simply not work as intended or stakeholders may completely change whatever they requested of the original project. Whichever the case may be, any changes must be managed to ensure that all individuals on a project are working with the correct version.
While change management is of paramount importance, the approach you take will vary from project to project. Use the scope of an information system (IS) project as an example. ISs can be massive conglomerates of software, hardware, data and so on. As you might expect, managing change in an IS is a significant challenge, but not an impossible one. For this Discussion, your challenge is to determine the key to managing change in IS projects.
To complete this Discussion
Post: Create an initial post in which you take a position on the requirements for successfully managing change in an IS project. In your post, recommend the steps, controls, processes etc. required to manage change in an IS project. Explain why your recommended steps, controls, processes etc. are effective in managing change in an IS project. Support your reasoning with at least one researched, academic source and examples from your own research of IS projects.