16 min
Are Programmers Really To Blame For BAD Estimates? Healthy Software Developer
-
- Technology
When programmers are forced to estimate code on software projects and they turn out wrong, who's to blame? Are there other reasons why estimating software development projects are so hard, that are outside the control of each programmer?
In this episode, I share some of the unique properties of estimating code, and why programming estimates are different than many other types of work. Most of it boils down to treating software development like manufacturing, which is a repeatable process that doesn't involve as much teamwork. Programming on the other hand, is usually done on a team. And to meet the commitment forecasted by our estimate, we need help from other developers.
There are also complexities to our work that make estimating increased the chance that things go bad that are a symptom of misunderstanding the nature of programming by project managers, product managers, and scrum masters at some companies. They need help from software developers to understand why the number of variables increases the chance that estimates turn out bad, and that the degree of things being wrong can have disastrous consequences for business commitments that relied on estimates.
You can also watch this episode on YouTube.
Chapter markers / timelinks:
0:00 Introduction 1:19 Why Programming Is Unreliable 1:26 #1 Not Repeatable 2:06 #2 Too Many Variables 2:50 #3 Surface Understanding 4:06 #4 Unique Integration 4:59 #5 Low Diagnostic Output 6:08 #6 Knowledge Work Mismatch 7:19 #7 Undervalued Teamwork 8:20 Reduce Impact of Bad Estimates 8:42 #1 Reduce Estimated Work 10:06 #2 Keep Estimates With Estimators 11:26 #3 Estimate In Components 12:50 #4 Choose Familiar Technologies 13:56 #5 Find Native Integrations 15:04 #6 Stop Using Estimates 16:10 Episode Groove Visit me at JaymeEdwards.com
Find me on Facebook at JaymeEdwardsMedia
Find me on Twitter as @jaymeedwards
When programmers are forced to estimate code on software projects and they turn out wrong, who's to blame? Are there other reasons why estimating software development projects are so hard, that are outside the control of each programmer?
In this episode, I share some of the unique properties of estimating code, and why programming estimates are different than many other types of work. Most of it boils down to treating software development like manufacturing, which is a repeatable process that doesn't involve as much teamwork. Programming on the other hand, is usually done on a team. And to meet the commitment forecasted by our estimate, we need help from other developers.
There are also complexities to our work that make estimating increased the chance that things go bad that are a symptom of misunderstanding the nature of programming by project managers, product managers, and scrum masters at some companies. They need help from software developers to understand why the number of variables increases the chance that estimates turn out bad, and that the degree of things being wrong can have disastrous consequences for business commitments that relied on estimates.
You can also watch this episode on YouTube.
Chapter markers / timelinks:
0:00 Introduction 1:19 Why Programming Is Unreliable 1:26 #1 Not Repeatable 2:06 #2 Too Many Variables 2:50 #3 Surface Understanding 4:06 #4 Unique Integration 4:59 #5 Low Diagnostic Output 6:08 #6 Knowledge Work Mismatch 7:19 #7 Undervalued Teamwork 8:20 Reduce Impact of Bad Estimates 8:42 #1 Reduce Estimated Work 10:06 #2 Keep Estimates With Estimators 11:26 #3 Estimate In Components 12:50 #4 Choose Familiar Technologies 13:56 #5 Find Native Integrations 15:04 #6 Stop Using Estimates 16:10 Episode Groove Visit me at JaymeEdwards.com
Find me on Facebook at JaymeEdwardsMedia
Find me on Twitter as @jaymeedwards
16 min