December 23, 2014
My Approach to Estimating without Requirements [Video]
Estimating without requirements isn't easy. It's even worse if you're using a 3-point approach incorrectly. Here's my approach, and how I use it to differentiate me from others (while reinforcing my experience).
I've often told you that I break a project up into a discovery project followed by the work in a second project, because it helps figure out all the details (in discovery) that no one talks about. It's still my favorite way to mitigate risks when estimating without requirements.
But sometimes a client doesn't want to go for a discovery project. They may not mind a discovery phase - but it's part of the overall project. And even though it's clear there aren't enough details in the requirements, it doesn't stop someone from asking about the delivery date, costs and more.
So you have to learn to estimate well - especially when estimating without requirements.
I use a 3-point estimating approach that I know others use. But often when I come across other's estimates I find that they're using the three points differently than I do. And the result is that if you use three incorrect points, your estimate will be wrong as well.
So here's my approach to estimating work when I don't have enough detail.
A story. An insight. A bite-sized way to help.
Get every article directly in your inbox every other day.
I won't send you spam. And I won't sell your name. Unsubscribe at any time.
About the Author
Chris Lema has spent twenty-five years in tech leadership, product development, and coaching. He builds AI-powered tools that help experts package what they know, build authority, and create programs people pay for. He writes about AI, leadership, and motivation.
