Agile effort estimation in software development projects – case study
AbstractAim:Aim: The purpose of this paper is to identify common mistakes and pitfalls as well as best practices in estimating labor intensity in software projects. The quality of estimations in less experienced teams is often unsatisfactory, as a result of which estimation as part of the software development process is abandoned. The decision is usually justified by misunderstanding "agility". This article is part of the discussion on current trends in estimation, especially in the context of the new "no estimates" approach.
Design / Research methods: The publication is a case study based on the experience of a mature development team. The author, on the basis of literature-based estimation techniques, shows good and bad practices, as well as common mistakes in thinking and behavior.
Conclusions / findings: The key to correct estimation is: understanding the difference between labor intensity and time, ability to monitor performance, as well as how to analyze staff requirements for the team.
Originality / value of the article: The publication helps to master confidence-boosting techniques for any estimation (duration, and indirectly, the cost of software development) where requirements are known, but mainly at the stage of project implementation (design and implementation).
Limitations of the research: The work does not address the problems of initial estimation of projects, i.e. the estimation made in the early stages of planning.
Bjarnason, Elizabeth, et al. "A multi-case study of agile requirements engineering and the use of test cases as requirements." Information and Software Technology 77 (2016): 61-79.
Choudhari, Jitender, and Ugrasen Suman. "Story points based effort estimation model for software maintenance." Procedia Technology 4 (2012): 761-765.
Coelho, Evita, and Anirban Basu, Effort estimation in agile software development using story points, International Journal of Applied Information Systems (IJAIS) 3.7 (2012).
Farr, Leonard, and Henry J. Zagorski. Factors that Affect the Cost of Computer Programming. Volume Ii. a Quantitative Analysis. SYSTEM DEVELOPMENT CORP SANTA MONICA CA, 1964.
Jorgensen, Magne, and Martin Shepperd, A systematic review of software development cost estimation studies, Software Engineering, IEEE Transactions on 33.1 (2007): 33-53.
Jørgensen, Magne, and Stein Grimstad, The impact of irrelevant and misleading information on software development effort estimates: A randomized controlled field experiment, Software Engineering, IEEE Transactions on 37.5 (2011): 695-707.
Jørgensen, Magne, Unit Effects in Software Project Effort Estimation: Work-hours Gives Lower Effort Estimates than Workdays, Journal of Systems and Software 117 (2016): 274-81.
Mahnic, Viljan. "A case study on agile estimating and planning using scrum." Elektronika ir Elektrotechnika 111.5 (2011): 123-128.
Mahnič, Viljan, and Tomaž Hovelja, On using planning poker for estimating user stories, Journal of Systems and Software 85.9 (2012): 2086-2095.
Moløkken-Østvold, Kjetil, Nils Christian Haugen, and Hans Christian Benestad, Using planning poker for combining expert estimates in software projects, Journal of Systems and Software 81.12 (2008): 2106-2117.
Nelson, Edward Axel. Management handbook for the estimation of computer programming costs. No. TM-3225/000/01. SYSTEM DEVELOPMENT CORP SANTA MONICA CA, 1967.
Patton, Jeff, and Peter Economy, User story mapping: discover the whole story, build the right product. O'Reilly Media, Inc., 2014.
Pendharkar, Parag C., Girish H. Subramanian, and James A. Rodger, A probabilistic model for predicting software development effort, Software Engineering, IEEE Transactions on 31.7 (2005): 615-624.
Schwaber, Ken, and Mike Beedle, Agile Software Development with Scrum, Upper Saddle River, NJ: Prentice Hall, 2002.
Srinivasan, Krishnamoorthy, and Douglas Fisher, Machine learning approaches to estimating software development effort, Software Engineering, IEEE Transactions on 21.2 (1995): 126-137.
Schwaber, Ken and Jeff Sutherland. “The Scrum Guide - The Definitive Guide to Scrum: The Rules of the Game” (2013)
Torrecilla-Salinas, C. J., et al. "Estimating, planning and managing Agile Web development projects under a value-based perspective." Information and Software Technology 61 (2015): 124-144.
The aim of CEREM is to make scientific work available in accordance with the principle of open access. The rules mentioned below are important, as they enable CEREM and its publisher, the WSB University in Wrocław, to distribute the scientific work to a wide public while complying with specific legal requirements, at the same time protecting the rights of the authors.
The author transfers to the WSB University in Wrocław, free of charge and without territorial limitations, with all proprietary copyrights to the said piece of work in the understanding of the act of 4th February 1994 on copyrights and derivative rights (Journal of Laws of 1994, no. 24, item 83, as amended) on an exclusivity basis, i.e. the rights to:
1. Make the piece of work in question available via the Digital Library established by the WSB University in Wrocław.
2. Produce, record and reproduce in multiple copies the piece of work using any techniques whatsoever, including printing, reprography, magnetic recording and digital processing, and particularly its reproduction by recording on CDs and similar data carriers,
3. Use fragments of the piece of work for promotional purposes in publications, promotional materials, the Internet and Intranet type networks managed by the WSB University in Wrocław.
4. Store the piece of work into computer databases managed by the WSB University in Wrocław.
5. Copy and reproduce the piece of work using photo-mechanic technologies other than those commonly known at the time of the signature hereof (photocopies, Xerox copies etc.),
6. Process the piece of work, transferring it into an electronic form, and distribute it on the Internet without limitations.