When it comes to a software development project, we often kick off with the estimates. In fact, we estimate the amount of money, time, and the effort that is needed to reach the goals of the project. We also evaluate the estimate with the outcomes of the project, which is helping us to get a better understanding about the return of investment. Along with that, the team leaders and developers will be able to deliver maximum value to the customer budgets, while catering to their project goals.
At the time of developing a product in an agile environment, it is important to be highly dynamic. In other words, it is important to adapt according to the change fast. On the other hand, it is possible for the requirements to change quickly along with time. When there is a change in requirement, the initial estimations would be subjected to change. This is why it is a good idea to follow the #noestimates approach.
When following the #noestimates approach, it is possible to accelerate the development lifecycle. On the other hand, it is forcing the development teams to go ahead and slice their user stories into further small stories. This would deliver numerous benefits with iteration planning as well. That’s because the project managers would only need to understand the velocity and then figure out how many stories would fit in. By doing that, it is possible to reduce the amount of time that is spent on estimating.
All in all, #noestimates can be considered as a legitimate alternative that is available for the concept of story points estimation. However, it is important to remain mindful when extending this approach to the project level. By playing carefully with #noestimates concept, it is possible to get the maximum out of agile developments.
— Slimane Zouggari