9.6.09

Ok Mr. Customer…your software is late what are you gonna do now?

How do projects get late? Well as Brooks says in the seminal Mythical Man Month, “projects get late one day at a time”. That day the developers spent listening to that lousy presentation or fixing their development environments instead of delivering features, the project was getting late. That day the developers spent time chasing requirements because the product owner could not be bothered, the project was getting late. Kind of reminds me of the boiled frog metaphor.

Scrum and daily releases mitigate this risk, but the can only succeed in an enabling context.

No comments: