So Which Is Better?
This was the inevitable purpose of this article was it not? To compare methodologies? Some methodologies were first implemented for IT purposes where others were considered best to provide quality outcomes, defects perfection, and recognizing and prioritizing risks and change. The United Kingdom’s PRINCE2 may argue it combines all of these into one perfect project management methodology.
The simple answer is that no methodology can fit all purposes, but is that really true? First what does a project mean?
According to my Random House Webster’s College Dictionary, a project is, “something that is planned or devised or an important undertaking, especially one involving considerable expense, personnel, and equipment." Project Management Basics defines a project as something that “will bring about change in some fashion," or something, “that has a defined starting point (A) and reaches a desired goal (B)."
If we take those definitions of a project, couldn’t a flower garden be created by using Agile management? Or risk or quality management? Sure it could be. When comparing project management methodologies, choosing one may come down to your teams and what sort of mindset they have or what training they’ve incurred. A flower garden could even be developed through a Six Sigma or Lean Six Sigma process. With the basics needed for a garden, however, a Waterfall approach may not be your best bet, especially in the case of the end-product. Waterfall could be used for the flower garden if change management was included in the process, however.
In the end, it is still difficult for a project manager to choose the right methodology. A forethought may be which methodology are you most familiar with and have had success with? There will always be debaters on which methodology is more effective and which has the best track method. Perhaps, when you look at project management methodology comparisons, it takes a blend of all of them to get from point A to point B.