During lunch one day, project managers Jim, Mary and Alex got into an argument over who was best adhering to their industry’s project success criteria. They all had sound arguments. The problem was, however, an “industry standard” did not appear to exist.
Jim argued that he follows the good old “triple constraints” or “iron triangle” concept (i.e., time, cost and scope). Mary sharply retorted that she follows the “quadruple constraints” concept (i.e., time, cost, scope and quality), where the “quality” minimized bugs or defects. Alex quickly asserted that he is the best project manager because in addition to what both Jim and Mary did, he reduces risk, meets stakeholder expectations, and his projects generally add value to the organization in extra areas.
Before we jump into crowning who we think should be project manager of the year, let’s take a trip down some project manager memory lane based on recent research I performed.
Although PMI’s A Guide to the Project Management Body of Knowledge (PMBOK® Guide) makes certain recommendations, the subject of project success criteria has been evolving for more than five decades.
In her report, Kate Davis summed up the different success criteria throughout the years:
1970s: Project success was centered on the “operations side, tools and techniques (‘iron triangle’).”
1980s: The technical components of the project and its relationship with the project team and project manager.
1990s: The “critical success factor” framework, and its subsequent dependence on both external and internal stakeholders.
21st century: The focus has primarily been on the stakeholder.
Davis isn’t the only one pointing out the changing criteria. Many academics and authors have noted the differences, including:
1980s: Jeffrey K. Pinto and Dennis P. Slevin expressed their frustration in a Project Management Journal article by asking, “How can we truly assess the outcome of a project when we (in the project management field) cannot fully agree on how project “success” should be determined?”
Late 1990s: David Baccarini from the Curtin University of Technology recounted in a Project Management Journal article that “a review of the project management literature provides no consistent interpretation of the term ‘project success.’”
2008: Graeme Thomas and Walter Fernández said that “although IT project failure is considered widespread, there is no commonly agreed definition of success and failure.” They described project success as being “a difficult and elusive concept, with many different meanings,” and hence called it protean (likening it to the Greek sea-god Proteus), based on its ability to continually change its “form to avoid capture.”
The current decade: Hans Georg Gemünden criticized the triple constraints for failing to consider other factors, such as stakeholder impact, since “value lies in the eye of the beholder.” He recommended project success criteria be based on its “targeted outcome and impact” to the organization’s business case.
Standish Group’s 2015 CHAOS Report redefined a successful project from one being “on time, on budget and on target,” to one being “on time, on budget and with a satisfactory result.” This redefinition was to ensure project deliverables met stakeholder expectations and also added value to the organization.
So based on the above, which of our three project managers (Jim, Mary or Alex) should be crowned project manager of the year?
Stevbros delivers project management training worldwide, our courses have proven their worldwide acceptance and reputation by being the choice of project management professionals in 168 countries.