Eight to Late

Sensemaking and Analytics for Organizations

Archive for the ‘Project Management’ Category

Scapegoats Pty Ltd

with 2 comments

Standish and others tell us that a significant percentage of projects fail for one reason or another. Many of these are projects that could have been saved by timely action, but instead end in ignominy due to inaction by various stakeholders. Transfixed by impending doom, those responsible are content to let problems fester until the potential for disaster translates to reality.

That’s when the proverbial stinky stuff hits the fan: project sponsors demand explanations about what went wrong, and how, and why. Above all, they want to know who is responsible. Then the finger pointing begins, culminating in the  identification of the scapegoat.  Once identified, the scapegoat is blamed, pilloried, and if he or she is really unfortunate (or the sponsor really ticked off), sacked.

Here’s what I reckon, though:  organisations can ill afford to lose individuals they have invested in over the years.  It would be so much easier if they could sack someone who didn’t matter. Alas, if only we had someone like….

——————————————————————————————————————————————————-

Scapegoats Proprietary Limited

“You mess up, we’ll fess up”


Scapegoats Pty Ltd offers consummate, professional scapegoats for hire. Our consultants are guaranteed to be technically and socially inept. They are people you can well afford to lose. So when you see early signs  that your project is going to fail, hire one our pros and rest assured that your team will survive intact. Why  get sacked for incompetence when you can sack someone else instead?

Here are some comments from our satisfied clients:

“…Our SPL consultant was a life saver. His incompetence ensured that no one on the team was blamed…” AP, Project Manager.

“…We asked for a standout consultant; Pete exceeded our expectations. His unhelpful manner coupled with his obnoxiousness made him an obvious scapegoat when our project went belly up…” TY, Project Manager.

So, don’t wait for fate – call us now on 1800 SCAPE GOAT.

Written by K

August 25, 2008 at 6:19 pm

Nice one, Dave

leave a comment »

It is strange how many issues come to one’s notice through conversations initiated around the coffee machine. Just the other day, I was getting myself a caffeine fix when Dave wandered by.

“How are you going, Dave?” I asked.

“Hmm good…. good,” he said, nodding absently. He’d looked a little abstracted lately – focusing on the reports he was doing for Finance, no doubt – or so I thought.  Then he looked at me and said, “Those reports I’m doing –  I still haven’t received all the requirements for them.”

I got a little alarmed; the first tranche of the reports were due next week. “Wasn’t Ralph supposed to get them to you a couple of weeks ago?” I asked.

“He hasn’t given me everything I need.”

“Have you reminded him?” An obvious question that had to be asked.

“Yes – several times.”

“And…what did he say?”

“He didn’t respond to my emails.”

Ah, Dave, Dave. You should know better than to send reminders through email and not follow-up.

Some background:  As you may have gathered, Ralph’s in Finance and Dave’s in IT. Dave does a fair bit of reporting work for Finance, hence the work connection between the two. They also happen to be located in the same building – less than a minute’s stroll apart.  Yet,  I reckon most of the communication between them is  via email. The only time they talk to each other, face-to-face, is at the occasional meeting.

Dave should have wandered over to Ralph’s office to have a chat. Although Dave had done the right thing (at least in letter, if not spirit) by sending Ralph reminders, he could have done much better. Email is a sub-optimal mode of communication  because, among other things,  emails can go “missing” (consider the familiar excuse: “Oh, I must have deleted it by mistake.”), or be misunderstood if the tone’s wrong or content incomplete.   On the other hand, face-to-face conversations can’t be ignored, and any potential misunderstandings can be sorted on the spot. Further, they also enable one to listen to what’s not said,  through observation of non-verbal signals or body language. So, the next time you start to type out that electronic missive, stop a minute and ask yourself, “Can I do this by conversation instead?” If so, do so.

In politically charged situations, where there’s a danger that a conversation may be denied or conveniently forgotten, one might consider sending a follow-up email that summarises the conversation and agreed actions. But in my experience that is rarely as useful as it’s made out to be.

