[#Agile] De l’intérêt de l’estimation ! via @hjvanderklis @Capgemini

De l’intérêt de l’estimation en agile !

Depuis quelques mois on voit passer régulièrement des débats dans la communauté agile autour du hashtag #noestimate, lancé par certains gurus, cette pratique fait l’objet de beaucoup de controverses. L’estimation serait inutile dès lors que l’équipe de développement se connaît bien, dans certain cas il serait nécessaire de ne définir que le nombre de user story à intégrer dans une itération. Cet article revient sur ce sujet en l’abordant d’un point de vue assez pragmatique.

The Agile Manifesto (2001) was introduced to state boldly how failures of traditional system development approaches could be overcome. Rather than doing something ‘agile’ as chasing the next buzz word, being agile is radically different. Changing requirements are a major cause of software cost estimating problems, and therefore embracing change sounds counter intuitive.

Kiera Conboy investigated in 2006 whether traditional cost estimation techniques are used on agile projects, and how mangers of agile development projects adhere to the traditional critical success factors cited by the traditional cost estimation literature. Cost estimation tools, or model-based estimation techniques use data collected from past projects combined with mathematical formulae to estimate project cost. The main model-based techniques include COCOMO, QSM SLIM, PRICE-S, SEER-SEM, and ESTIMACS. These estimation models produce an estimate of the cost, effort or duration of a project based on factors such as the size and desired functionality of the system. Expertise based approaches, based on personal memory and analogies are useful when no quantified, empirical data is available.

https://goo.gl/J2qepr

___________________________________

_____________________________________________________________________________