The document discusses the limitations and challenges of traditional estimation methods in project management, particularly in relation to feature delivery and client communication. It presents a no-estimate approach that relies on historical data and emphasizes smaller tasks to improve cycle times and focus on quality. The author encourages collaboration and education within the team and with clients to adapt to this new method.

1. No estimates
Easier for the team, beneficial for the client
By Lazar Milovic

2. What are estimates and
what are they used for
• What are estimates?
• What are estimates used for?
• Estimation methods

3. Challenges we had with
estimates
• Not knowing what story
point presents
• This led to wrongly
communicated milestones
• Which resulted in making
tradeoffs and having difficult
negotiation conversations
with the client

4. Why estimates are hard
delivery time = effort time + backlog time + WIP coordination time +
new work coming in between time + bottlenecks time +
blockers time + defects time
The cost of every feature is a function of two cost elements:
Essential complication
Accidental complication

5. Inspect & adapt
• New epic was coming, but
old way of estimating was
not working
• Velocity was fluctuating
• BUT one thing was
consistent - number of
delivered items per sprint

6. No estimate –
how we started
• Ditched previously used methods
• Rely on historical data
• Number of delivered items
• 90% of items finished in less than 8 days
• Average cycle time less than 4 days

7. No estimate - how to
• Have smaller tasks that can fit into the average cycle time
• Know your product well
• Collaborate with technical lead on tasks creation
• Educate the team to split the tasks in the right way

8. No estimate - challenges
• Have smaller tasks that can
fit into the average cycle
time :)
• Educate the client what an
item is - even one liner is an
item

9. Summary
• We still predict, but the scale is much smaller - can it be
done within ACT or not?
• Team is focused on bringing the quality and value, not on
having the precise estimates

10. Thank you all!
Shoot any questions you have :)