hide

Read Next

Detailed Analysis of My Current Time/Habit/Life Tracking

One of the things I've gotten tremendous amounts of mileage out of it is tracking my time, habits, and life each day.

To put it simply - I now realize it's impossible to understand how your life is going without some careful observation. There's a lot of time each day, and knowing where that time goes, what you ate, what you did and didn't do... it's almost impossible to get a good picture of your life without some kind of measuring.

I'm going to you my newest tracking template, and then I'll give some analysis. Before I start though, I'd like to share a quote -

“A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over, beginning with a working simple system.” -John Gall

Thus, if you want to track your time, please do not attempt to track 20 things at once, because it's unlikely to work. I started very simply, as I described in "The Evolution of My Time/Habit/Life Tracking" - I'd recommend you read that post if you want to do something like this.

Estimating like an Adult - What to Steal from Agile...

On Imported Blog

In Part 1, we talked about the primary problems with estimating software development accurately:

But we ended with the uplifting message, which is if you plan for the former (by multiplying out your estimates), and make sure you adequately track the latter, then your estimates - when taken in aggregate - will probably be ok. And by ok, I mean better than 90% of other developers.

But who wants to be a 10 percenter, when you can be a 1 percenter?

I also promised Agile was going to solve all your problems ever when it came to estimating. This may not have been 100% accurate. What we are going to do is look at a whole bunch of Good Ideas(TM) that the Agile folk stole, curated, and invented when it comes to estimation.

It turns out that we humans get a little weird about time. However much you believe "six hours" is "just an estimate", however much buy-in there is from the team about this, and however many times you've accepted that there's always hidden complexity, if a six hour task takes eighteen hours, everyone gets a little squirrely.

Rendering New Theme...