February 15, 2007

...Learn TDD with Codemanship

Milestone Misunderstanding

I keep running across this misconception among project managers - namely that milestones are scheduled. "So we plan to enter the construction phase on May 13th at 2:32pm". And then when 2:32pm on May 13th finally arrives, and it transpires that the project is still in the earliest stages of requirements definition, the typical project manager response is to decree that the milestone has been reached.

It doesn't work like that, though. The lifecycle of a project is not the same thing as the process we use to execute it. There's a big difference between heating water for 5 minutes and heating water until it boils.


A fat lady singing yesterday

This might explain why so many projects end up serving tepid soup on the planned release date.
Posted 13 years, 11 months ago on February 15, 2007