Ep. 3: Why software estimation sucks - podcast episode cover

Ep. 3: Why software estimation sucks

Oct 01, 202212 minEp. 3
--:--
--:--
Download Metacast podcast app
Listen to this episode in Metacast mobile app
Don't just listen to podcasts. Learn from them with transcripts, summaries, and chapters for every episode. Skim, search, and bookmark insights. Learn more

Episode description

For today’s episode, Asim Razzaq takes on the topic of software estimation and how engineers can improve the quality of estimates through calibration and confidence intervals. Most engineers in companies are overestimating, and in some cases, underestimating, their software estimates. With the help of Doug Hubbard’s research, Asim can share how company engineers can train themselves for a more accurate estimation rate.

[01:19] Software Estimation

[02:02] Ways to Train Estimation

[02:45] Challenges Often Faced on Estimation

[05:37] Asim’s Experience

[09:39] Training From Doug Hubbard’s Book

[10:45] Solutions Based on Training


Missing the Mark

There are many ways to miss the points when it comes to software estimation. This varies depending on the person’s confidence level and mindset towards the estimation and creates their own bias. Some cases occur based on underestimation, overestimation, and similarities-based results. Thankfully, each error has a training method that applies to help better hit the right mark.


Practice Makes Perfect

Luckily for software engineers, estimation can be trained and be improved overtime. With the right tools, you can conquer the constant overestimation and underestimation results. Asim based his techniques on Doug Hubbard’s teaching materials. Here, he managed to showcase an estimation that was a lot more accurate than initial estimation on the population of Italy.


Got questions or suggestions for future episodes? Just visit www.alwaysanengineer.org


Additional Resource Materials:

Doug Hubbard’s Website

For the best experience, listen in Metacast app for iOS or Android