Saturday, 25 August 2012

Project success and the role of good estimates

By Peter Young, PMP
 
As project managers, we crave the same thing – we want our project to be seen as a “success”, by the sponsor, business owner, governance, the team, end-users, ... everyone.
Successful projects deliver benefits, within constraints including scope, time and cost. To be seen as a success, a project needs to start out with good estimates of the time required to deliver the scope, and the cost of that time.
A key finding of KPMG’s NZ Project Management Survey in 2010[1], was that projects undertaken by New Zealand companies often perform poorly in at least one of the following areas – lack of timely delivery, cost over-runs, or inability to achieve the stated deliverables.
The survey found that only a third (36%) of NZ organisations reported consistent on-time delivery of projects, and only half (48%) reported projects being consistently delivered to budget. Internationally the Standish Group found only a third (32%) of all projects were delivered on time, on budget, with required features and functions. NZ project success rates are not unlike elsewhere.
As Project Managers, we are not enjoying “success” as often as we would like. At least some of the reasons for this can be traced back to how we go about preparing our estimates of time and cost to complete the project.
When looking back on a successful project, the following features will often be found to be true:
  • During planning, the scope was broken down into detailed requirements that were measurable (testable). This ensures everything gets estimated, and the estimators are clear on what will be an acceptable deliverable.
  • Estimation time was adequately budgeted, and a sound process used. It takes time, and a good process, to do a good job of estimation.
  • Estimates were provided by the people who did the work. This ensures estimates reflect the work rate of the people involved, and helps to get their buy-in.
  • Estimators understood the work and were able to estimate it accurately. Possibly the most challenging aspect of estimation. Get data on similar projects, to enable comparison. It also helps to break the work down into less complex tasks that can be more readily estimated. If in doubt, get advice from someone with more expertise, either in estimation techniques, the work being estimated, or both.
  • Actual delivery was regularly monitored against the project baseline, to validate that the work accomplished matched the plan. Where there are variances, re-forecast completion time and costs. This enables you to signal early if the project is likely to run ahead or behind on schedule or budget, and creates the opportunity for the project schedule and budget to be adjusted (using appropriate change control).
  • Scope variations were quickly identified and managed. Volumes can be written on this topic, and experienced project managers know that scope creep will torpedo the success of a project. The mitigation for this involves good communications within the project team and with stakeholders, an effective change control process that enables request for changes to baselines to be identified, assessed, estimated, approved or declined, documented, and communicated to all those that need to know.
  • Risks to the project were identified and managed effectively. Risks and issues need to be estimated, either quantified as time and cost, or at least identified qualitatively in a risk and issues register, enabling allowance to be made in project contingency estimates. Under-estimating risks will lead to insufficient contingency time and costs, which in turn can lead to under-estimation of schedule and budget for the project.
This is not an exhaustive list, you may have tips and techniques of your own that contribute to project success. Consider sharing the benefit of your experience with the wider project management community. See below for details on how to submit an article to PMINZ eNews.
Good luck with your project estimates, may all your projects be seen as successes.
Peter Young has managed business focused IT projects in the Wellington government sector over the past 5 years, and prior to that 25 years in international and local roles in the oil industry. He has held several volunteer roles with PMINZ and is the current Central Branch Chair. All rights reserved.

Monday, 16 July 2012

A Leader Without Followers is Just a Person Going For a Walk

By Allan Old, PMP

So how do you get others to walk with you ?

You have to know where you are going and know that you can’t get there by yourself.

You have to convince others that the goal is worthy of obtaining and that you need them.

This has to be done with integrity and be believable.

Share the vision
What
and Why. The what can be attractive, but the why is more important.


Get a team together and determine the basic principles that the team will operate under. This aligns the values of the team and the individuals with the why of the undertaking. Get the team to determine the how.


You may think you know the answer but by asking open ended questions team members will be able to provide input and then the resulting plans will a shared outcome. The quality of your questions will determine the quality of the answers. Become a better questioner.

