Success Factors for Building and Managing High Performance Agile Software Development Teams

  • Dan Schilling Nguyen, Ph.D Mt Washington College National Online Program, 1015 Windward Ridge Parkway, Alpharetta, GA 30005, USA
Keywords: Agile Leadership Effectiveness, High Performance Agile Team, Leadership, Workplace Factors.


Information technology (IT) project success depends on having a project manager with effective decision-making, leadership, and project management (PM) skills. Project success also depends on completing the project in a given budget, time, and scope. However, there is a limited understanding of the Agile Leadership Effectiveness in Leading High Performance Team. Agile Software Development Team (ASDT) success factors such as organizational, people, process, project management, technical, trust, and so forth. The purpose of this paper is to present and synthesize the success factors generally accepted as critical in building and managing high performance ASDTs. These success factors consisted of ASDT (e.g., structure, member’ competencies, commitment and trust, communications, goals, and collaboration), leading ASDTs (e.g., leadership styles), workplace factors (e.g., cultural, functional and organizational differences), technologies (e.g., development tools), and organizational, people, process, and technical factors.  Organizational leaders and practitioners from various industries who are building or managing ASDTs could be of benefits with the researcher’s study outcomes by implementing or developing strategies or processes that could improve ASDT performance for long term sustainable development. High performance ASDT outcomes include improve team overall performance, time to the market, project success rate, and a better safer and healthier organizations or society.


Aldea, C.C., Popescua, A.D.,Draghicia,A. & Draghicib, G. (2012). ICT Tools Functionalities Analysis for the Decision Making Process of Their Implementation in Virtual Engineering Teams. Procedia Technology, 5(2012), 649–658. doi: 10.1016/j.protcy.2012.09.072

A Guide to the SCRUM BODY OF KNOWLEDGE (SBOKTM GUIDE)- 2013 Edition. @2013 SCRUMstudyTM, a brand of VMEdu, Inc.

P. Abrahamson et al. 2002. Agile software development methods – review and analysis. VTT Publications 478.

Beck, K., Andres, C., 2004. Extreme Programming Explained: Embrace Change.

Addison-Wesley Professional, Boston, MA.

Bunderson & Boumgarden. (2010). Structure and Learning in Self-Managed Teams. Why Bureaucratic” Teams Can Be Better Learners. Organization Science, 21(3), 609–624. doi: 10.1287/orsc.1090.0483

Berry, G. R. (2011). Enhancing effectiveness on virtual teams. Journal of Business Communication, 48(2) 186-206. doi:10.1177/0021943610397270

Cao,B.B. (2008). A Survey Study of Critical Success Factors in Agile Software Projects. Journal of Systems and Software. DOI: 10.1016/j.jss.2007.08.020

Connor, C. (2009). How Product Management Must Change to Enable the Agile Enterprise. Retrieved from

Espinosa, J.A., DeLone, W., & Lee, G. (2006). Global boundaries, task processes and IS project success: A field study. Information Technology & People, 19(4), 345-370. doi:10.1108/09593840610718036

eWorkshop. 2002. Summary of the First eWorkshop on Agile Methods. http://fcmd. April.

M. Fowler and J. Highsmith. 2001. The Agile Manifesto. Software Development Magazine. August. (Last accessed: December 2005).

Guba, E. G. (1981). Criteria for assessing the trustworthiness of naturalistic inquiries. Educational Communication and Technology Journal, 29 (1981), 75–91. doi:10.1007/BF02766777

Johnson, M.D., Hollenbeck, J.R., DeRue, D.S.,Barnes, C.M.,Jundt, D. (2013).Functional versus dysfunctional team change: Problem diagnosis and structural feedback for self-managed teams. Organizational Behavior and Human Decision Processes, 122(2013)1-11.

Joiner, B. (2012). How to Build an Agile Leader. Retrieved from

