Project Management

Game Theory in Management

by
Modelling Business Decisions and their Consequences

About this Blog

RSS

Recent Posts

George Jetson, Bring Me A Rock!

How To Obstruct A PMO

Rage, Rage Against The Dying Of The Project

Think You Have A Culture Problem? Think Again.

Finally! A GAAP Concept PMs Can Get Behind!

Categories

Game Theory, PMO, Politics, Risk Management, Strategic Management

Date

Forces Pushing Projects Towards Failure

linkedin twitter facebook Request to reuse this  

In previous blogs I’ve referred to the old saw, Availability, Affordability, Quality: Pick Any Two. To elaborate:

  • If it’s readily available and affordable, it’s probably not high quality.
  • If it’s high quality and available, it’s going to be expensive.
  • And, if it’s high quality and affordable, there’s probably going to be a lot of people in line in front of you to get one.

Another rather inescapable rule of free market economics: the price of an item or service is what aligns supply with demand. When the price of something is allowed to move freely, rare somethings will command higher prices, signaling the macro economy that more of that something is in demand. If there’s an excess, prices will fall, and the macro economy will respond in such a way that the resources used to produce the something could be better directed elsewhere.

Now consider what happens when some outside controlling influence, like government, decides that a certain good or service is “too important” to be allowed to have its price set by something as seemingly arbitrary as supply and demand – in the United States, gasoline in the late 1970s, or health care now. With the price set lower than it otherwise would be by something as arbitrary as bureaucrats, what happens to availability and quality? In most instances, they both suffer reverses from what they would have otherwise attained in a truly free marketplace. In the case of the gasoline shortages during the 1970s, since the artificially capped price of gasoline meant that oil producers could not with confidence make a profit, American oil production actually went down during the period, resulting in more unintended negative consequences to the macro economy. As far as health care is considered, the effects are identical: by employing the political “solution” of artificially holding down prices, there’s an abundance of evidence that both quality and availability are suffering (along with the patients!). Conversely, if those cases where the price is artificially set too high, surpluses will occur as consumers seek viable alternatives. If the something that is subjected to artificially high prices is perishable, massive amounts of waste will ensue – it’s pretty much automatic.

Meanwhile, Back In The Project Management World…

So, what does all of this basic economics have to do with Project Management, specifically? Let’s indulge in a little thought exercise, where we are setting up a PM consulting firm. Our start-up is capitalized, but we’re not rich. Since nobody is going to hire outside PM help that’s not provably advanced, we can’t skimp on the quality aspect of our service; nor will customers be inclined to wait, so our deployable consultants had better be able to arrive on-site relatively quickly, meaning that the availability parameter is already set. Can we, then, expect to be successful if we are charging high rates? Clearly not – as a startup, we’re going to have to come right out of the starting gate offering the full availability—quality —affordability (AQA) trifecta.

For the sake of this analysis, let’s say our new little PM consulting firm does pull off that very trifecta for its first three fiscal quarters, and we’re attracting more customers than we can quickly address. What to do? We will have to select which two aspects of the AQA model we want to maintain, since:

  • If our people have been providing a high-quality service at an affordable price, then they’re probably being underpaid, meaning that in order to retain them, our prices will need to go up;
  • If we fail to provide consultants to customers on a timely basis, they’ll look elsewhere;
  • If we hire additional people at bargain-basement rates, odds are our quality will quickly drop below that at which our customers could probably provide in-house.

In short, competition in the free marketplace will inevitably force us to decide which one of the two AQA functions we should embrace. There is, however, one aspect that allows an overcoming of these decision-driving factors: technology advances.

Referring back to gasoline prices, an advancement in extraction technology – hydraulic fracturing, or fracking – made so much more crude oil available in the United States that it changed energy prices around the world. Similarly, advances in the Project Management sciences will put those discovering or embracing them into a superior position to consistently deliver a higher-quality service at a more affordable price than the competition, with availability far easier to maintain. That’s one of the reasons I keep harping about the need for the PM community to not only return to performing legitimate management science research, but to shed the vestiges of the more archaic or obsolete aspects of PM.