Leaders manage the task and the sequence, provide the support and ask the people for outcomes. When asked to make decision, unless the consequences of a delay are serious, a leader will ask a question to maiximise the learning opportunity.

Think about those who you thought were good leaders. Did they tell you what to do or ask you?

Allan Old is a Project Manager at Alcatel-Lucent with over 20 years experience in change leadership and project management.

Authentic Leadership in Project Management

By Sean Whitaker, PMP

There are many aspects of project management that contribute to project success. There are the technical skills learned and the experience gained in applying them. There are also the soft skills such as communication and influencing that a project manager must possess. Perhaps most important amongst all these skills is the ability to lead and demonstrate leadership, particularly authentic leadership. A good project manager manages a project; a great project manager leads a project.

Leadership is the purposeful, influencing of followers. Without any of the three key elements is simply isn’t leadership. Without purpose, it is someone we may wish to follow who doesn’t want to lead. Influencing acknowledges that the leader has a vision and influences followers to go in a particular direction. Followers are the most important part of the equation though, for without followers there are no leaders. Great leaders respect their followers and great followers respect their leaders – it’s a mutual relationship. Leadership is a conscious deliberate decision. It is an acknowledgment there is a relationship between leader and follower, and each needs the other to exist. It is a commitment by those who choose to lead of continual personal and professional development. It is a commitment by those who choose to follow of support and feedback.

Leadership requires many different competencies to be displayed at different times as it is highly situational. The competencies you must display during times of high stress and challenge will be different from the competencies you must display during settled and stable times. However, the one core constant aspect of leadership is authenticity. Being authentic means having integrity and not pretending to be something you aren’t. People will always know when you are not being authentic. Being authentic means having a set of values and living them. Don’t be the ‘do as I say, not as I do’ type of leader. Being authentic means having a genuine interest in people and especially your followers. Begin authentic means having a balanced assessment of your own strengths and weaknesses.

It has been proven that good leadership enhances the chances of project success and the absence of leadership negatively affects the chances of project success. So if you want to increase the chances of project success practice your leadership skills and recognise that the best sort of leadership is authentic leadership so be true to yourself. Be true timber, not a thin veneer. 

Sean Whitaker is the current President of PMI New Zealand and author of The Practically Perfect Project Manager. Sean is also the co-owner of Falcon Training and spends his days teaching, speaking or writing about project management.

Saturday, 14 July 2012

Leadership: Ten Attributes of an Effective Leader

By Gary Nelson, PMP

[Also available as a Podcast]

Effective Leadership

No, it is not a myth. Many of us have actually seen this phenomenon, or even been lucky enough to work with an Effective Leader. If you were really lucky, they were also your manager/ team leader/ project manager etc.

Ok, to be fair, Effective Leadership is not quite that rare - but uncommon enough that people definitely appreciate it when they see it - and they wished they had it too.

My experience with an Effective Leader

1989 - Back at the beginning of my first career, straight out of University, I was quite fortunate to be hired by an Effective Leader. Of course, I did not know that at the time, but as time went on this became more and more apparent as teams came and went - and his stayed together. 

We identified with him, the team was loyal to him, even through a multi-year dissolution of the company into fragmented parts - in part, because he was also loyal to us. In the final stages of the corporate sell-off, while other departments in our part of the business saw an attrition rate of 70-90% over a 6 month period, his department lost only 2 people in the same period of time. And those only did so after long soul searching on career direction.

Over a period of 11 years, his team stayed together, until he recognized a strange truth - in order for his team to grow further on their personal development paths, he had to leave the company.

In our case, we not only had an Effective Leader, but an exceptional one.

So what makes an Effective Leader? And does that person need to be "the boss"?


Ten Attributes of an Effective Leader

1. Ethics

