PM 1.0 versus PM 2.0. What Is Next – Project Management 3.0?

There are certain individuals nowadays, mostly “project managers”, that decided to add version numbers to the notion of Project Management… And they created PM 1.0 and PM 2.0. More than probably the numbering idea came from the software domain: different tools and different versions for various needs.

A Little History Background

Since ancient times man created spectacular structures. The Great Pyramid of Giza around 2550 BC and The Great Wall of China around 206 BC are just two of them. Both survived to the test of time and even now are still standing. For this to happen it required a well done preparation, knowledge and workforce. These are clear proofs of an extraordinary construction engineering. Can we talk about project management at that moment? Perhaps not under this name but in reality it was exactly that.

The notion of Project Management as we know it today began to take root around year 1950. At that time organizations started to systematically apply management tools and techniques, developed in earlier years, to complex engineering projects. A famous tool that is being heavily used even today is the Gantt chart. One way or another businesses and other organizations began to see the benefit of organizing work around projects. So it was not just management anymore but it was also about projects: Project Management.

The Software Era

Managing projects on paper, as it was done at that time, is a time consuming process, prone to errors and costly. Obviously all these are true for medium to large projects and not for the small ones where the management is a lot easier to be done. But with the technology advances between 1970 and 1980 the first few project management related software solutions were created. This was an incredible increase in the performance of managing projects: faster computation, more reliable data and all the advantages that came from using a computer.

Over the years from users feedback better and better project management tools were created. Some solutions became deprecated and died while others evolved. However there is one particular point in time that can be considered a milestone: the evolution of Internet and the appearance of Web 2.0. All the fuss around the new World Wide Web aka Web 2.0 started around year 2000. The new way of dynamically rendering pages over the Internet offered an increased flexibility in using web application as a team as opposed to desktop ones. The gate to collaboration between team members directly through project management software was opened. And starting from this people created the term of Project Management 2.0


How did that happen? Simple: the traditional way of managing projects (this approach was renamed into PM 1.0 at a later stage) was lacking in one regard they say – collaboration – and the new approach came with that. It is a hard thing to believe that before Web 2.0 there was no collaboration between stakeholders when managing a project… Maybe not through the use of PM tools but there were other means like email, chat, phone etc. So is it right to say that PM 2.0 = PM 1.0 + collaboration? (more…)

By |2022-11-18T10:20:07+00:00August 8th, 2013|Project Management Methodology, Project Management Software|Comments Off on PM 1.0 versus PM 2.0. What Is Next – Project Management 3.0?

Project Management Software for Traditional vs. Agile Environments

Agile vs. Traditional project managementHow much does an agile project management software differ from a traditional project management software? On short: pretty much. But on the other side both types of products have many things in common.

Many say that agile is not a project management methodology but rather a product development methodology. But in many cases the companies prefer to treat the development as a project and hence the notion of agile project management. Now the agile and traditional approaches are totally different so the first thought would be that the software used to manage each type of projects to be different. The idea is that agile PM is not a method per se, but rather an umbrella term for different processes. In turn, agile processes are very different among them.

In Scrum there are small teams, usually collocated, no project manager, and very often there is no need for a software for the managing the project. The team is self organizing, team members are doing daily meetings, and the project is split in iterations that take maximum one month. At the end of each iteration it is decided the next one and so on… No one wants to loose time by updating a plan that keeps changing or to monitor the daily progress of the team with a project scheduling tool.

In other agile processes the iterations take longer but the main idea is that the project plan, the requirements and the product specifications are subject to change. So a traditional project management software does not solve these needs. Indeed it is necessary to have a monitoring process for the project and the team, a system for client communication etc. but due to the dynamic nature of the processes there is no needs to have fancy or complicated features. An agile product should be light in functionality, easy to use, easy to access and highly portable. (more…)

By |2022-11-18T10:20:08+00:00May 7th, 2013|Project Management Methodology, Project Management Software|Comments Off on Project Management Software for Traditional vs. Agile Environments

Traditional and Agile Project Management in a Nutshell

Project Management in a NutshellThere is no standard project management approach that works for all projects. The choice of the right approach for managing a project depends on various factors, ranging from the complexity and type of project to the experience in conducting projects of the organization, the customer’s willingness to be involved in the project, and the norm in the industry.

Traditional vs. Agile Projects

Essentially, there are two approaches: traditional and agile. Typically, traditional project management works for most construction projects, for example, where the whole project can be completed in one sequence, and the success is defined by completion of the deliverables in time and below budget. Agile project management is better suited to volatile and innovative projects, such as software development, where there are many risks, where the scope of the project is likely to change, and where an iterative methodology is needed so that risks are mitigated and opportunities fully exploited.

Traditional Project Management

Traditional project management is an established methodology for running projects in a sequential cycle: initiation, planning, executing, monitoring and controlling, and closing. For each of these five project steps, there are tools and techniques, such as the ones defined by the PMBOK®, the standard methodology for traditional project management. Traditional project management approaches include other methodologies, for example PRINCE2, adopted by the UK government organizations, but also by private organizations, such as Vodafone or Siemens.

Be Agile to Adapt to Changes

More and more projects have requirements that are subject to change as the project progresses, sometimes to keep up with the market conditions. In these cases, a traditional project management approach, in a single sequence of five processes, is not possible in order to take full advantage of the opportunities that may arise. Any projects associated with a high level of uncertainty (such as research and development, software development), or in highly volatile industries (such as IT or oil and gas industry), can benefit from an agile approach. (more…)

By |2022-11-18T10:20:08+00:00March 20th, 2013|Project Management Methodology|2 Comments
Go to Top