Agile effort estimation in software development projects - case study

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.