To summarize, then: any formal guidance that posits a cap on PM budgets – a 5% limit is often bandied about – represents an arbitrary application of pressure on the price of the Project Management role, and is a force pushing any PMO so afflicted towards failure. The solution? I’m not going to offer a solution per se, other than to point out that any organization claiming to produce usable PM guidance that attempts to set a cap on Project Management (or any other function, for that matter) expenses has already exposed itself as being singularly backwards in the realm of basic economics.

Do we really want to accept guidance or advice from those organizations?

Posted on: February 04, 2019 09:37 PM | Permalink | Comments (5)

The Whippersnappers’ Main Deficiency: They Don’t Recognize When They’re Standing Next To A Flying Monkey

linkedin twitter facebook Request to reuse this  

In last weeks’ blog I discussed one of the advantages that PM’s new practitioners (ProjectManagement.com’s theme for January) have, that of being more likely to recognize a simple, direct solution to a complex problem should one be available, analogous to the Scarecrow realizing he can use the Tin Woodman’s axe to discombobulate the Wicked Witch’s castle guards in The Wizard of Oz (1939). But there are two sides to every coin, and the flip side of this one represents a real disadvantage to the new practitioner: They tend to believe the other members of their organization are automatically on their side.

A lot of the material presented in PM coursework, PMP® preparation classes, and PM-themed seminars can be rather sterile. Yes, yes, I know I’ve been advocating for a return to more, well, science-based analysis here in the management science arena, but I also freely admit that there’s a side to what Project Management practitioners do that defies quantification, let alone valid, logical analysis. And the quicker the new practitioner comes to a working knowledge of these more subjective factors, the better off they (and their project teams) will be.

Of course, not all PM curriculum are excessively or unrealistically sterile. Exhibit A is the use of Michael Maccoby’s excellent book The Gamesman[i] , which I have referenced in this blog before. Maccoby posits four archetypal behavior patterns among workers, so:

  • The Craftsman is interested in his output and its quality, but not so much for whom he works.
  • The Company Man tends to assume the persona of the macro organization.
  • The Jungle Fighter gets ahead through deceit and calumny, and
  • The Gamesman tends to see his pay and benefits not as food on the table or a roof over his head, but as tokens in some grand game. Because of this, he tends to have an advanced mastery of the “rules” of this “game,” and is more willing to take risks.

One of my main takeaways from Dr. Maccoby’s work as it applies to the PM world specifically is the working assumption that, in project teams of any significant size, there is going to be at least one Jungle Fighter. The new project team leader can count on it. The implications here include:

  • At least one of your team members will be engaging in office politics, usually egregiously so. My personal definition of office politics includes those activities that are designed to help the practitioners personally, but at the expense of the team or organization. The primary tactic here involves harming (or even destroying) the meritocracy elements of the group, and substituting a structure that benefits the Jungle Fighter specifically.
  • If this approach to satisfying ambition is allowed to succeed, the Company Men archetypes will see it, and tend to emulate it, given the fact that this type tends to assume the persona of the group anyway.
  • Once a sizable percentage of the project team recognizes that merit is not the exclusive – or even primary – vehicle for advancement, the odds of that project team realizing its objective on-time, on-budget decreases significantly.

Another landmine that I’ve encountered multiple times in real-life but have never seen addressed in PM literature or paper presentations has to do with the business model pathologies stemming from the teaching of the asset managers’ narrative, that the point of all management is to “maximize shareholder wealth.” Even though this assertion is in sharp contrast to the Project Managers’ goal of completing the customer-defined scope on-time, on-budget, I have yet to read other writers’ work pointing this out. The real-world difficulties that come from this clash of visions is probably most often manifested the first time the new PM approaches her organization’s accounting department with the request to collect actual costs at the reporting level of her project’s Work Breakdown Structure (WBS). The ability to collect actual costs based on the WBS is critical to the creation and maintenance of an Earned Value Management System, the only method for accurately gauging a project’s cost performance. Many of the accountants I’ve encountered, however, will be inclined to (a) maintain that cost performance is performed by comparing actual costs to budgets (which is false), and (b) collect actual costs based on the Organizational Breakdown Structure (OBS), which is, after all, an ordering of the company’s assets. By pushing the asset management narrative, whether through a genuine belief that that’s the way things are done, or due to a more vindictive motive, the information streams that the PM needs in order to make informed decisions are eroded or even prevented outright.