An Effective Leader has a firm ethical compass. They stick to what they know is right, even in the tough times, and do not easily bow to social pressure or fads. They also make sure that their team embodies the same ethics - honesty, looking out for the customer, doing the right things - right, etc. And not a "closet ethic" - it shows in how they conduct themselves every day.

2. People Skills

An Effective Leader has good people skills, and can communicate effectively with their peers and their team, as well as up and down the corporate ladder. They don't have to be a gracious public speaker to hundreds or thousands, but they do communicate well within their sphere of influence. And Exceptional Leaders develop a significant sphere of influence.

3. Not the Boss

In those 11 years, except for a few periods while on projects with a different department, I did not have a Boss. I had a Manager, a Coach, and a Leader - not a "Boss". An effective leader works with their team, encourages and supports them. Sure, there are plenty of times the leader needs to have things done a certain way, in a certain time - but the difference lies in how they communicate it. A Boss demands the work be done - a Leader requests it and expects it do be done properly - and those working for them are dedicated to doing just that.

4. Praise in Public - Criticize in Private

We have all heard this mantra - and it certainly makes a difference not being "dressed down" in public. However, an Effective Leader takes this one step further - when discussing issues in private, the Effective Leader rarely brow-beats their team member - even if they want to. They address the issues, the behaviour - whatever was at fault, but in a way that does not rip the team apart. If anything, their expression of caring for the team member while firmly addressing the issues at fault further strengthens the team and engenders loyalty and respect. Yes - you will be held accountable, Yes - you are expected to do things right/on time/etc. No - your Leader is not a push-over, and you cannot "get away" with poor performance or behaviour. But you leave the conversation wanting to improve/fix it - you want to live up to their higher expectations of you.

5. Formal vs Informal Authority

An Effective Leader knows how to get the job done - and how to use their formal authority as well as forms of informal authority (primarily influence). As we know, formal authority is bestowed with a title/job description, and not always respected fully if the person does not behave in accordance to the expectations of the role. You may "have to" do what is asked - that is more "Boss" talking. However, an Influencer gets things done by those around them by earned influence and respect - and people wanting to help. Exceedingly happy to help, even - because they know they can rely on the Effective Leader to help when they need it. A formal title may change - but influence tends not to fade that easily.

6. Loyalty

An Effective Leader both demonstrates and earns loyalty - through consistent interactions with their team members, standing up for them, and expecting the best from them. They are great people to work for (and with), but they are not just an easy-going smile-a-lot, they are firm when needed too. They will stand up for you with the higher-ups and with other departments, but they also expect you to live up to their expectations as well.

7. Consistency

An Effective Leader does not change their stripes according to the day - you can rely on them to be consistent in behaviour. Even when they have a bad day (and we all do), they do not completely change direction, and do not lash out at the team when frustrated. You know what to expect in your dealings with them - on good and bad days too.

8. Encouragement

Effective Leaders help to grow their team - collectively and individually. They support team members trying new things, advancing themselves by learning new skills - and providing opportunites to practice their new skills in the workplace. And it's OK to fail - if you are learning something new, you willl not get it right the first time. An Effective Leader understands this, and helps you to progress to the next level, without knocking you down a peg for failing while trying.

9. Not the Detail Expert

Effective Leaders are not the experts in what you do at the detail level. Maybe they used to know it once, but that is no longer their role - they know their value lies in orchestrating the team of experts to perform at their peak, and deliver the goods - on time, with high quality of results, etc. They become experts in working with people instead.

10. Caring

Finally, an Effective Leader cares. About the team, about the company,  about the customer, about the result - and about You. You can see this whenever you work with a team led by an Effective Leader, there is a whole different nurturing atmosphere. People want to be there, and are happy to do whatever it takes to succeed - because they are making a difference and know they are appreciated.


Summary

