Project Management 2.0 (PM 2.0) seemed to be going the same way some Agile anarchists were trying to take software development which was essentially not to do project management and hope a group of people with good will and good luck will create something useful. Agile anarchists have largely been supplanted by Agile pragmatists who recognize an appropriate amount o management control is needed to achieve the best outcomes for the client; but what if anything is happening to PM 2.0?
From any perspective, not doing ‘project management’ is a really good idea if you and your client have no idea what’s needed, when it’s required, or how much budget is available. Journeys of pure exploration can be fun and can be highly creative but have very little to do with managing projects. As soon as some constraints become important, then some level of pragmatic management is needed, the different types of project and the type of management required is discussed in our WP 1072: http://www.mosaicprojects.com.au/WhitePapers/WP1072_Project_Size.pdf
Wikipedia (retrieved 22/9/2012 from: http://en.wikipedia.org/wiki/Project_management_2.0) lists the following differences between PM 2.0 and ‘traditional’ project management.
Whoever wrote this table has absolutely no idea what good traditional project management looks like and has probably never worked on a successful major project. Good traditional project management differs from this highly subjective and biased list in many ways:
The table is correct in so much as project management involves a degree of top down planning. Project management is about delivering a required output to the specifications requested by the client. The product or service is a failure if it does not meet the quality requirements set by the customer; which may include time, cost and scope parameters.
It is also correct in respect of the implied structure – projects work because there is an implied structure that sets a framework for collaboration. If you don’t know who is doing what it is nearly impossible to collaborate. Even Wikipedia and Linux have structure in their collaborative frameworks.
I have emphasized good project management throughout this post. Bad project management involves excessive attempts to ‘control the future’, lack of stakeholder involvement, excessive bureaucracy, and many other problems. These traits are bad management full stop.
One comment on the Wikipedia article is important though: PM 2.0 is good for small jobs. This is consistent with a survey of construction projects in the UK undertaken by the Chartered Institute of Building, focused on time management, which found that on ‘simple projects’ there was no difference in performance between those projects with a properly developed and managed schedule and those without. The same proportions finished early, on time and late.
However, as soon as the projects became ‘complex’; there was a marked difference in performance. Projects with effective schedule control performed significantly better than those without, and the bigger/more complex the project, the more significant the difference.
The CIOB’s findings and a closer look at many of the blogs and comments on both PM 2.0 and Agile seem to fit this trend. I would suggest two conclusions could be drawn:
In both of these circumstances traditional project management may not be appropriate. In fact I would question if either circumstance is actually a project given the definition of a project is to produce a defined product, service or result that meets the needs of a customer.
The challenge for senior organisational management is recognizing the threshold where PM 2.0 and ‘free form Agile’ cease to be appropriate and more traditional forms of project management are needed. Traditional project management does not mean ridged control, the type of project influences what’s needed (see: Projects aren’t projects – Typology) but appropriate systems do help optimize cost, time and quality to deliver client satisfaction.
This does not mean dumping the new ideas, rather melding them into an improved project management process. Agile software development fits in nicely to ‘rolling wave’ planning. Similarly some aspects of PM 2.0 can really help enhance team communication and collaboration. Used wisely, these ideas and technologies simply help improve the way projects work to deliver quality outputs to their clients. This change is really no different to the shift from faxes and carbon copy paper to emails. Good project management has always adapted to use improvements in processes and technology to improve the quality of service provided to the project’s clients. This next wave of improved technologies should be no different.
Management fads come and go – modern project management has been generally successful in achieving positive outcomes for well over 50 years now and continues to evolve and improve. My feeling is the concept of ‘PM 2.0’ is now dead and buried, but many of the useful ideas around collaborative technologies have become mainstream project management. Probably the most innovative move in this direction is the emergence of BIM in the construction sector (BIM = Building Information Modeling) for more on this topic see: http://www.mosaicprojects.com.au/WhitePapers/WP1082_BIM_Levels.pdf.