Updated: Mar 2
Although it may seem controversial, not estimating is a valid option in the Agile environment. It is used in the 'Kanban' framework based on a queue of tasks. In Scrum, many teams embrace the no estimates approach, which works very well. In fact, for some people in the industry, estimations are considered a pure waste of time as they take effort that does not add value to the customer.
Naturally, this is a susceptible subject. Despite our inherent understanding of the challenges and lack of estimation efficiency, it’s an essential mechanism for managing projects.
Moreover, a look at the software industry reveals that the reason people resist this approach is the fear among managers. They believe that without estimating their project, they will not be able to monitor its progress and even worse, it will be either late in delivery or not delivered at all.
You can conduct this worthwhile experiment in your teams. It provides a new (advanced) approach for dealing with software projects. It reduces non-value processes and frees time for the team to deliver value.
It is essential to understand that not estimating does not mean you are not managing your team. No estimates reflect the management approach of fully trusting the team to take honest commitments and deliver them on time.
If you are still not comfortable with it, that’s fine. However, if you dare to experiment with no estimates, then below are some insights I have gained:
Try to prevent context switching to maximize development flow.
No estimates do not mean you cannot calculate your velocity. Counting the finished backlog items will do the trick.
Although there is no actual estimation done for a user story, it should still be small enough to take a maximum of 3-5 working days to complete (including all activities related to the acceptance criteria and the DoD of the specific story).
Do not use this approach if your team is new to the Agile environment; as mentioned earlier, it takes time for a team to build the infrastructure to operate and succeed with this approach.
A no estimates approach will only work in a fully committed team, constantly collaborating and having relevant experience in the technical aspects of the product.
When using the no estimates approach, your team must adopt the “swarming” method of handling the top prioritized stories and work on them until completion.
Keep your agility all the way. If your team is experiencing issues and things are not working as expected, do not push them to use this technique because you think it is best for them. If it does not work, go in another direction and try it again in future sprints.