↓ Skip to main content

·128 words

I agree with this take by Jacob Kaplan-Moss that you should be able to estimate very accurately and then just not do it most of the time. Learning how to estimate is a non-negotiable part of building an intuition for software engineering. It’s not the estimation that we need, it’s the intuition.

The other reason why we wouldn’t do it all the time is because estimation (AND tracking, oftentimes people estimate without a tracking mechanism) has a real cost attached to it both to the team doing the estimations and to the org as a whole. Relying on estimations makes the entire organization less agile.

The follow-up post has a bunch of ways how you can estimate better but it doesn’t reference my preferred one: critical chain

https://jacobian.org/2021/may/20/estimation/

Alper Cugun
Author
Alper Cugun

Related

Improving the way we do posts is something I’ll be spending a bunch of attention on in the next months and here is an excellent guide of how to improve that part of the incident process.

·64 words
“I see operationally-minded engineers working cross-functionally with software development teams to help them grow in a few key areas: making outsourcing successful, speeding up time to value, and up-leveling their production chops.”

·57 words
A lot of the stuff here is our common sense when running projects and also our unique problem as a platform team trying to get stuff done with/for other teams. One thing that engineers tend to forget is how much agency they have: “Although you can’t control what other teams can do, you can influence them.”