Nobody is perfect, even Effective Leaders. However they are consistent in what they do, and they do it well, which you can see by looking at the people that surround them. You might also say there are more attributes of Effective Leaders, and I would agree. If pressed, I could also boil it down to two main words - Caring and Consistency. But in truth, there is really so much more to it as you see above. 

Can we all learn to be Effective Leaders? Certainly! Few are born as Effective Leaders, those who have a high natural aptitude for it. Most Effective Leaders start out as good observers of people, and can learn the extra skills along the way. And having a good role model/mentor and exposure to Effective Leaders certainly helps too.

I have had the good fortune to work with (and for) an Effective Leader for a good portion of my career, and when I am uncertain of what to do in some leadership situations, I think back and ask myself "what would he do?". 

Am I an Effective Leader? Honestly, I can say not yet - though I am on the path and still striving to be closer - still wanting to live up to the expectations planted over two decades ago.

To my Mentor, Coach, Manager and Friend (you know who you are) - thanks for being a great example. Your infuence continues.
Originally posted on Gazza's Corner by Gary Nelson, PMP Wed, 24 March 2012. Reposted with permission. All rights reserved. Click here to see the original post.
Gary Nelson is the current Director of Communications for PMINZ, and is an independent IT consultant who has worked in the Telecom and Student Information System sectors since 1989.

Sunday, 17 June 2012

Everything I Need To Know About Risk Management I Learned From My Pocket Umbrella

By Gary Nelson, PMP

January 6, 1991: Standing on top of Ayers Rock (Uluru), Northern Territory, Australia. 
45C/113F and a cloudless, brilliant sunny sky. Humidity? near zero.


 




One of the driest, hottest places on earth.


So why am I carrying my pocket umbrella in my backpack?

And what does this have to do with Risk Management?


Interesting question!

To answer that we need to go back a few years earlier - and to a much wetter climate.

A Basic Lesson in Risk Management

Vancouver, BC, Canada - the "Wet Coast". 
Growing up in Vancouver you get used to rain. Lots of it - or at least long periods of drizzle especially in winter. (In Vancouver they can take a good NZ afternoon downpour and spread that out over three weeks of solid gray sky and liquid sunshine. One joke goes like this: "If you can see Mount Baker, it is going to rain. If you can't, it is already raining."  And another one - "They don't tan in Vancouver - they rust.")

Exaggerating a bit of course, but you get the idea. Wet. And not only that - you expect it, and plan for it.

Everyone has an umbrella (or three or four) and a rain jacket. One umbrella for the car, one for the office, one or two for home, and some spares for guests that might come by. Why? Well for the rain, of course - or at least the very high likelihood of rain, especially in the cooler months.

From the time I was in High School and taking the bus (or walking on a fine day), I carried a small umbrella in the bottom of my backpack.

It did not rain every day, of course - but I always carried the umbrella with me. It was perhaps my first practical exposure to Risk Management Planning. Knowing the region and the climate, there was a decent likelikood that on any given day I would need to keep my head - and especially my textbooks - dry from all that liquid sunshine. 

Remember the book "All I Really Need to Know I Learned in Kindergarten" by Robert Fulghum?  

My parallel to this might be called "Everything I Need To Know About Risk Management I Learned From My Pocket Umbrella."

Silliness, you say. How can you learn anything from an umbrella?

Essential Components of Risk

Risk - especially in the context of a project, is sometimes misunderstood, sometimes feared, and sometimes given no more than a sideways glance as everyone just wants to "get on with it" and start working on the project and produce the deliverables everyone is expecting. On the other end of the scale, Risk Management may become an all-consuming task that sucks the life out of your project as everyone is consumed by the worry of what might happen.

So what is a Risk - vs an Issue?

An Issue is a definite item that will pose some challenges or problems for your project. You are going to have to address it, or choose to ignore it - but it is not a "maybe" - the item is there, in your face- either right now, or at a known stage of your project.

Risk relates to an event that might happen at some time on your project. This Risk can be broken down into the following components:

- What may happen (the Risk Event)
- When is it likely to happen (timeframe: during a specific stage of the project, or at any time)
- What is the likelihood (probability) of it happening (High/Medium/Low)
- What is likely to be the outcome (the Impact) of the RIsk Event should it occur (High/Medium/Low)
- What factors might precipitate or contribute to the event

These are just the basic concepts - in your Risk Management Planning you will indeed include all of the above, as well as what you might be able to do about it - to try to prevent it happening (Risk Avoidance/Pre-Event Risk Mitigation), or if it does happen, what you can do to lessen any negative impacts (Post-Event Risk Mitigation/Risk Response).

The trick with Risk Management is doing a thorough enough job to make sure that you are aware of what might happen to impact your project - and to have plans in place to monitor the potential risk conditions and respond in the event it occurs. You don't want to take the "hope and pray" approach, hoping risk will pass you by - but you don't want all of your resources tied up in an exhaustive Risk Management approach that takes on a life of its own and detracts from your project. 

You need to take a practical approach to Risk Management. Look at what is "out there", and do a realistic assessment of what may happen, probabilities and impacts, and then devise an action plan to respond to any events, and look at what practical preventative measures you can afford to take, without going overboard.

When you have your list of Risk Items, you need to categorize them as outlined above, and map them out. You can do a simple 2x2-square grid (High-Low) or 3x3 (High/Medium/Low) if it is helpful to your project, but in my experience, simpler is better. For now let's discuss a simple 2x2 model.

In this model, we want to pay particular attention (and concentrate most of our efforts) on the High Impact/High Probability quadrant items. These could be show-stoppers. Proactive risk mitigation actions might also be advisable for several of these items.

High Impact/Low Probability items need to be monitored and prepared for - but you should not spent a huge amount of effort on prevention - but do have a good post-event mitigation plan.

Low Impact/High Probability items need to noted - but you should not spent a huge amount of effort on prevention or the mitigation plan.

Low Impact/Low Probability items can in many cases be simply noted and little time should be spent on them. Don't lose them though - it might be that their profile will change if conditions on the project change.

Pre-and-Post Event Mitigation

When you develop your Risk Management Plan, you will likely come up with a "what to do IF it happens" set of plans (Post-Event Mitigation) - write them down, and keep them in a drawer somewhere, just in case you might need them later. Update them as necessary.

However, the proactive (Pre-Event Mitigation) side of Risk Management includes taking preventative measures on an active or semi-active basis.

For example, if there is a risk that you might be attacked while staying in a war-torn foreign country, it might be wise to actively station armed security outside your complex. (The best Pre-Event Risk Mitigation strategy is simply not to go there in the first place, but if you are already there...)

But in our example (fortunately) all we have to worry about is rain. Specifially, preventing it from soaking your bag or briefcase.

Preventative Risk Mitigation

 If we took a fully active approach, you might walk around all the time with an umbrella open over your head. Aside from the lack of Vitamin D from sunlight, you would look pretty silly after a while and people will begin to talk about your odd behaviour.

So a semi-active approach might be a bit better. In this scenario, we would be prepared for rain- or at least rain of an average volume. So let's just take an umbrella with us - all the time. (If you only take an umbrella when you know it will very very likely rain - i.e. the weatherman warned you it is going to rain, that is just being prudent. No bonus points for you!)

Which umbrella to choose? (aka Effort)

Those big golf umbrellas provide great coverage, but they are bulky - and just like the guy walking with the open umbrella on a sunny day, walking around with one of those all the time will get people talking. Not ideal. Plus you are quite likely to poke people with it on the bus.

I prefer a more pragmatic semi-active approach - be prepared, but not necessarily for a monsoon. Prepare for a typical or middle of the range event - in this case, a typical Vancouver rain. So I packed a pocket umbrella in my bag. (Not the tiny ones, the ones about 33cm/1 foot long when closed). Suitable for most conditions, but small enough and light enough to carry everywhere, and not be too visible. People will commend you when you bring it out in the rain, but not look at you oddly on sunny days, because they can't see it.

