Blog

Thanks to my first post, i had the chance to have very interesting chat with some cowokers. One of the main concern was the mandatory apsect of the estimates in specific situations, mostly in order to arbitrate between two projects. First of all, let me clarify my thoughts about estimates. In order to provide reliable estimate, the following criteria have to be gathered : Team should know itself perfectly, knowing precisely what are the strenghts and weakness of each member. Team’s codebase should be either blank or without defects product should entierely identified and specified, and the Product Owner, as the domain experts, 100% sure of what the final product should be. I’ll post more on this later, but in my opinion, thoses conditions are at best anti-agile and at worst impossible to get. ...

This is a daily struggle of the developper nowadays : to give accurate estimates of the work we are doing, or we’ll have to do. When was the last time you succeeded to give an actually accurate estimate? You know, the one that perfectly fits the amount of work to do, in the exact time frame, with a clear vision of what you were meant to do? It’s been a while, isn’t it? ...