Empirical Research on Critical Success Factors of Agile Software Process Improvement

Jiangping Wan, Ruoting Wang

.

DOI: 10.4236/jsea.2010.312132                

Abstract

In this paper, we discuss agile software process improvement in P company with their description of process management in current level and analysis of problems, design the P Company success factors model in organizational culture, systems, products, customers, markets, leadership, technology and other key dimensions, which is verified through questionnaire in P company. In the end, we apply knowledge creation theory to analyze the open source software community with successful application of the typical agile software method, propose ten principles of knowledge creation in open source software community: Self-organizing, Code sharing, Adaptation, Usability, Sustention, Talent, Interaction, Collaboration, Happiness, and Democracy.

Keywords

Agile Methodology, Software Process Improvement, Critical Success Factor, Knowledge Creation, Open Source Software Community

Conflicts of Interest

The authors declare no conflicts of interest.

References

[1]	K. Beck, M. Beedle, et al., “Manifesto for Agile Software Development,” 2009. http://agilemanifesto.org
[2]	S. McConnell, “Rapid Development Taming Wild Software Schedules,” Microsoft Press, Washington DC, 1996.
[3]	C. L. Liu, “The Tutorial of Information Systems Project Management,” Tsinghua University Press, Beijing, 2005.
[4]	M. C. Paulk, “Extreme Programming from a CMM Perspective,” IEEE Software, Vol. 18, No. 6, 2001. pp. 19- 26. doi:10.1109/52.965798
[5]	M. C. Paulk, “Software Process Proverbs,” Crosstalk: The Journal of Defense Software Engineering, Vol. 10, No. 1, 1997, pp. 4-7.
[6]	Q. F. Min, “The Empirical Study of Critical Success Factors of ERP Implementation in China,” Doctoral Dissertation, Dalian University of Technology, Dalian, 2005.
[7]	H. Sharifi and Z. Zhang, “A Methodology for Achieving Agility in Manufacturing Organizations: An Introduction,” International Journal of Production Economics, Vol. 62, No. 1-2, May 1999, pp. 7-22. doi:10.1016/ S0925-5273(98)00217-5
[8]	J. Z. Zhang, L. Q. Qian and S. Y. Zhu, “An Overview of Agile Methodology,” Computer Applications and Software, Vol. 19, 2002, pp. 1-9.
[9]	J. Highsmith, “Agile Project Management: Creating Innovative Products,” Addison Wesley, Boston, 2004.
[10]	J. Li, “Martin Fowler Talks Scrum Certificate Authority, Agile Today and Tomorrow,” 2008. http://www.infoq. com/cn/news/2008/06/martin-agile-scrum
[11]	K. Conboy and B. Fitzgerald, “Agile Drivers, Capabilities, and Value: An Over Arching Assessment Framework for Systems Development,” In: K. C. Desouza, Ed., Agile Information Systems; Conceptualization, Construction, and Management, Butterworth-Heinemann, Burlington, 2007, pp. 207-221.
[12]	Z. Y. Lin, “SPSS Operation and Application,” Peking University Press, Beijing, 2007.
[13]	I. Nonaka, “The Knowledge Creating Company,” Harvard Business Review, Vol. 69, No. 6, 1991, pp. 96-104.
[14]	G. von Krogh, et al., “Enabling Knowledge Creation: How to Unlock the Mystery of Tacit Knowledge and Release the Power of Innovation,” Oxford University Press, New York, 2000.
[15]	E. Raymond, “The Cathedral and the Bazaar,” Knowledge, Technology, and Policy, Vol. 12, No. 3, 1999, pp. 23-49. doi:10.1007/s12130-999-1026-0
[16]	F. P. Brooks, Jr., “No Silver Bullet: Essence and Accidents of Software Engineering,” Computer, Vol. 20, No. 4, 1987, pp. 10-19. doi:10.1109/MC.1987.1663532
[17]	A. Mockus, R. T. Fielding and J. Herbsleb, “A Case Study of Open Source Software Development: The Apache Server,” Proceedings of the 22nd International Conference on Software Engineering, Limerick, 4-11 June 2000, pp. 263-272.
[18]	Netcraft Survey. http://www.netcraft.com/survey