Project Methodologies: Keep 'Em Flexible

Time and time again, I've seen organizations spend months devising the perfect project management methodology, sometimes even building it into their EPM tools, only to find people complain that it slows them down and doesn't add much value.

In many cases, they're right. The problem is that not all projects require every step, and in many cases there are easier ways to accomplish what certain steps are meant to do. Another mistake many people make is forcing task dependencies into the project template, such that design cannot happen until planning is completed, and construction cannot occur until the design is approved, and so on.

While this may be true of some projects, on many others, work does not occur in a linear fashion. For instance, certain segments of a project can udergo development while other segments are still being planned. On agile IT projects, the feedback from prototypes and iterations will often dictate the design, and rightfully so.

When it comes to methodologies, frameworks, and templates, the most effective organizations use one or more of following approaches:

- A methodology and project schedule template that allows project managers the discretion of which steps to apply to their project.

- Multiple methodologies and templates for various types of work, with streamlined versions for smaller or more flexible efforts.

- A methodology that identifies which items are mandatory for all projects versus those that are at the project manager's discretion.

In project management, as in pretty much any field, one size does not fit all.