I am, however, at a loss as to how to articulate these two new-PM-practitioner traps without sounding cynical or even paranoid. I mean, “Welcome to the company, new PM practitioner. You should know that at least one member of your project team is going to advance their agenda at the rest of your team’s expense, and the most powerful single group within the company, Finance and Accounting, has been educated to believe that the information you need to succeed is the wrong way of doing business” is hardly a rational-sounding introduction. I suppose I could be a bit more circumspect, as in “beware the enemies within your project team, and those external to the project team, but internal to the company,” but that version is so vague as to sound even more psychotic.

I think I’ll settle for a Wizard of Oz reference.

 


[i] Maccoby, Michael. The Gamesman: The New Corporate Leaders. New York: Simon and Schuster,1976

Posted on: January 21, 2019 10:34 PM | Permalink | Comments (6)

Whippersnapper Advantage #23: They Are More Likely To Recognize When They’re Standing Next To A Tin Woodman

linkedin twitter facebook Request to reuse this  

In the classic film The Wizard of Oz (1939) there’s a scene that takes place in the Wicked Witch’s castle, where Dorothy, the Scarecrow, the Cowardly Lion, and the Tin Woodman (and Toto, too!) are cornered in the castle’s great room, with halberd-armed guards advancing menacingly towards them. The situation appears to be completely hopeless when the (supposedly brainless) Scarecrow notices that the massive candelabra hanging high in the room is suspended by a rope, and that rope just happens to be secured to a cleat on the wall right next to them. When the Wicked Witch, who is standing on a mezzanine above them, throws the large hourglass to the floor where it explodes, the Scarecrow simply grabs the Tin Woodsman’s axe and severs the rope (he doesn’t even remove the axe from the Tin Woodman’s grasp, or tell him what’s going on), dropping the massive candelabra onto the assembled guards. The protagonists then escape (temporarily) in the confusion.

I was reminded of this scene recently when I was working a little project of my own, restoring a 29-year-old sedan that I use for getting around my far-flung workplace. It has over 200,000 miles on the odometer, and it was looking so ratty that I was concerned my co-workers would take me for a ragamuffin. Here’s a before picture:

Posted on: January 14, 2019 09:46 PM | Permalink | Comments (1)

What's With The Push To Complete (One’s) Training?

linkedin twitter facebook Request to reuse this  

I was casually watching a Star Wars movie marathon a while back, and was struck by how often the practitioners of the Dark Side of The Force (“Sith”) would articulate a desire to complete the training of the young Jedis, Anakin and Luke Skywalker. What was so obviously missing in their nominal Jedi training? It became clear that they weren’t really interested in conveying advanced techniques, but instead wanted that training to go in a dramatically different, sinister direction.[i]

Meanwhile, Back In The Project Management World…

And now, on a completely different subject, in last week’s blog I discussed a potential paradigm shift in Project Management along the lines of moving away from predictive models and towards adaptive ones. I conceded that a complete abandonment of predictive models was highly unlikely, due to the fact that government-issued contracts tend to rely heavily on projects rarely overrunning their original baselines, and government-funded projects represent a significant part of the PM community that expects, or even demands, advanced proficiency in Project Management.

With this caveat in mind, I began to reminisce about the kind of project controls analyst I was when I could be considered a young Padawan learner “new practitioner” (ProjectManagement.com’s theme for January). When I showed some aptitude for Project Management in the company I worked for straight out of college, I was sent to a couple of week-long courses in Cost/Schedule Control System Criterion (C/SCSC). I absorbed all I was taught with enthusiasm. It was all brand-new to me, and, it appeared, fairly new to the management community at large.

After a while, though, I encountered significant issues that weren’t even hinted-at in the PM codex as-presented. After being effectively stiff-armed by every accountant I encountered while trying to do nothing more than set up a simple project cost performance measurement system, I began to wonder exactly what they thought they knew that I didn’t, and went back to school to get my MBA. A few semesters in, and I had my answer – their whole management philosophy, “maximize shareholder wealth,” was utterly at odds with the PM approach, of meeting the scope, cost, and schedule expectations of the customer. I had never seen this dichotomy articulated in any of the PM literature I had consumed, but I was also fairly certain that I wasn’t the only analyst in the world that had come to this realization. Clearly my indoctrination as a new PM practitioner had been incomplete (“Ben! Why didn’t you tell me?”[ii])

