paint-brush
What We Need To Do To Produce An “Accurate” Ship Date For Our Productby@poornima
168 reads

What We Need To Do To Produce An “Accurate” Ship Date For Our Product

by Poornima VijayashankerApril 10th, 2018
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

I don’t know about you but I HATE kale… That stupid leafy green vegetable with the ANDI score of 1000. It’s really hard to chew, and any time I see it on a menu, I skip it! But I get there are a lot of kale converts who go around saying, <em>“Eat your veggies, especially kale!”</em>

People Mentioned

Mention Thumbnail
Mention Thumbnail

Company Mentioned

Mention Thumbnail
featured image - What We Need To Do To Produce An “Accurate” Ship Date For Our Product
Poornima Vijayashanker HackerNoon profile picture

Hiten Shah Founder of Product Habits (right) and Poornima Vijayashanker, founder of Femgineer (left)

Interview with Hiten Shah Founder of Product Habits

I don’t know about you but I HATE kale… That stupid leafy green vegetable with the ANDI score of 1000. It’s really hard to chew, and any time I see it on a menu, I skip it! But I get there are a lot of kale converts who go around saying, “Eat your veggies, especially kale!”

OK, I know what you’re thinking, “What does this have to do with building software products and product estimates?”

Everything.

Just like we have to buckle down and eat our veggies (including kale) to stay healthy, there are a number of things we need to do in order to have accurate estimates that will ensure shipping a product consistently.

, we mentioned how a number of the current approach fall short. If you were left wondering what to do next, don’t fret, because in, today’s episode, Hiten Shah is back. He’ll be introducing a new approach to coming up with product estimates, and it’s coincidentally called the EAT method.

As you watch the episode you’ll learn:

  • How to perform each step of the EAT method — Explore, Adjust, and Task
  • What you CANNOT do with this approach
  • How this approach reduces ambiguity, which is the #1 cause of delays and scope creep

OK I know what you’re thinking… “Ugh not another approach!” OR, “This is never gonna fly at my company!”

Well that’s why after you’ve watched the episode, we want you to let us know what your concerns are in the comments below. We’ll be addressing a number of them in next week’s episode!

Listen to the episode on iTunes!

You can listen to this episode of Build on iTunes.

Enjoyed this post and want more?

Help others enjoy it too by hitting the 👏🏽 !

Check out these additional resources on estimating stories for your product:

Build is produced as a partnership between Femgineer and Pivotal Tracker. San Francisco video production by StartMotionMEDIA.