Editorial | Viewpoints | Papers | 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.
by Rob Zanfardino
For those of you who do not recall the American story classic “The Wizard of Oz”, written by L. Frank Baum, in its most simplistic description it is a story about a teenage girl named Dorothy growing up in the heartlands of the United States, who receives a blow to the head and has a dream of this magical place where she is confronted with untold obstacles and challenges. With the help of friends she meets, each with their own strengths and short comings they work as a team, and overcome obstacles placed before them. In the end they help Dorothy reach her ultimate goal which is to find the great and powerful Wizard of Oz who will grant her wish to return home.
More and more as I started thinking about this story, I realized it could very easily be applied to project management and its disciplines than one would first realize. In fact I see so many similarities I would like to pursue this concept in this article. We talk about project management as if it applies only to the IT/IS world and we must remember that we are just a small part of this equation. In fact we need to spread our disciplines over to the business side and have them become as proficient as an IT/IS project team in the management of projects. For those of you who are first time project managers your first few projects will make you feel very much like Dorothy waking up in a strange land. At certain bends along the way you will run into your own types of munchkins and witches and you will have to become very nimble on your feet.
Read the full text at “Toto, I’ve a feeling we’re not in Kansas anymore” An Unbalanced Equation: Separating Facts from Fiction and Feelings
by Michel Thiry
A few years back, I was coaching project managers in a specific program for a large multinational organization. I encountered a strong reluctance from the project managers to use and update their project plans. When investigating the reasons for this, I discovered that the project plan template was imposed by the PMO. It had been designed, with a complete processes and procedures manual, by an external consultant who used a standard project plan model loosely based on the PMBOK Guide®. This model was all inclusive, designed for large projects and since the projects in this program, as most of the projects of the organization, did not exceed €2m-€5m the project plan template was much too detailed.
The project managers felt they were imposed something they did not need and were very reluctant to spend time on it. When I discussed this with the PMO people, I realized that they were aware of this and agreed it was too complicated for the projects, but had been told that the information was needed to input in the PMIS (Project Management Information System).
This is a typical situation that I have encountered in many organizations where PMOs are developed by a small core of experts and rolled out with the support of an “Enterprise Project Management Solution”.
Read the full text at The PMO: What Is It Really Managing?
by Matthias Gelbmann
Republished with permission from Q-Success.
While many brilliant books and articles have been written on good project
management, there is little attention paid to all the possibilities a
project manager has to create the appearance of managing a project well
without the burden of actually doing it. The following article is a summary
of such tactics, which I could not help noticing in many years of being
involved in software projects. It is intended for project managers as well
as people who monitor or supervise project managers, because we can prevent
dirty tricks better if we have studied them.
Read the full text at 10 Lessons in Guerilla Tactics of Project Management
by Nels Hoenig and Susan Snedaker
Your project is moving along on time and on schedule…well it’s pretty close anyway. Yes, there has been slippage on the delivery date and not all the features are there. Sure some costs came in a little over budget, but that is why it is called a plan and a budget. You have been generating status reports almost every week. The number of open bugs are dropping and you feel pretty good.
So, you walk into the monthly staff meeting confident, prepared to watch those other guys sweat. But, as you enter the room you notice the conversation comes to a halt and everyone is looking at you like you just ran over the plant manager’s dog. Everyone seems so relieved that you came to the meeting but you start to get nervous when the plant manager says to you, “For today’s staff meeting we are going to focus on your project and review its status exclusively. I also have the corporate CIO, Hank, “The Hammer,” on the speaker phone as he asked for this meeting specifically.” You suddenly feel like the guy in the deodorant commercials. However, you have all your status reports up to date and have been doing a good job of change management, so maybe this won’t be that bad…
Read the full text at The Project Status Meeting and How It Could Go
by Mark Kozak-Holland
Continuing with our series on Churchill the Project Manager (PM), this article discusses his background, and why he was so uniquely qualified in May 1940. It looks at the skills that he brought to bear to the project. It also asks what is a good background for a PM, what are the most desired traits, and how important is previous project experience along with the battle scars?
When Churchill became PM at the ripe age of 65 in 1940, he had to find the strength to lead his nation forward from the darkest and most dangerous of times, towards the defeat of a tenacious enemy. But Churchill was ready for this and he had always believed he had a fate with destiny that would require him to lead his nation. As he took the position he had a very good idea of what he was undertaking with the background he had and could draw from experience in tough international negotiations or fierce political battles. In many ways he was so well prepared that he wasted little time in taking actions.
Read the full text at Churchill the Project Manager - Part 2
by Bob Youker
For many organizations the capacity to effectively and efficiently manage projects from conception to completion should be considered a core competency. This means the entire project life cycle not just the implementation phase. Thus project management includes selecting the right projects as well as good implementation. Some people call this Strategic Project Management or just Strategic Management.
Professor Sebastian Green, Dean of the University College, Cork, Ireland defines Strategic Project Management as completing “projects which are of critical importance and enable the organization to have a competitive advantage”. There are three attributes to a core competence: it adds value to customers, it is not easily imitated and it opens up new possibilities in the future. Strategic PM includes the selection of the right projects as well as effective implementation. Thus we have a continuum of Strategic Objectives and Plan – Portfolio Management – Project Management – Organizations PM Capability. This takes an organization from Goals to Results. Doing this well can be a core competency.
Read the full text at Project Management as a Core Competency
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