Earlier this year, I wrote these tips to improve estimation: https://blog.amirathi.com/2018/02/05/science-of-software-estimation/ https://blog.amirathi.com/2018

Earlier this year, I wrote these tips to improve estimation: https://blog.amirathi.com/2018/02/05/science-of-software-estimation/ https://blog.amirathi.com/2018/02/05/science-of-software-est... I will summarize it here: - It's not just about code. New developers typically don't account time for testing, documentation, data migrations, backwards compatibility work and such - Spend a few hours to discover unknowns. Unknown unknowns can rattle the estimation big time whereas known unknowns can be factored into estimation with some upfront research. - Have a deeper conversation with product owners. Often you realize that some nice to have use case is taking 80% of the time and can be decoupled from the core feature. Win-Win.