Perhaps you’re wondering what happened about reports. Here’s the rest of the story. After some prompting Dave had a chat with Ralph and fixed up a time to discuss the reports. Dave got his missing requirements and a delivery date was agreed on. It looks as though the reports will be ready on time. What’s more, Dave tells me that he has been talking to Ralph a lot lately, showing him work in progress and getting useful feedback on it. Ralph has a good idea of what he’ll get in the end, and Dave has peace of mind knowing that his work is indeed on track. Even better, I’ve had some feedback from Ralph as well, commending Dave on his initiative and work. 

Happy customers reflect well on the team. Nice one, Dave!

Written by K

August 21, 2008 at 8:42 pm

Directions in project management research

with 2 comments

There’s a huge gap between research and practice in most disciplines.  Project management is no exception – many practitioners feel that project management research is an academic exercise with little practical value.1 Yet, research is important because, among other things, it gives rise to new techniques and perspectives, and also confirms (or disproves!) the often assumed utility of existing practices.  So, when a couple of well known academics with significant industry experience comment on directions in project management research, it behooves practitioners to read and understand their views. Hence this post in which I review a paper entitled, Project Management Research – The Challenge and Opportunity,  published by Aaron Shenhar and Dov Dvir in the June 2007 issue of the Project Management Journal.

The authors begin by stating that project management is one of the fastest growing disciplines. Many initiatives in organisations are managed as projects, even if they aren’t labelled so.  The authors observe that, “…in a paradoxical way, project failures, delays, and disappointments are much too common to be ignored…there seems to be an alarming gap between the needs of the discipline and what we know in order to fix them. From a research perspective there is a great opportunity to help close this gap…” Their stated aim is to record some observations on the challenges and opportunities in project management research, in order to stimulate discussion about the role of research in academics and industry. 

As the authors point out, people have been engaged in creating things since antiquity. The creation of large monuments such as the pyramids would have required some degree of organisation, planning and coordination of the efforts of a large number of people, regardless of the specifics of how that might have been done. In other words, these efforts were all projects that had to be managed somehow.  The authors define a project as, “a temporary organisation and process set up to achieve a specified goal under constraints of time, budget and other resources2 and project management as,  “the managerial activities needed to lead a project to a successful end.” They claim that modern project management, as a discipline, arose from the invention of the Program Evaluation and Review Technique (PERT) in the late 1950s,3 and take the position that the PMI’s project management standard is the premier standard of the day. Although I have no strong views on this, I have the feeling that some practitioners (and academics) may disagree.

The authors admit that the paper presents their subjective view of challenges and opportunities in project management research. Given this, it is perhaps unfair to read too much into what they say. Yet, it is instructive to look at an implicit assumption they make. It is clear from some of their remarks (and to a lesser extent the references at the end of the paper) that the authors use PMI standard as the basis for their discussion. This, quite naturally, affects their arguments and conclusions: i.e. everything discussed is viewed through the lens of that standard. Perhaps this is unavoidable: one has to make some assumptions to make any progress at all! In my opinion, though, authors of research papers should highlight their assumptions and limitations thereof, so that readers are fully aware of them.4

Anyway, to move on with the review, it is evident that despite all our methodologies and experience, project performance is alarmingly low. The authors quote statistics from the Standish Report and other studies to emphasise this. They concede that some failures can be ascribed to neglect or lack of planning, but highlight – through examples – that even well-managed and planned projects fail. Reasons for this are varied. For example, the original Iridium Project was deemed a failure because it did not take into account future business and technology trends. The construction of Denver International Airport is another example of high-profile failure. In that case, the reason for failure was that the automated baggage-handling system which was relatively unproven (and thus high risk) was treated as a standard well-proven system. On the other hand, the Sydney Opera House is now deemed a huge success despite being a classic example of project management failure – massively over time (by 16 years) and over budget ($100 million against an original budget of $ 7 million).

Citing these examples, the authors note that the problem is not with processes, rules or tools, as project management has plenty (perhaps too many!) of these. They suggest that the problem is at a conceptual level rather than process or practice, and that what’s required is a new understanding of what the discipline is about. This, they say, is the responsibility and challenge of future research.