Fast forward to my more experienced years, after I had quite a few paper presentations, keynote speeches, and training track designs under my belt. I began to realize that those whom I considered my peers were becoming frustrated at the propensity of new practitioners to eschew process, only to re-encounter the entirely avoidable pitfalls that they themselves had had to overcome. It seemed to me that a large and growing percentage of the papers presented at major conferences were little more than eat-your-peas-style hectoring, on how everybody needed to acknowledge or accept the virtues of setting up a tightly-regulated cost and schedule baseline, fully integrated, don’t you know, complete with rigorous change control protocols, risk analysis, and reporting formats.

The more I thought about it, the more I realized that many of the seasoned paper-presenters were trending strongly towards the dark predictive model side of things, and that it was the Agile/Scrum crowd that represented a departure from that approach. Indeed, if it weren’t for the well-written structure of the Manifesto for Agile Software Development[iii], I seriously doubt that any if its basic assertions would be accepted today. With this as the backdrop, what can be said of the advantages and disadvantages of new PM practitioners?

Well, for starters, the newer practitioners have the advantage of not having been involved with projects during the era where United States government projects were more likely to be compelled to adopt a specific set of criteria governing how their projects would be run. With the decline of the Cost/Schedule Control System Criterion as management system absolutes, the use of the two main methodologies behind PM – Earned Value and Critical Path – had to stand on their own as information streams critical to improved project performance. New practitioners, then, have the advantage of the perspective that allows better PM information system integration than those who have been convinced that a rigorous, predictive model PM approach is a condition of doing business.

Another advantage that the whippersnappers newer practitioners have is that they naturally trend toward the adaptive models, owing to the underlying causes of the Project Manager role being nicknamed “the accidental profession.” After having successfully conquered some piece of scope that has led to more, similar work, the succeeding technician/engineer/programmer will often attract a request from their organizations to assemble a team and do more of that kind of work. At this point the newly-minted PM will rarely have a concept of the reasons behind rigorous change control procedures, or risk management approaches. They simply want to get the job done, and, I would speculate, will perceive these vestiges of the predictive model to be bureaucratic impediments to that goal, making the new practitioner more inclined to question their need at the very least, if not abandon them altogether.

One distinct sign, though, that the new practitioner is being trained in the wrong direction is if they develop a predilection for within-duel taunts, such as “Your powers have become weak, old man.”[iv] But at least the older masters don’t have to wear their hair in that weird rat-tail fashion.

 

 

 


[i] Lucasfilm Ltd. ; 20th Century Fox. (2013). Star wars original trilogy. [San Francisco] : Beverly Hills, Calif. :Lucasfilm ; Twentieth Century Fox Home Entertainment,

[ii] Ibid.

[iii] Kent Beck; James Grenning; Robert C. Martin; Mike Beedle; Jim Highsmith; Steve Mellor; Arie van Bennekum; Andrew Hunt; Ken Schwaber; Alistair Cockburn; Ron Jeffries; Jeff Sutherland; Ward Cunningham; Jon Kern; Dave Thomas; Martin Fowler; Brian Marick (2001). "Manifesto for Agile Software Development". https://agilemanifesto.org/. Retrieved 6 January 2019.

[iv] Lucasfilm Ltd. ; 20th Century Fox. (2013). Star wars original trilogy. [San Francisco] : Beverly Hills, Calif. :Lucasfilm ; Twentieth Century Fox Home Entertainment,

Posted on: January 07, 2019 09:55 PM | Permalink | Comments (8)

“And The Winner Of The Next PM Innovation Prize Is…”

linkedin twitter facebook Request to reuse this  

In previous blogs I have referenced the old saw of “Quality, availability, affordability: pick any two” as it applies to Project Management. This week I would also like to pull in a discussion of Thomas Kuhn’s groundbreaking book The Structure of Scientific Revolution (University of Chicago Press, 1962), and how manifestations of Kuhn’s theories have been exhibited in the introduction and advancement of Agile/Scrum PM strategies in the Information Technology arena.

Briefly, Kuhn pointed out that, while the common perception is that scientific and technological advances appear to occur at a somewhat steady pace, the opposite tends to be the truth. Kuhn actually introduced the term “paradigm shift,” and theorized that scientific advances follow this model:

