Why organizations need OPMS to manage projects?

The following is another image, from another chapter in our recent book, #Project Management beyond #Waterfall and #Agile (https://goo.gl/hFYoHQ). It is about the SUKAD Seven Elements of Project Management Maturity, which is the model we use to help organizations build their OPMS, Organizational Project Management System.

The OPMS Model

Organizational Project Management; The Seven Elements of Project Management Maturity
This image is from the chapter on Organizational Project Management (#OPM); Chapter 9. The red is added here to illustrate the concept and is not in the original graphics.

Organizational Project Management System

The importance of this chapter (and graphics) is to remind everyone that guides like the #PMBOK Guide and #ISO21500 are not enough to manage projects. This is not a critique of those guides since these guides are NOT #PM_Methods. Further, these guides clear mandate is that organizations MUST HAVE an established Organizational Project Management System (#OPMS) that project managers and teams can use to manage projects.

In addition, if organizations do not have an OPMS, inclusive of policies, guidelines, methods, flowcharts, etc., that are #tailored to the type of projects the organization handles, then their project managers are reinventing the wheel with every project, which will likely result in less than optimal and consistent performance.

#OPMS will help organizations deliver projects faster, cheaper, better, and with a higher level of satisfaction.

The red in the graphics is to highlight that the core of the OPMS Model, which we developed in SUKAD back in 2010, is the CAMMP™ Model (CAMMP™ = The Customizable and Adaptable Methodology for Managing Projects™).

Did you get your copy of the book yet? You can find on Amazon or from SUKAD.

Advertisements