Johanna Rothman writes in Waterfall Projects Create Naivete:
But a waterfall project organization, where you have milestones such as “requirements complete” or “feature freeze” or “feature complete” provide a disservice to the entire project and management team. We know the requirements are not complete. We know the features will change. Saying they are complete or frozen won’t change reality. But those complete or frozen milestones provide a sense of inevitability about the eventual ending of the project, and infer that since we’re “meeting” (ha!) the project milestones, that we will continue to. That’s the naive part. (See There is No Such Thing as Percent Complete and Showing Project Progress (NOT percent complete) for why.)
What methodology do you think is the best way to manage and track a project? Tried and true Waterfall? Up and coming Agile?
Tags: project management
monthly email
RSS 2.0