Phase 1 is the pre-paradigm phase, marked by the absence of a single, widely-held theory that explains the preponderance of occurrences within the given field of study.

In Phase 2 normal science begins, where most problems can be evaluated within the hypothesis-experiment-confirmation/overturning cycle. However, should a series of problems or anomalies occur that the commonly-held theory/theories cannot adequately address, a series of cycles and then epicycles are layered onto the prevailing theory/theories to account for them.

Phase 3 is marked by the occurrence of the commonly-held paradigm proving unable to adequately address an increasing number of problems or anomalies, eventually leading to an entirely new paradigm being introduced that appears to not only explain the previous paradigm’s older problems, but also accounts for the newer issues that the old theories could not adequately explain.

Phase 4 represents the “paradigm shift,” where the new theory begins to displace the previous one(s) while overcoming the inertia inherent in the dramatic modification (or even overturning) of a widely-held belief structure.

Phase 5 is, essentially, a return to Phase 2, just with the new paradigm being used to solve problems, resolve anomalies, and predict future behaviors.[i]

So, how did the introduction of Agile/Scrum for Information Technology PM perform against this model? I believe we have yet to see the final answer to that question, since much of the literature for Agile/Scrum does not appear to present as a direct challenge to more traditional PM practices, but more like cycles and epicycles – distinct but less-than-revolutionary – changes to the current paradigm. For example, Agile/Scrum does not propose to eliminate the change control process, but to radically streamline it.

However, if there were to be a principal associated with Agile/Scrum that did represent a potential paradigm shift within the PM community, I believe that it would have to do with the fourth “value” of The Agile Manifesto[ii], “Responding to change over following a plan.”[iii] “Following a plan,” in traditional PM parlance, is “Freezing the baseline,” and informal changes to an established cost/schedule baseline are, to engage in a massive bit of understatement, strongly discouraged. Conversely, Agile/Scrum represents itself as being on the opposite side of traditional PM on a scale where the extremes are “Adaptive” and “Predictive,” with Agile on the former end, traditional PM on the latter. I have come to the conclusion that the reason Agile/Scrum was so readily embraced by the IT project management culture at large is due to the prohibitively lengthy and formalistic aspects of traditional change control, which typically involve the documented and approved establishment of:

  1. a change control board, with their authorities and thresholds spelled out in precise terms,
  2. a nominal schedule for reviewing baseline change proposals or requests (BCPs, or BCRs),
  3. another nominal timeline for how rejected BCPs/BCRs can be either appealed or amended for re-submission, and
  4. yet another timeline for how approved changes are to be implemented and reflected in the baseline documents, as well as how these changes are recorded in such a way as to establish an audit trail.

For projects like the ones that make up the brunt of Information Technology work, this process was simply untenable, which is why, for example, each Sprint Planning Meeting functions as a practical, streamlined substitute for the Baseline Change Control Board meetings. I believe that this aspect alone points unmistakably to a trend in Project Management away from the “predictive” models and towards the “adaptive” strategies, and not just for IT projects.

Of course, in the realm of government contracts, the various sponsor agencies have an obligation to provably spend the taxpayers’ money wisely, so the predictive models and traditional ways of conducting baseline changes will never be abandoned in their entirety. However, my prediction (it is, after all, New Year’s Eve) is that, as those project teams who are using the more adaptive approaches to their Statements of Work consistently out-perform those following the more predictive methods’ strategies, the adaptive methods will become more and more attractive and will gradually displace the more commonly- (and currently-) held paradigms, at which point the shift will have begun.

It will be at that point that we can recognize and confidently announce the innovative trend that changed Project Management.

 

 


[i] Wikipedia contributors. (2018, December 8). The Structure of Scientific Revolutions. In Wikipedia, The Free Encyclopedia. Retrieved 04:13, December 23, 2018, from https://en.wikipedia.org/w/index.php?title=The_Structure_of_Scientific_Revolutions&oldid=872736571

[ii] Retrieved from https://agilemanifesto.org/ on December 27, 2018, 16:45 MST.

[iii] Ibid.

Posted on: January 01, 2019 12:41 AM | Permalink | Comments (5)
ADVERTISEMENTS

"I love deadlines. I love the whooshing sound they make as they fly by."

- Douglas Adams

ADVERTISEMENT

Sponsors