Korrapati, R., & Rapaka, S. (2009). Successful leadership styles in software projects in offshore centers in India. Allied Academies International Conference: Proceedings of the Academy of Information & Management Sciences (AIMS), 13(2), 56–59. Retrieved from

Kropp, M.(2015). Agile Success Factors - A qualitative studyabout what makes agile projects successful. DOI: 10.13140/RG.2.1.3593.2320

M. Lindvall et al. 2002. Empirical Findings in Agile Methods. Proceedings of Extreme Programming and Agile Methods – XP/Agile Universe 2002, pp. 197-207.

Mead, N., Carter, D., & Lutz, M. (1997). The state of software engineering education and training.

IEEE Software, 14(6), 22-25.

Nguyen, D.S. (2013). Workplace Factors That Shape Information Technology Project Success. Retrieved from ProQuest Dissertation and Theses database.

Palmer, S.R., Felsing, M., 2002. A Practical Guide to Feature-Driven Development. Prentice Hall PTR, Upper Saddle River, NJ.

Panteli, N. (2005).Trust in Global Virtual Teams. Retrieved from

Proulx, M. (2010).Are you an Agile Leader? – Nine questions for people managers. Retrieved from

Reed, A.H., & Knight, L.V. (2010). Project risk differences between virtual and co-located teams. Journal of Computer Information Systems, 51(1), 19-30. Retrieved from

Remus, U., & Wiener, M. (2009). Critical success factors for managing offshore software development projects. Journal of Global Information Technology Management, 12(1), 6–29. Retrieved from

Ruhleder, K. & Jordan, B. (2001). Co-constructing non-mutual realities: Delay generated trouble in distributed interaction. Computer Supported Cooperative Work, 10, 113-138. Retrieved from icar.univ‎

K. Schwaber, M. Beedle, Agile Software Development with Scrum, first ed., Prentice Hall PTR, Upper Saddle River, NJ, USA, 2001

Shachaf, P. (2008).Cultural diversity and information and communication technology impacts on global virtual teams: An exploratory study.Information & Management,45(2008),131–142. doi:10.1016/

H. Sharifi and Z. Zhang, “A Methodology for Achieving Agility in Manufacturing Organizations: An Introdu- ction,” International Journal of Production Economics, Vol. 62, No. 1-2, May 1999, pp. 7-22. doi:10.1016/ S0925-5273(98)00217-5

Sharma, D., Stone, M., & Ekinci, Y. (2009). IT governance and project management: A qualitative study. Journal of Database Marketing & Customer Strategy Management, 16(1), 29–50. doi:10.1057/dbm.2009.6

Shore, J., Warden, S., 2008. The Art of Agile Development. O’Reilly Media, Inc, Beijing Sebastopol, CA.

A. Trendowicz, J. Münch, Factors influencing software development productivity – state-of-the-art and industrial experiences, Advances in Computers 77 (2009) 185–241.

Wan,J.,Wang, R. (2010). Empirical Research on Critical Success Factors of Agile Software Process Improvement. J. Software Engineering & Applications, 2010, 3, 1131-1140 doi:10.4236/jsea.2010.312132 Published Online December 2010 (

J. Z. Zhang, L. Q. Qian and S. Y. Zhu, “An Overview of Agile Methodology,” Computer Applications and Soft- ware, Vol. 19, 2002, pp. 1-9.

Zhang, S., Tremaine, M., Egan, R., Milewski, A., Plotnick, L., O'Sullivan, P., Fjermestad, J. (2008). International Journal of e-Collaboration ,5(1),48-67.Retrieved from

Zimmermann, A. (2011). Interpersonal relationships in transnational, virtual teams: Towards a configurational perspective. International Journal of Management Reviews, 13, 59–78. doi: 10.1111/j.1468-2370.2010.00284.x

How to Cite
Nguyen, Ph.D, D. S. (2016). Success Factors for Building and Managing High Performance Agile Software Development Teams. International Journal of Computer (IJC), 20(1), 51-82. Retrieved from