Editorial | Viewpoints | Papers | Case Studies | Community | Scene | Publications
The
full text of featured papers are available as PDF files. Click on the full
text link in the summary to access the full content in PDF format.
This article compares the changes from the PMBOK® Guide 2000 Edition to the PMBOK® Guide Third Edition (2004 Edition). Its purpose is to review the historical perspective of the Guides with reference to their process inputs and outputs. In particular, there have been conceptual changes that should be explained for the benefit of the project management community.
As a result of this research, as well as making suggestions for future editions, we strongly recommend improvements to the 2004 Edition by way of an amended update. This should be done in two stages. The Project Management Institute should move to correct invalid figures as First Stage Improvements, to avoid harm to the reputation of the Guides. This should be followed closely by a Second Stage project of improvements along the lines described in this paper.
Read the full text at The PMBOK® Guide Third Edition: An Analysis
When I think about all of the projects I have been involved in and consider all of the aspects of the management of those projects, what I would consider to be the single most important area of knowledge that has the most impact on the outcome of the project is 'Risk'
Why? Well, if we could predict all of the issues, both opportunities and risks, that would have an effect on our project and have a plan in place to avoid, mitigate, transfer or accept the outcome of the issue, would we not have a perfect project?
Probably yes, is the answer, but we all know that the very nature of risk dictates that we cannot predict them all.
Read the full text at The Danger of Failing to Manage Risk in Projects
Executives rely more and more on projects to marshal the cooperative behaviors needed for fast-tracking innovation and improving organization performance (Eisenhardt and Brown 1998). Although the central driver of performance is the quality of inputs like cooperative behavior, most organizations are focused on outputs like cost control and resource optimization (Liebowitz 1999, Devinney 2000, Hamel and Valikangas 2003).
An objective of the article is to widen debates from the relative merits of 'soft' behavioral skills versus 'hard' control skills. It engages debates about improvements in project practices for making informed decisions through lifecycles of product innovation in construction, telecommunications, defense, and financial services. Its discussion will interest people in the fields of organizational learning, knowledge management, project-based management, project integration management, and development of project professional standards.
Discussion in this article will explore a compelling question. If senior executives continue to favor 'soft' cooperation skills more than 'hard' skills for managing projects, and if management-by-projects becomes part of organization strategy, then how could the alarming rate of project failures be rectified? Tackling this question may contribute to advancing standards published in mainstream project bodies of knowledge and national competency standards.
Read the full text at Cooperative Competency as an Input Factor for Project Success
Project management data – which is obtained from time tracking information – is often an area that could be improved in many companies. Recent studies have shown that cost reductions of 6.5 percent are common from improvements in tracking time from the project management area alone. This compares with improvements of about 5 percent for billing automation or 1 percent for payroll automation.
Read the full text at Project Management: Using Data to Increase Profitability and Reduce Risks
There is an amusing joke that is circulating around the water cooler these days and it goes something like this:
A tourist walked into a pet shop and was looking at the animals on display. While he was there, another customer walked in and said to the shopkeeper, "I'll have a C monkey please." The shopkeeper nodded, went over to a cage at the side of the shop and took out a monkey. He fit a collar and leash, handed it to the customer, saying, "That'll be $5,000." The customer paid and walked out with his monkey. The tourist went over to the shopkeeper and said, "That is a very expensive monkey. Why did it cost so much?" The shopkeeper answered, "Ah, that monkey can program in C - very fast, tight code, no bugs, well worth the money." The tourist looked at the monkey in another cage. "That one's even more expensive! $10,000! What does it do?" "Oh, that one's a C++ monkey; it can manage object-oriented programming, Visual C++, even some Java. All the really useful stuff," said the shopkeeper. The tourist looked around for a little longer and saw a third monkey in a cage of its own. The price tag around its neck read $50,000. He gasped to the shopkeeper, "That one costs more than all the other put together! What on earth does it do?" The shopkeeper replied, "Well, I haven't actually seen it do anything but, the other monkeys call him the project manager."
I love a good joke and I truly feel the moment that we start taking ourselves too seriously or all important in our professional and personal lives we are in trouble. However, this joke has real meaning to me and perhaps to anyone else that had to manage a project of one type or another, who may have had the same feeling. It is an interesting way to start this article but in many respects this question, “What do you do around here?” is one of the most important ones that we need to be asking ourselves time and time again throughout the project cycle.
Read the full text at What Do You Do Around Here?
Negotiating is most often learned by the old fashioned "sink or swim" method when the representative for "our side" is told to "go negotiate and do your best". The difficulty with this method is obvious. Any early success will be accidental. Success and failure will produce a pattern of behavior from which the negotiator will learn how to negotiate. Unfortunately, this does not guarantee that the negotiator will have learned the most important or most effective behaviors to ensure continued success.
Learning from others' experience is an excellent way to increase success on purpose. Ten common problems we have discovered are presented below with suggestions for dealing with them. Because six of these common problems are related to planning, a checklist is presented as a guide for the negotiator. Use of the checklist will help enhance the negotiator's probability of success.
Read the full text at Negotiation success requires planning
Letters to the Editor are readers comments and observations on the Editorial, Viewpoint Columns, articles, papers or other notices of PM happenings appearing in the monthly issues of the Project Management World Today.
Editorial Policy: The PMFORUM® has no connection to any national or international project management organization nor does it reflect the policy of any project management professional or commercial organization. The PMFORUM® maintains an objective and impartial view of project management affairs. In the interests of advancing professional project management the PMFORUM® will publish contending and objective views on issues that reflect collegial differences and perspectives