And most of the time - as a Pre-Event Risk Mitigation Plan it was sufficient. Until last year, that is...

Change the Environment, change the Risk

As with everything in your project, things change over time. And sometimes, your Risk profile can change. You need to be aware of the changing conditions and re-assess your risks based on new data. You just might need to update your mitigation planning (post-event and pre-event).

Sometimes what worked before simply won't be enough!

August 30, 2011, Annapolis, MD, USA. 7:45am - I am due to start the training class at 8:00am. I am waiting in my car, outside in the parking lot, along with dozens of other people in their cars. Waiting - because it is not raining. It is drowning outside. Heavy rain bombs hitting the window, and over 1.5cm/half an inch of water pooled everywhere in the flooded parking lot, deeper in many places.

I have my pocket umbrella. Wheelie computer bag is in the trunk. Waiting.

7:59am. Still pounding down outside. I am going to be late for class!

Risk assessment: I have my umbrella. If I grab the bag and pull it, running fast I might be ok. 30 seconds to the front door, give or take. How bad could it be?

8:00 Inside the foyer, absolutely soaked except my head.

8:01 In the classroom, opening my computer bag. Everything is wet.

8:02 My laptop will not turn on.

8:02:01 Risk Event: Computer will not turn on! !@#&*!&#*(&!@#(*&!@*(#& 
Oh dear... I definitely did not make the right call on this one!

8:04 Risk mitigation (post-event): USB thumb drive with the training materials I made as a backup copy seems to be dry. Let's give it a shot, or I will not be earning money today!

8:10 Class starts, up and running with a borrowed laptop and my USB stick - while I completely empty my bag and disassemble the components of my laptop to try to dry them out with the hot air from the LCD projector.

11:55am Wrapping up for lunch. Things seem dry- I reassemble the laptop and power it up. Crossing fingers! 

11:59 Laptop boots up normally. Lucky. Very lucky I don't have to go buy a new laptop.

Lesson #1: Sometimes having a backup to your backup plan is a good thing to have!

Lesson #2: Don't let the heat of the moment let you make bad judgement calls when you have a Risk mitigation plan in place that is likely inadequate. As it turns out, at 8:05am the rain stopped. Haste makes waste, all those sayings...very true. Patience is a virtue...

Lesson #3: Pre-Event Risk Mitigation Plan adjustment: Buy a plastic bag to line the inside of the laptop bag in case of heavy rain.

Back to the Australian Desert

Down from Ayers Rock (Uluru), back in the LandCruiser and on the way back up to Alice Springs.

Still very hot, and dry. No cloud at all.

Feeling a little bit foolish about dragging that little pocket umbrella into the middle of the arid Australian desert. But then - I could not exactly leave it anywhere either - so here it is with me, in the bottom of my bag.

January 10, 1991: Took the train from Alice springs towards Canberra, stopped in Broken Hill NSW. 44C/111F. Dry. Hot. (Note: Home of Silverton Pub, the pub in the original Mad Max movie. If you go there, take "the challenge" and you will get a free beer. Really! I did.

January 11, 1991: Broken Hill, New South Wales, Australia. One of the few rainstorms per year hits the town, dumping several inches of rain in the afternoon.

** Guess who has an umbrella? ** :-)

Ironically, as there is so little rain, there are no storm drains in Broken Hill. They just have the street curbs, and some walkways the put out from the curb to the middle of the street so people can walk over the water until it flows back out into the desert. However as the rain was quite heavy, the little bridges only went halfway through the flowing water. 

So - umbrella held high and barefoot I went, walking down the street holding my shoes in my hand.

You can't plan for everything!

Summary

Risk Management is a matter of awareness and balance - and updating your Risk Profiles as time goes by - some risks disappear, new ones may be added, and some may change.

