Feeds & Connections

Our Mobi QR Code

Search the Key Stakeholders Blog
Navigation
Registration
What's new?
Tools

Professional Project Management, Training, and Consulting

Entries in Project Management (4)

Sunday
Oct252009

The Big Dig, In A Nutshell

An excellent chronicle of the mammoth project's triumphs and failures. This archive provides a wealth of knowledge about the massive Boston construction project: Big Dig Project (Boston) News - The New York Times. There are many lessons to learn from the project. And, the teaching is there for the learning.

Below: From catastrophe …

… to a brighter day in Boston

Friday
Apr102009

Why Bad Projects Are So Hard to Kill

Why is it hard to recognize impending failure?

 

The very nature of projects, something that has never been done before, means there is always a risk of failure. 


While some projects fail in pieces, cost over runs or late delivery, others fail in totality. Because projects are often times close to the brink of failure yet they ultimately succeed, sometimes it is difficult to predict abject failure. There are many examples of projects that looked over the precipice a few steps away from total disaster, ultimately achieving great success. Another reason why it is sometimes hard to recognize a project’s impending failure ismany organizations do not have processes in place to foresee it. These organizations lack proper controls, and do not collect relevant information. A change in the structure would go a long way to prevent project failures. Similarly, poor risk management is another cause for project failures that go undetected. Yet another cause of project failures that go unrecognized is “collective belief” noted by Royer. Typically the collective belief begins with the project’s evangelist and continues to grow like a snow ball rolling down a hill. The project’s  evangelist with an extensive and strong network, charisma, and a good reputation can fan the flames of collective belief in the project very quickly. Other factors like personal and organizational desire for a “winner” is further strong incentive for people to believe in the project. At this stage, a “group think” emerges that causes everyone to move in lockstep, critical thinking goes out the window and outliers with differing  opinions are censured.

What are some of the avoidance techniques for limiting the impact of bad projects?

 

The longer bad projects run, the greater their impact on the organization. Therefore, an early warning sign to indicate a project is a bad one is essential. Ideally, the warning should come very early in the project’s life cycle - the sooner the better. During the initiation phase or at the point of scope development, rigorous examination of the project’s viability including risk profile must take place: Is the project the best way for the organization to achieve its strategic goals? Are there other projects that can accomplish the organization’s strategic goals for less money, shorter duration and less risk? How does the project’s financial metrics like payback, ROI, IRR, or MIRR compare to the organization’s benchmarks? In addition, a SWOT analysis vis a vis the project, the firm, and market should also be done. If the project passes these types of gates and is executed, key factors like earned value, risk, quality and the project’s standing in the organization’s project portfolio must be continually managed. Significant changes that are detrimental to the project means the project should be seriously considered for termination. At the completion of rigorous assessment, if necessary the project should be shut down - immediately. This type of objective, rigorous, methodic process will limit a bad project’s negative impact on the organization and its customers.



By: Deon Robinson


Sunday
Mar222009

The Benefits of MoR Risk Management Training

Six months ago I undertook a course in MoR risk management and since then I have reaped the benefits of putting this knowledge to use. However, before I went on the course I thought I didn’t need any training. As the Project Manager in my company for the past 5 years, there had been many instances where I had saved projects from being adversely affected by negative changes in the work place, and I had finished my projects on time. So why did I have to do a risk management course? To be honest I was told I had to attend the course by my boss as it was the start of the company embracing continual learning for their staff. It wasn’t met with great enthusiasm by me, but now I’m glad I did the training because of the benefits it has brought to me as an individual and to the business.

MoR risk management is a detailed approach to managing risks but it is also an extremely logical approach to risk management. During our training, each step of MoR risk management was looked at in close detail, and the instructors ensured we understood each step before we moved on.

