Risk Analysis for Use in Methods of Agile Software Development Project Management
DOI:
https://doi.org/10.5585/gep.v5i2.255Keywords:
Projetos de Desenvolvimento de Software, Métodos Ágeis para Gestão de Projetos de Software, Riscos em Projetos de Software.Abstract
Agile Methodologies (AM) are offering improvements on several aspects of software development projects. However, its application involves risks, which are higher for some organizations and software projects. The objective of this work is to identify the main risks of applying AM in software development companies. The work involved an exploratory and qualitative research carried out by open and semi structured interviews with software project managers. Results show that many different risks can occur and with different impact on software projects. However, the main reasons behind all sort of risks are due to two aspects: (i) client involvement and (ii) experience and knowledge with agile practices.
References
Albino, R. D., Souza, C. A. D., & Prado, E. P. V. (2014, Janeiro/Abril). Benefícios alcançados por meio de um modelo de gestão ágil de projetos em uma empresa de jogos eletrônicos. Revista de Gestão e Projetos, 5.
Alliance, A. (2001). Principles: The Agile Alliance. Retrieved Feb 1, 2011, from http://www.agileallieance.org/principles.html
Beck, K. (2001). Manifesto for Agile Software Development. Retrieved Nov 1, 2011, from http://agilemanifesto.org/
Beck, K. (2004). Extreme Programming explained: embrance change. EUA: Addison-Wesley.
Boehm, & Turner, R. (2003). Balancing Agility and Discipline: A Guide for the Perplexed. EUA: Addison-Wesley.
Cockburn, A. (2002). Agile software development. EUA: Addison-Wesley.
Cohn, M. (2005). Agile Estimating and Planning. EUA: Prentice Hall.
Cooper, D., & Schindler, P. (2004). Método de Pesquisa em Administração. Porto Alegre: Bookman.
Fowler, M. (2005). The New Methodology. Retrieved Feb, 2011, from http://www.martinfowler.com/articles/newMethodology.html#PredictiveVersusAdaptive
Highsmith, J. (2004). Agile software development ecosystems. EUA: Addison-Wesley.
Hiranabe, K. (2008). Kanban Applied to Software Development: from Agile to Lean. Retrieved Mar, 2011, from http://www.infoq.com/articles/hiranabe-lean-agile-kanban
Jones, C. (2007). Estimating Software Costs : Bringing Realism to Estimating: Bringing Realism to Estimating: Mcgraw-hill.
Jørgensen, M. (2002). A review of studies on expert estimation of software development effort. The Journal of Systems and Software, 70(2), 37-60.
Jørgensen, M., & Shepperd, M. (2007). A Systematic Review of Software Development Cost Estimation Studies. Software Engineering, IEEE Transactions on, 33(1), 33-53. doi: 10.1109/TSE.2007.256943
Keith, C., & Cohn, M. (2008). How to Fall With Agile: Twenty Tips to Help You Avoid Success. Retrieved Mar, 2011, from http://www.mountaingoatsoftware.com/articles/40-how-to-fail-with-agile
Kerzner, H. R. (2009). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (10ª ed.): Wiley.
Kniberg, H. (2007). Scrum and XP from the Trenches: How We Do Scrum. EUA: C4Media Inc.
Larman, C., & Basili, V. R. (2003). Iterative and Incremental Development: A Brief History. Computer, 36, 47-56.
Malhotra, N. K. (2006). Pesquisa de Marketing: Uma Orientação. Porto Alegre: Bookman.
Mølkken-Østvold, K., & Jørgensen, M. (2005). A comparison of software project overruns - flexible versus sequential development models. Software Engineering, IEEE Transactions on, 31(9), 754-766. doi: 10.1109/TSE.2005.96
Paetsch, F., Eberlein, A., & Maurer, F. (2003). Requirements Engineering and Agile Software Development. In: Proceedings of the Twelfth International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises. IEEE Computer Society, 308-324.
PMI. (2009). Um Guia do Conhecimento em Gerenciamento de Projetos (4ª ed.). EUA: Project Management Institute.
Poppendieck, M., & Poppendieck, T. (2006). Implementing Lean Software Development: From Concept to Cash. EUA: Addison-Wesley Professional.
Schwaber, K. (2004). Agile Project Management with Scrum. EUA: Microsoft Press.
Schwaber, K. (2010). Control Chaos. Retrieved Mar, 2011, from http://www.controlchaos.com
Sheffield, J., & Lemétayer, J. (2013). Factors associated with the software development agility of successful projects. International Journal of Project Management, 31(3), 459-472. doi: Doi 10.1016/J.Ijproman.2012.09.011
Waters, K. (2007). Agile Software Development Made Easy. Retrieved Mar, 2011, from http://www.agile-software-development.com/2007/09/disadvantages-of-agile-software.html
Downloads
Published
How to Cite
Issue
Section
- Abstract 762
- PDF (Português (Brasil)) 449