I have continued the habit of carrying a pocket umbrella in my bag - or, I did until my teenage son needed it more than me this year - now that it is his turn for taking the bus to High School. 

Time to buy another umbrella!

Good luck with your projects, and try to stay dry!
Originally posted on Gazza's Corner by Gary Nelson, PMP Sunday, 17 June 2012. Reposted with permission. All rights reserved. Click here to see the original post.
Gary Nelson is the current Director of Communications for PMINZ,

Wednesday, 13 June 2012

Risk Mitigation Through Contracts


By Lars Theil-Lardon (MBA)

In my years as project manager, one thing my clients have valued most is the security of their funds or at least the knowledge of the last final figure.

At university they teach us that through planning 70% of the total expenditure of a project can be predetermined and secured. Life teaches us that clients usually do not want to go the extra mile in the planning process either due to time constrains or overconfidence.

Under these circumstances risk management helps to determine potential risks, which deviate from the desired project goal, and eliminate, isolate or minimize them. In the current market, dealing with risks and their potential influences can’t make up for inefficient planning.

In my personal opinion risks are best managed, some even avoided, through a solid written contract. However, this can only be achieved if the planning phase has been correctly and robustly executed. I have been in the construction sector for the last 6 years and I can recall that the most project issues came through wrong client expectations and sloppy written contracts. Many of my fellow engineers and project managers dealing with Local Government Agencies are using NZS3910 as their contract construct, but forgetting to personalise the contract with the particular project they dealing with. Sometimes recommendations made by the Engineers or Project Managers are rejected by the Clients as they are different to their standard contract conditions.

Now most of the readers will ask themselves, ‘why is this guy talking about contracts and risks avoidance in the same moment?’ The answer is easy. With a good and solid contract the client can avoid additional risks and with a sloppy written contract they will create additional risks. For example, if you predetermine your design in detail, you can anchor all the items in the contract document. As a client you will rely on the knowledge and experience of your consultants to get an understanding of the construction period. Even if the suggested timeframe is longer than your anticipated plans allowed for, try not to restrict the time by specifying the contract period shorter than it actually takes. Most contractors will still sign contracts with overly short contract periods, but they will work on potential extension of time from the early days. One piece of major advice is that a client shouldn’t change any plans or objectives after the contract is signed. A move like this will expose the client to a risk that the price for the variation is no longer the lowest market price and an extension to the contract period will be added.

Another catastrophic risk which can be eliminated with a contract is the reserves for any damages. Every construction contract has retentions placed on the suppliers. The maximum should be within 5% to 10% of the construction sum. This money can be used as funding source for any claimed damages after the project is practically complete and payment has occurred. I remember one of my contracts, where a maximum retention sum of $100K (equal to 1%) was specified. Three payments before the contract finished, potential applied damages were identified as being in the order of $300K to $500K. As you can imagine, the client got very nervous due to the fact that he was exposed to the risk of having to claim the damages from the contractor as invoices. This situation is not a single case - rather a regular thing.

A last but major risk is ambiguity of the contract. Some contracts are rushed and therefore mistakes, minor as well as major ones, slip into the contract. These ambiguities are risks which can cause financial implications to the client and frustrations on all sides of the contract. As a guideline to good management practice, all contract documents should be proof read at least 3 times preferably by 3 different people. At best one of these people should have had no involvement in the design process at all. With the increase in complexity and value the number should be increased too.

In my current project a lot of frustration between the contractor, client and consultant could have been avoided, if the document would have been closer examined before it was released for tender.

But every contract has its limitations and some unforeseen issues, such as unexpected ground conditions, can’t be eliminated. For these events and many others like delivery issues, theft, vandalism and so on, a well prepared risk management plan will govern the way through the risk world.

Lars Thiel-Lardon (MBA)

Professional Management Services 2009 Ltd

