8 Practical Rules For Producing Decent Estimates

This the second part of How I Was Able To Be Successful Even When Forced To Use Waterfall

Rule #1: take your time

Luckily, your estimation meeting will be much more fortunate than mine (see Part I).
In my previous Scrummerfall experience, since I was forced to produce a big-planning-up-front phase, I was used to always plan 2 or 3 days for it. I was asking for an estimation when my ignorance of the problem was at the maximum level, hence I needed a lot of analysis.

Advertisement

8 rules for being successful even when forced to use Waterfall (with a pretty good estimation)

Waterfall can work

No it cannot.
I mean: actually, it does, but adopting new and modern methodologies, you can dramatically improve your team productivity.
Yet, I believe most teams are using a mix of Agile and Waterfall. The reason is Waterfall is the sole methodology able to give the only information your manager needs to know: how much the project will cost and what’s the delivery date. About this, read the excellent post by Christopher Goldsbury Why Agile Adoption Fails in Some Organizations

The biggest difference between Waterfall and Agile

I attended Alberto Brandolini‘s speech at DDD Day.
Among all the interesting concepts he exposed, one struck me the most.