Since the training I have experienced the benefits of implementing MoR risk management in my workplace and I can now see that risk management is a highly organised approach to dealing with probable risks. It also brings down the level of uncertainty associated with a project and, since the level of uncertainty has decreased with projects, staff morale has increased. I have been able to mitigate the negative effects of risks when they actually occur, and avoid some risks altogether. I have been able to efficiently complete projects assigned to me on time, and I am better prepared to cope with sudden changes in the external or internal environment of work. The success ratio of my projects has increased and in turn this has increased the reputation of my firm. Unnecessary wastage of resources is avoided and ultimately profitability has increased.

MoR Risk Management training was no picnic-in-the-park as the learning curve was steep. The coursework covered was extensive, but the instructors were really good at taking their time and explaining each step. For example, we looked at the process of risk management and how it consists of six major steps, i.e. identifying possible risk factors; assessment of these factors; determining treatments for the risks; creation of a risk management plan; implementation of the plan; and evaluation of the plan. We then looked at situations in our own workplace to help the theory we had just learnt ‘cement’ in our minds. This also illustrated to us that theory and practice do go hand-in-hand and are not treated as separate entities, which is often the case when training courses are taught.

Another stage of MoR risk management was determining the treatment of risks and the instructors taught us the mnemonic ARRT. A = Avoidance (where an activity which contains a risk is not performed). R= Reduction (where steps are taken to minimise the negative effects as far as possible). R = Retention (where the loss due to the risk is accepted and borne by the firm when it occurs). T = Transfer (the loss due to the risk is shifted to another party through certain means, for instance – insurance). I have found the ARRT mnemonic a great memory jogger for when I’m back in the work place and working through each step of a risk assessment.

I do have one regret…not doing the MoR risk management course earlier! So don’t be like me and delay going onto a MoR risk management course, do it today!

By: Aimee Logan


Sunday
Mar222009

The Role of Project Managers

A project manager is one, who looks into the application of knowledge, skills, tools, and techniques to describe, organize, oversee and control the various project processes. Having said that, the roles and responsibilities of a project manager differ from company to company. It is important to understand what role a particular project manager will play in a certain company or organization.

The tasks to be handled by a project manager to successfully manage a project include:


  • Integration Management - This is developing and managing the direction of the project

  • Scope Management - This includes planning, defining and managing the scope of the project.

  • Time And Cost Management - This covers developing a schedule, allocating resources and managing funds for the project.

  • Quality Management - This involves taking care of the quality of the process in question such that it meets or even exceed various quality parameters set earlier.

  • Human Resource Management - A manager needs to take care of his team, encourage and motivate them and make sure the team moves in the right direction.

  • Communication Management - The manager needs to prepare a communication plan and make sure that there is a healthy communication, both horizontally and vertically.

  • Risk Management - Various risks involved in a project should be identified and a mitigation and contingency plan needs to be developed to ensure that the project is not derailed at any point.

  • Procurement Management - Various materials needed during the project needs to be procured and managed with the vendors and suppliers for successful completion of project.


A project manager is usually responsible for the success or the failure of the project. They first need to define the project and then build its work plan. If the scope of the project is not very clear, or the project is executing poorly, the manager is held accountable. However, this does not mean that the project manager does all the work by himself (which is practically impossible). There is an entire team under the project manager, which helps to achieve all the objectives of the project. However, if something goes wrong, the project manager is ultimately accountable.

Apart from this, depending on the size and the complexity of he project, a project manager may need to take on multiple roles. The project manager may need to assist with gathering business requirements, help to design a database management system or may prepare project documentation. A project manager may work full time on a large project, or may work part-time on various projects of smaller nature; or may alternatively handle various projects as well as handle other responsibilities like business analysis and business development.

At times, a project manager may have accountability but not authority. For example, he may be using certain resources but might not have direct control over those resources. At such times, the manager might find certain limitations over task execution, which might not take place as they might have liked. Not having direct control over the state of finances and finance allocation might cause ambiguity.

In order to be successful, the project manager must be given support by upper management and authority.

By: Tony Jacowski