Lars studied at the University of Rostock and graduated in 2004 with a MBA. In 2005 he immigrated to New Zealand and works since in the construction sector.

Lars is specialised in civil and building construction projects and managed a number of construction projects in New Zealand. For the last 15 months he is involved with the Morrinsville Wastewater Plant Upgrade on behalf of Matamata Piako District Council.

Lars is also the Bay of Plenty Sub-Branch Coordinator.

Sunday, 3 June 2012

Pragmatic Risk Management for Projects

By Grant Goodman

Life is risky and since time immemorial human beings have found a myriad of ways to maim, injure and kill themselves and others. However, the vast majority of us are still alive and well, through risk management practices that we are often unaware of. Driving on the roads is risky but we mitigate the risk by having speed limits and road rules.

Before I got into project management I spent three years as a risk manager in a healthcare setting. Healthcare settings are risky but a good risk practitioner looks for a way to minimise and mitigate risk. It is only in rare circumstances that we can actually eliminate risk. I suppose one could stop treating patients and that would stop the risk of treatment side effects but immediately another and larger risk will present itself – death from the risk of non treatment. The rule of thumb that the organisation I worked for was to identify all the risks and pro-actively manage the top ten on an ongoing basis. This allowed real progress to be made on reducing the risk profile without seeing monsters around every corner.

As we all know one of the cornerstones of effective project management is to keep an active risk register along with an issues register. For those of you who are unaware of the distinction a risk may happen, but an issue has already happened and needs action. The challenge is to manage risk effectively by following a small number of principles:

Risk Identification

At the initiation stage of your project identify all the potential risks with the project board, team and key stakeholders. Be realistic and resist the temptation to go overboard. Reputational risk from a botched project is real, the risk that your whole business will be destroyed by a catastrophic event is not very likely (but does happen as our colleagues in Christchurch can testify).

Risk Review

Review the risk register on a regular basis. Has the risk profile changed? Have new risks appeared? Have old risks been further mitigated? Have some of the risks become issues? All these questions should be asked but this should not take hours to do. Check out the risk controls to ensure that these are still working, if not, rework them.

Risk Reporting

I like to see full risk reporting on a monthly basis with a risk reporting section in all weekly project exception reports. The monthly report lets me track risks across my portfolio and associated programmes and forms the basis of the monthly risk reporting through to the project, programme and executive boards. Of more interest to me are the weekly exception reports. All I want to see in the risk section is new risks or an escalation/or dramatic de-escalation of existing risks. Any risk that is realised as a new issue is also reported. That way I can keep a regular view on the risk profile across the organisation without wasting a day reading full risk reports.

In my experience when risk registers get over-bloated then senior project and business stakeholders lose a sense of the real risk profile, this in itself raises another risk that real risks get obscured by the noise of smaller risks. It is unusual that any project manager is actively managing more than five active risks in any week so I only want to know what is happening to the top five on a weekly basis. Of course I do expect my project managers to escalate any significant risk that is worrying them when it occurs. While I see all the risk reports on a monthly basis only the top ten make it to the executive management for review. Once again this is a pragmatic approach. Senior executives are very busy and your report is usually one of many items on the agenda, so focus what you report to allow them to see the real view.

End of Project Risk and Issue Review

At the project close out a final review of the risk and issue registers needs to be performed. Any risk that has not turned into an issue can be closed. Issues need to be reviewed to see if they are still active or not. If they are active transfer them to someone in the business, if not close them out. This is an important exercise and should feed into the lessons learned section of the project close out. It also provides a reality check as to which risks can be dropped off the next project and which ones can really bite you in the rear.

Effective risk management will help you project manage without tying you up in minutiae.

Grant Goodman

Grant is an experienced programme director who has worked on a large number of programmes and projects nationally and internationally. He has recently returned from a three year consulting stint in the United Kingdom. Grant is also the Waikato Sub-Branch Coordinator.