0:0017:47

When Can We Ship?? A Fun Exercise in Estimating Software Tasks

Alicia Chen 17:47 2020

A 6.5-hour paint job turns into 14.5 hours once you ask the right questions

Product managers at Dropbox, the story goes, swapped notes on each engineer's multiplier: if John says a week, budget two; if Joe says a week, budget three. Alicia Chen, an early Dropbox engineer now Head of Engineering at CoProcure, was the one engineer a PM credited with a multiplier of one. When a missed date means angry users, sales and an exhausted team, what does she do before naming a ship date?

Learn the pre-estimate steps, buffers and pushback that make your ship dates hold

Watch on YouTube

In short

Alicia Chen, Head of Engineering at CoProcure, uses a room-painting exercise to show why software estimates are so often wrong. She argues that research, requirement confirmation and cheap prototypes must come before any date is given, that effort must be converted into elapsed time with multipliers and buffers, and that engineers need the courage to challenge unrealistic deadlines.

“You tell them, I don't know, but I'll be able to tell you in a few days.”
“And a cheap prototype can save you a lot of time.”

What you will learn

  • Treat research, requirement confirmation and prototyping as pre-estimate steps before committing to any date.
  • Use cheap prototypes to uncover hidden work, like the prep and extra coats that doubled the room-painting estimate.
  • Convert effort into elapsed time by accounting for meetings, vacation, outages and other interruptions with a multiplier and buffer.
  • Calibrate your estimating by measuring actual time on small and medium tasks and working up to larger ones.
  • Push back with evidence when an imposed deadline conflicts with your estimate instead of revising it downward under pressure.

Details

Level
Beginner
Format
Talk
Technical depth
Introductory technical
For
Early career, Mid-career, Senior individual contributor
Length
17:47
Published
June 2020

Questions this talk answers

Why are software estimates so often wrong?

People are over-optimistic and give a date before they understand the spec, the requirements and the hidden work. Experience helps, but software projects are rarely done exactly the same way twice.

What should you do before giving an estimate?

Research existing solutions, confirm requirements with the decision makers and build a cheap prototype. If asked for a date first, say you will have an answer in a few days and budget that time.

What is the difference between how long a task takes and when it can ship?

The first is the time strictly required to do the work; the second is elapsed time, which includes meetings, vacation, other projects and site outages. She accounts for the gap with a personal multiplier and buffer sized to the project's complexity and risk.

How can you get better at estimating?

Estimate small to medium tasks, measure the actual elapsed time, reflect on the gap and gradually work up to larger tasks. She points to Joel Spolsky's article on Evidence Based Scheduling for detail.

What should you do if someone else already set the deadline?

Do the estimating work yourself, and if your estimate differs sharply from the timeline, speak up. Do not revise your estimates downward because of pressure.

About this talk

Do you have trouble giving estimates for how long your software projects will take? Are you frustrated by people in your organization setting unreasonable timelines for delivering projects? This exercise (audience participation encouraged) will help demonstrate why estimation is hard, how you can get better at it, and how you can manage expectations related to deadlines.

Topics

Related talks

Browse the library