What’s probably the MOST popular and frustrating question you’ve come across when building a product: “How long do you think it will take to do task X?”
It’s frustrating on so many levels…
First, we need to produce an “accurate” estimate. If it’s off, there goes our ship date!
Next, we need to give a response that seems “realistic”, i.e. is going to meet the expectations or deadlines set by someone else.
Third, we need to be a fortune teller and anticipate things that come up in the course of completing task X.
Finally, we have to do it the moment we’re asked because we’re expected to know how long any task will take.
I don’t know about you, but despite building and launching a number of software products over the past 14 years, I still struggle with estimating how long a task will take to complete.
There are a number of approaches and methodologies that have sprung up over the years such as Waterfall, Agile and Lean whose goal is to provide a framework that helps engineers, designers, and product managers to estimate how long something will take to build and ship. However, as you’ve probably experienced, each one of these misses the mark.
In today’s episode we’ll dive into the aftershocks you may experience when it comes to following one of these approaches and providing product estimates.
Next week we’ll tackle an alternate approach that may seem too good to be true…
As you watch the episode you’ll learn the following:
Have you tried one of these approaches? Let us know in the comments below what you experienced when you did.
Listen to the episode on iTunes!
Help others enjoy it too by hitting the 👏🏽 !
Check out these additional resources on estimating stories for your product:
Create your free account to unlock your custom reading experience.