n stages of the project’s lifecycle, and should provide a “toolkit” of ready-made templates and skeleton plans to save reinventing the wheel. Like maps however, different methods are more appropriate forMethodologies are often presented as the stuff of legends. Sit in any presentation by one of the large implementation companies, and by the fiftieth PowerPoint slide you’ll likely be convinced that the methodology being presented will create a flawless implementation, nearly run itself and eventually bring about world peace in our time. Each company presents its methodology as unique and special. When questioned about the competition, although using slightly more flowery language images of six year olds fighting on the playground still come to mind: My methodology can beat up your methodology!

Is there any method to all this methodology madness? On some level, a methodology plays an important part in any project. Similar to a road map, the methodology maps out what tasks should be completed during certain stages of the project’s lifecycle, and should provide a “toolkit” of ready-made templates and skeleton plans to save reinventing the wheel. Like maps however, different methods are more appropriate for

hodology being presented will create a flawless implementation, nearly run itself and eventually bring about world peace in our time. Each company presents its methodology as unique and special. When questioned about the competition, although using slightly more flowery language images of six year olds fighting on the playground still come to mind: My methodology can beat up your methodology!

Is there any method to all this methodology madness? On some level, a methodology plays an important part in any project. Similar to a road map, the methodology maps out what tasks should be completed during certain stages of the project’s lifecycle, and should provide a “toolkit” of ready-made templates and skeleton plans to save reinventing the wheel. Like maps however, different methods are more appropriate for

oned about the competition, although using slightly more flowery language images of six year olds fighting on the playground still come to mind: My methodology can beat up your methodology!

Is there any method to all this methodology madness? On some level, a methodology plays an important part in any project. Similar to a road map, the methodology maps out what tasks should be completed during certain stages of the project’s lifecycle, and should provide a “toolkit” of ready-made templates and skeleton plans to save reinventing the wheel. Like maps however, different methods are more appropriate for

ny method to all this methodology madness? On some level, a methodology plays an important part in any project. Similar to a road map, the methodology maps out what tasks should be completed during certain stages of the project’s lifecycle, and should provide a “toolkit” of ready-made templates and skeleton plans to save reinventing the wheel. Like maps however, different methods are more appropriate forn stages of the project’s lifecycle, and should provide a “toolkit” of ready-made templates and skeleton plans to save reinventing the wheel. Like maps however, different methods are more appropriate for different tasks. Just as you would not take a highly detailed topographic map for a drive across the country, any company advocating a “one methodology fits all” approach should immediately be regarded with an element of suspicion.

The dirty little secret in the implementation business is that all of these methodologies are nearly identical. Most are based on a standard Systems Development Lifecycle (SDLC) model, providing for well defined and demarcated phases from Planning and Analysis to Testing and Implementation. Again returning to our map analogy, endlessly debating methodologies, or strongly advocating one “brand” over the other is akin of arguing the merits of AAA versus Michelin road maps. While a methodology can provide a solid overall framework for a project, if you are not comfortable