|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Lars Mathiassen, Ojelanki K. Ngwenyama, Ivan Aaen, "Managing Change in Software Process Improvement," IEEE Software, vol. 22, no. 6, pp. 84-91, November/December, 2005. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2005.159, author = {Lars Mathiassen and Ojelanki K. Ngwenyama and Ivan Aaen}, title = {Managing Change in Software Process Improvement}, journal ={IEEE Software}, volume = {22}, number = {6}, issn = {0740-7459}, year = {2005}, pages = {84-91}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2005.159}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Managing Change in Software Process Improvement IS - 6 SN - 0740-7459 SP84 EP91 EPD - 84-91 A1 - Lars Mathiassen, A1 - Ojelanki K. Ngwenyama, A1 - Ivan Aaen, PY - 2005 KW - change management KW - software process improvement KW - organizational change VL - 22 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2005.159
When software managers initiate SPI, most are ill prepared for the scale and complexity of the organizational change involved. Although they typically know how to deal with large software projects, few managers have sufficient experience with projects that transform organizations. To succeed with SPI, software managers must understand the context, know the organizational elements that are involved, and master the tactics that facilitate successful change.
Index Terms:
change management, software process improvement, organizational change
Citation:
Lars Mathiassen, Ojelanki K. Ngwenyama, Ivan Aaen, "Managing Change in Software Process Improvement," IEEE Software, vol. 22, no. 6, pp. 84-91, Nov.-Dec. 2005, doi:10.1109/MS.2005.159
Usage of this product signifies your acceptance of the Terms of Use.

