Project Management Methodologies. Which one should I use? (Part I)
August 25th, 2010Hello everybody!
For this last post in August, we want to pick up the thread of posts about the 6 key reasons for the failure in project management. In the next two posts, we are going to take a look to project management methodologies and try to answer the questions that someone may encounter when dealing with this subject.
What meth
odologies are there? What are the differences among them? Which one is the most suitable for me?
Rationale behind the project management methodologies
Let’s define a project as the set of linked activities that have a common goal which has to be achieved in a predefined time span and with a particular set of resources. There are 3 key elements in the development of these activities: people, processes and tools/technologies. And therefore, the first step to take is to organize them so that they are completely coordinated.
Project management methodologies started to be defined in a formal way by the US army during the 50s. The goal was to reduce the number of projects that became out of hand and to solve some common problems that appear in most projects:
- The load of work that is planned is too low or too high.
- Costs surpass the project budget.
- The final result doesn’t have the expected quality or value.
In general, project management can be predictive or agile, and as in any other subject, there are supporters of one and the other.

1. No defining clearly the project objectives