Read Next

Staying With It: Design vs Marching, Lead vs Lag, Process vs Outcome, Trend Upwards vs HOHW

Before we get started, a couple announcements --

The first Ultraworking Work Weekend was a huge success.

We're having another one on 14 May and 15 May.

You can read more about the concept here. Starts at Noon Eastern Time on Saturday and Sunday 14/15 May. $140 to join if you're not currently a member at Ultraworking. Includes two 1-on-1 consulting calls and a 3 month membership to the Adherence League. You can sign up at this link.

If you're curious about Ultraworking, we've also fleshed out the concept of what we're trying to do more -- you can see it at the Ultraworking website.

How to Estimate like an Adult - A Developer's Guide

On Imported Blog

Usefully estimating software projects is difficult, but not impossible.

A lack of understanding about why we estimate, what to estimate, and how to estimate leads to a breakdown of trust and communication between developers and managers.

Developers end up feeling guilty that they're not meeting their estimates, and at the same time defensive: they were just estimates after all, right? Managers feel exasperated that everything is taking three times as long as it should. What are they doing all day?

This article is about fixing your estimates, and your estimation process. It's split in to two parts - the part you're reading, titled "How to Estimate like an Adolescent", and the part you're not yet reading, titled "How to Estimate like an Adult - What to Steal from Agile".

As an aside, if you're in a position where someone else is estimating work you're doing, get out. The work will be late, you will be blamed, and you will be miserable. Programming is meant to be fun, and setting yourself up for accusations of professional incompetence and the niggling feeling that maybe you are incompetent is the antithesis of fun. Seriously, get out.

Rendering New Theme...