Showing posts with label experience. Show all posts
Showing posts with label experience. Show all posts
March 15, 2017
Deficiencies: The Achilles’ Heel of Construction Projects
This week, please welcome Paul Behner, an accomplished project manager in the construction industry, as my guest writer.
Deficiencies are a standard line item on most, if not all, construction projects.
Construction project deficiency is defined as a characteristic or condition that fails to meet a standard, or is not in compliance with a requirement or specification, and is sometimes referred to as defective work.
Frequently, the term deficiency is confused or misinterpreted as incomplete work and, more times than not, it's used under lien act legislation to delay substantial completion milestones which trigger holdback releases. In reality, a deficiency is not the same as incomplete work. From a legal perspective, only incomplete work affecting the beneficial use of the facility or asset intended from the project performance determines substantial completion.
Without evaluating the global issues surrounding the interpretation of substantial completion, it is fair to say that both deficiencies and incomplete work are routinely misunderstood.
There is inherent ongoing risk to the general contractor who is responsible for contract performance of all trade subcontractors and suppliers. This includes all work until project close-out, with the exception of warranty work. The ongoing issue of ineffective deficiency management cannot be improved without first breaking down the problem. Until then never-ending deficiencies will inevitably remain the Achilles' heel of successful project delivery and, in turn, erode profitability and customer satisfaction.
Deficiencies are commonly cited as the barrier to successful project completion. To get to the core issue, it is more effective to consider a deeper understanding of project management which goes beyond the deficiency issue. The General Contracting business is as much about time sensitive delivery of a specified product or facility, as it is about operating a business. The business strategy ought to be focused on exceptional project delivery, therefore requiring exceptional project management proficiency.
Without question, deficiencies are an anticipated task and risk of every project and should be managed holistically within the project management plan. Whether deficiencies are the catch-all reference for incomplete or defective work being a chronic issue plaguing success, a project management plan that includes the five phases will greatly improve project close-out and overall performance. There is only one solution to effectively manage construction deficiencies and that is by way of a project management plan with improved guidelines on project close-out.
Paul Behner has spent 30 years in the construction sector. He provides strategic consulting on the full-cycle management of a project from planning to execution to close out. Visit his website at greentreepm.ca.
September 23, 2016
Sully, the Risk Manager
I went to see Sully last week, a movie based on a true story. Sully - Captain Chesley "Sully" Sullenberger - performed a great act of risk management.
An airplane pilot, Sully made a quick decision when his plane hit a flock of birds, lost the use of both engines, and was in danger of crashing. He was flying above New York City when this happened, with approximately 150 passengers on board.
Sully decided to land on the Hudson River instead of trying to make it to the nearest air field.
Afterward, the landing was investigated by the US Transportation Security Administration. During the investigation, flight simulations seemed to prove that Sully could have made an airfield landing, instead of on the river as he did.
It hits Sully that there was one element missing in the investigation: the inclusion of the human factor. After all, making this type of landing was something he, a pilot with 42 years of experience, had not done before. When this factor was taken into account, he was proven right - landing on the Hudson River was the best option.
While making the decision to land on the river, Sully encountered a risk and dealt with it. According to the Project Management Institute (PMI), a risk is an uncertain event or condition that, if it occurred, would have a positive or negative effect on the project's objectives. Decidedly, flying into a flock of birds was a negative risk event, as was crashing!
Sully and his co-pilot followed the steps they were trained to do (the risk response plan) when the bird collision occurred: they notified their air traffic controller. But the solutions offered from ground control weren't viable in the situation - they didn't have time to get to the nearest landing field. So Sully made the decision to land on the Hudson River. This was their work-around, their solution to an unanticipated problem.
At the time, training for duel engine failure wasn’t something pilots usually did. (npr.org/templates/story/story.php?storyId=99480314)
What was going through Sully’s mind as he was making the necessarily quick decision? I think it would have to do with the probabilities of the different scenarios being successful, and the impact if they weren't. So he did what had the highest probability of success and the lowest impact of failure (loss of life) - he performed an on-the-spot risk analysis.
The story ended well (as my favourite movies do!) and Sully was regarded as a hero. His knowledge and quick thinking saved the lives of all who were on Flight 1549 from LaGuardia Airport that day.
An airplane pilot, Sully made a quick decision when his plane hit a flock of birds, lost the use of both engines, and was in danger of crashing. He was flying above New York City when this happened, with approximately 150 passengers on board.
Sully decided to land on the Hudson River instead of trying to make it to the nearest air field.
Afterward, the landing was investigated by the US Transportation Security Administration. During the investigation, flight simulations seemed to prove that Sully could have made an airfield landing, instead of on the river as he did.
It hits Sully that there was one element missing in the investigation: the inclusion of the human factor. After all, making this type of landing was something he, a pilot with 42 years of experience, had not done before. When this factor was taken into account, he was proven right - landing on the Hudson River was the best option.
While making the decision to land on the river, Sully encountered a risk and dealt with it. According to the Project Management Institute (PMI), a risk is an uncertain event or condition that, if it occurred, would have a positive or negative effect on the project's objectives. Decidedly, flying into a flock of birds was a negative risk event, as was crashing!
Sully and his co-pilot followed the steps they were trained to do (the risk response plan) when the bird collision occurred: they notified their air traffic controller. But the solutions offered from ground control weren't viable in the situation - they didn't have time to get to the nearest landing field. So Sully made the decision to land on the Hudson River. This was their work-around, their solution to an unanticipated problem.
At the time, training for duel engine failure wasn’t something pilots usually did. (npr.org/templates/story/story.php?storyId=99480314)
What was going through Sully’s mind as he was making the necessarily quick decision? I think it would have to do with the probabilities of the different scenarios being successful, and the impact if they weren't. So he did what had the highest probability of success and the lowest impact of failure (loss of life) - he performed an on-the-spot risk analysis.
The story ended well (as my favourite movies do!) and Sully was regarded as a hero. His knowledge and quick thinking saved the lives of all who were on Flight 1549 from LaGuardia Airport that day.
December 17, 2015
Decisions
At my home, we often share dreams we had the night before. This morning my son Zachary told me the he had dreamed about Poppy (my father) who passed away two years ago. In the dream, Dad told Zachary that I should say "No" to a decision.
This got me thinking about how many decisions I make in a day - which turns out be be a lot. So, I wondered which decision that might apply to.
Related to decisions, I saw this post on LinkedIn today about decisions, and you could say Expert Judgment. In the Guide to the Project Management Body of Knowledge (PMBOK), Expert Judgment is often a tool used for making decisions.
How do we know who is an expert? It's generally someone who has done the work before. And how do you become an expert...?
This got me thinking about how many decisions I make in a day - which turns out be be a lot. So, I wondered which decision that might apply to.
Related to decisions, I saw this post on LinkedIn today about decisions, and you could say Expert Judgment. In the Guide to the Project Management Body of Knowledge (PMBOK), Expert Judgment is often a tool used for making decisions.
How do we know who is an expert? It's generally someone who has done the work before. And how do you become an expert...?
Subscribe to:
Posts (Atom)