After outlining the history of the development of project management as a discipline, the authors conclude that there is no central paradigm underlying research or practice of project management. They reckon that  inspiration for new ideas may be found in other, allied areas such as: Technology and Innovation Management Research, New Product Development Research, Entrepreneurship Literature and Operations Management. Research in technology/innovation management and new product development is more mature than project management research, and hence may suggest fruitful directions for future work. This has already started to happen: many project management researchers are focusing on new product development. In fact, I have reviewed a couple of papers relating to this area in earlier posts.5 Operations management offers another complementary direction; Goldratt’s critical chain technique is the best known example of a project management technique that emerged from operations management.

The authors believe that project management researchers have largely ignored developments in the above fields – and hence there are significant research opportunities to be exploited. As mentioned earlier, I believe this process has already begun: researchers are indeed looking to other fields for inspiration and ideas, as evidenced by the growing number of cross-disciplinary research papers in project management journals. On the flip side, most of these papers are written by researchers in project management, very few by those working in other fields. The reason for this, as the authors rightly point out, is that project management still has a low profile in management research and business schools. They comment that very little project management research is published in “prestigious” journals. This is true enough, research published in a high-profile journal is more likely to be read widely. Finally they comment that there is a disconnect between project management research and practice. This is well recognised, and I’ve already commented on it in the first paragraph and in the footnotes. It should also be noted, though, that this problem is universal – the gap between academics and practice exists in all disciplines, not just project management.

Based on the current state of project management research and the issues listed above, the authors propose a “wider research agenda to address these challenges and bring project management research to the forefront of the academic world“. I outline their views below.

The authors suggest two perspectives for future research:

  • The problem-driven perspective: This view focuses on solving specific project management problems such as scheduling / resource allocation and time overruns to name just two. Typically, solutions to such problems emerge from other fields. For example, solutions to scheduling and resource allocation problems have come from operations research and network theory; and solutions to time overruns have come from operations management (critical chain). The problem(!) with the problem-driven perspective is that there is no unifying theme. Which takes us to the next perspective…
  • The central paradigm perspective: This refers to a central, unifying theme for the discipline – or as the authors put it, a view of what project management is about. The authors identify three views:
    • Operational/process view: which views a project as a sequence of tasks to performed according to a plan.
    • Team/leadership view: which considers a project as an organisational unit that has to be managed (and lead, motivated etc.).
    • Strategic/business view: in which a project is considered to be a business-related activity, which (presumably) forms a part of the an organisation’s strategy.

Each of the above perspectives is based on different assumptions, metrics of success and also a different view of what it means to “manage a project.”

The authors correctly recognise that, “Although each direction is a world of its own, the real challenge is to combine them all into a unified view.” They go on to state that, “success in project management can only be achieved by an integrated, holistic view of the entire landscape of the project.” The three perspectives are, in fact, complementary; neglecting any of them will lead to project failure (italics mine). As the authors recognise, progress in these wide-ranging, diverse areas will require a multidisciplinary approach. Finally, the authors address the issue of publication of research in “leading” (aka “prestigious”) journals. They believe that raising the profile of project management in the broader world of management academia can be achieved by a) improving the acceptance rate of project management papers in highly-rated management journals and b) improving the standing of project management journals in academia.

In conclusion the authors make the following observations:

  • Project management is still evolving as a discipline, and is yet to establish its position amongst traditional management disciplines.
  • It lacks a strong theoretical framework and a coherent set of guiding principles
  • It is perhaps too complex to have a single underlying theory, but the interdisciplinary nature of the field and the variety of research challenges may help attract established researchers from other fields as well as young researchers starting out on an academic career.

I think these observations are incontrovertible, and as such they point to significant new opportunities and a bright future for project management research.


Footnotes:

1 I believe this is one of the reasons for the low general readership of project management research journals. Another reason is that journal papers are written in journalese – an  obscure dialect, familiar only to professional researchers. I’m doing my small bit to address this issue by posting occasional (hopefully, accessible!) paper reviews.

2 This seems to be a hybrid of the PMI and PRINCE2 definitions, with some other bits thrown in.

3 This attribution by the authors is perhaps a good example of how the PERT myth is propagated.

4 See my post on a memetic view of project management for more on the insiduousness of tacit assumptions in project management.

5 See my posts on utility of project management techniques for new product development and the effect of organizational culture of new product development project success, for example.

Written by K

August 15, 2008 at 6:27 am