Powered by Max Banner Ads 

Tag Archive: BP


A blog post we created ended up as an article in PMSA’s  (Project Management South Africa) monthly magazine.  The posting was about BP, and their preparation for, and reaction to, the environmental project risk as a result of the so-called “Deepwater Horizon” well incident, which now seems like ancient history.  In fact, already we encounter people who forget that this happened.
Anyway, after our article was published in PMSA’s The Project Manager (an excellent journal, by the way), there was a rebuttal of sorts by a gentleman who is very experienced in the oil industry.  While we appreciated his technical expertise we felt that we deserved a chance to reply, and PMSA accommodated that recently with the following response by EarthPM:
Rejoinder from Rich Maltzman and Dave Shirley, co-authors of the award-winning book Green Project Management, to the article by Ronald Smith entitled “BP is not the enemy”, on the BP oil spill (March 2011 edition of The Project Manager)We thank Mr Smith for the explanation and expertise he provided on the process of drilling for oil. His description made the process much more accessible than most and, importantly, more relevant to us as project managers. We appreciate his acknowledgement that the consideration of sustainability early on in the project might have had an effect, although we understand his scepticism that it might not have made any notable difference.

For our part, we are increasingly convinced that sustainability thinking (and the resulting actions) could have had an effect on whether an incident happened the way it did and how it was responded to.

Since the original article was published, more facts on the story have come to light. For example, the risk register that the local BP team used was recently released by a United States government agency as part of its investigation; and it indicates that the only risk categories populated were in cost, schedule and production (see www.boemre.gov/pdfs/maps/AppendixJ_RiskRegister.pdf). You can see in the risk register that the suggested risk categories and those used by the team on the Macondo well.

Although BP, as a corporation, had admirably included environmental and safety risks in the overarching template, it incentivised all its teams with an “every dollar counts” programme, which did in fact yield significant savings for the company (see:www.bp.com/genericarticle.do?categoryId=2012968&contentId=7055139).

We would assert, however, that this incentive – and the immediate result it provided in terms of savings – drove behaviours, as illustrated by the fact that there were zero environmental and safety risks identified. Again, we know that we were not there to observe this happening so, admittedly, some of this is conjecture on our part (as we reminded readers in our original article); and no one can predict what would have happened if BP had identified these risks – but we do know as a matter of fact that unidentified risks will not have risk responses.

As far as the skimmer boats, with a $20-30 billion downside, and a need for “positive” public relations, why not have a fleet of these boats ready to deploy at key locations? It seems to us that it would have at least given the appearance that BP had been looking to prevent the spread of the oil, and at best would actually have recovered oil and helped prevent the spread of the oil. In our opinion, this is a relatively inexpensive purchase (or lease!), considering the downside risk.

Mr Smith discusses the way in which chief executive officer Tony Hayward and BP were treated by US President Barack Obama and Congress. On this note, we cannot defend politicians nor the political process and the actions of the committee that questioned Hayward.

We can acknowledge, however, that perception becomes reality; and the perception or impression that Hayward gave to many people – including some of these politicians – was that BP would sort of eventually get around to cleaning this up.

We think that part of corporate social responsibility is owning the problem and making it clear to all stakeholders that you believe the problem to be your own.

Now, let us talk to the point made about “low risk”. Let us be clear here on our terminology. Risk (in this case threat) is composed of two elements: the probability that something bad may happen; and the impact that this something may have. Multiplying the probability and impact yields the risk factor – the attribute used to judge how a risk affects a project objective.

We agree with Mr Smith that the risk event probability is low. But two similar events having occurred in 40 years is hard evidence that it is certainly not zero.

Furthermore, we think most people would agree the impact was high. Even BP would have to agree the $30bn of tangible fines and expenses and unknown intangible damage to its reputation is ‘high impact’.

When we multiply the probability (low, but not zero) and the impact (huge!), we still end up with a risk factor number that is fairly large. So – “low risk”? We disagree.

As to the analogy with plane crashes, we do not suggest clean-up crews at points all over the globe.

It should be noted that there are, in fact, emergency teams and equipment at every airport.

Furthermore, there are indeed agencies such as the Red Cross, the National Guard, the police and others who exist for the very reasons we discuss.

The analogy is not very appropriate nor relevant because the oil rigs are fixed in one place and not flying around. So it is therefore much less effort to plan and execute risk mitigations nearby at their source.

Mr Smith completes his story with this quote: “As Pogo the Possum said: ‘We have met the enemy, and he is us’.”

Well, we could not agree more, and we can do something about that.

Ensuring we include sustainability thinking in our projects, for example, including “environmental risks” in our risk analyses, goes a long way to helping us “go a long way” (i.e. being sustainable)

Here’s a link to the “rejoinder”:
Blame game
Tuesday, 17 January 2012

© 2012 – The Project Manager

VN:F [1.9.13_1145]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.13_1145]
Rating: 0 (from 0 votes)

…they manage (or better yet, lead) people!

And so – one of the “bottom lines” of our Quadruple Bottom Line (QBL) is people.  The full set, of course, is People, Planet, Profits, and Projects.

We focus a lot on the Planet piece – this is natural for a company named EarthPM – but we know that the People part of sustainability is an important one.

We found a good resource for PMs interested in this aspect.  It’s from Michigan State University, and it’s called the Sustainable Workforce site.  On it, we found a list of best practices for an organization that wants to support a sustainable workforce.  The list seems to also feather into the HR and Communications areas of the PMBOK(R) Guide as well as the Code of Ethics and Professional Conduct.  We’ve highlighted some of the areas where we assert project managers, as ‘project people managers’ can pay attention to better the workforce from a sustainability perspective.

  • workplace flexibility to support long term education & career development, individual and organizational learning, & facilitation of work-family well-being;
  • the attraction, retention and development of a motivated workforce that experiences a positive organizational environment in which they work;
  • organizational and personal resilience, engagement, and the capacity to thrive;
  • occupational wellness practices that create healthy workforces that don’t burn out or unnecessarily tap into health care or dysfunctional behaviors due to excessive stress at work;
  • positive and transformative employment relationships;
  • innovation to help individuals positively adapt to new social & economic change such as new technology, globalization, 24-7 work & blurring work-life relationships & growing workforce diversity and multiculturalism;
  • worker control over the timing, location and about of work in ways that they still can be employed yet ensure care for themselves and their families effectively;
  • organizational reinvention, continuous improvement of employment systems to foster mutually beneficial outcomes for employees, employers and communities;
  • positive social change and innovation in employing organizations while balancing stakeholder interests and a “triple bottom line” (profit, worker well-being, family);
  • inclusive leadership & organizational change for supportive work force renewal.

Here are some other places to look for this aspect of project management’s contribution to the sustainable workforce:

BP’s statements about a sustainable workforce

Walmart’s practices for a sustainable workforce

Cummins objectives for its sustainable workforce

What does your organization do in this area?  How does project management play in this area?  As a project manager, how do you add value to team members’ long-term sustainability?

What do you think of this aspect of project management sustainability?  We’re interested in your thoughts.

 

VN:F [1.9.13_1145]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.13_1145]
Rating: 0 (from 0 votes)

There are lots of things we could talk about one year later, but for this post we’d like to focus on the suit filed today by BP against Transocean, the rig’s owners, and Cameron International, the supplier of the  blow-out preventer, for $40 billion.  From AP (article), guardian.co.uk,  ”The Deepwater Horizon BOP was unreasonably dangerous, and has caused and continues to cause harm, loss, injuries, and damages to BP (and others) stemming from the blowout of Macondo well, the resulting explosion and fire onboard the Deepwater Horizon, the efforts to regain control of the Macondo well, and the oil spill that ensued before control of the Macondo well could be regained,” BP said in the lawsuit against Cameron.  BP is also suing Halliburton, the company responsible for pouring the cement.

The reason we are focusing on this aspect is because, when we look at the benefits of Green Project Management, we see that green thinking should be a part of all the project’s processes, including the procurement process (just one of the processes outlined in our book).  In this case, if the questions were not asked, we would have asked about the greenality of BP’s “vendors”.  There would have been questions like:  What did Transocean consider for their environmental impact?  What safe guards were in place in case of an issue like a spill or blowout preventer failure?  Were those scenarios even considered?  Driving back into their processes, we could have asked to see the invitation to bid, to examine whether Transocean considered the greenality of their vendors.  This is just a sampling of questions to ask.  On a project this large like this, with the potential for devastation it has, the questioning would have been extensive and rigorous.

We advocate a “greenality clauses”.  We believe that if we choose a company, considering their green efforts as part of the decision making process, that they should be held accountable for those green efforts, as well as capturing that criteria in the contract.   Again, we like to give the obligatory caveat that we were not in the room when the decision was made by BP to go ahead and lease the rig from Transocean, so we don’t know exactly what went on.  But from our point of view, the project did not consider all of the green aspects it should have and that green project management would have helped in that process.

VN:F [1.9.13_1145]
Rating: 10.0/10 (2 votes cast)
VN:F [1.9.13_1145]
Rating: 0 (from 0 votes)

sharkWhen you think is it safe to go back in the water, the sharks show up.  The cost of greenality keeps going up for the principles involved in the Gulf Oil Spill.  The Department of Justice announced today that it would join in the civil suit being filed against such companies as BP, Anadarko, and Transocean.  Adding the cost of the spill paid out so far, the losses of life, and the $20 billion fund, what will the final price tag be?  We’re not saying that the tragedy could have been avoided, or the damage could have been minimized if the companies involved had paid more attention to the project’s environmental risks  involved with the Deep Water Horizon.  But then again, why take the risks without fully investigating ALL project risks, especially with the potential environmental damage that could occur.  Again, we were not in the room when these decisions were made (perhaps we should have been and then we’d know), but it makes sense to us that if all of the risks were not considered, it certainly would have been cheaper, by orders of magnitude, to cover all the bases.   That’s what we think.  For more information on managing projects with greenality, see our book.

VN:F [1.9.13_1145]
Rating: 10.0/10 (1 vote cast)
VN:F [1.9.13_1145]
Rating: +2 (from 2 votes)

DeepwaterA joint post from EarthPM and TenStep:

There are many examples of projects undertaken to produce some deliverable with environmental implications. In fact, one may assert that in fact, any project, since it uses resources, has environmental implications.  This varies tremendously, based on scale and the direct impact on the environment.  One project that clearly has environmental implications is the Deepwater Horizon drilling project and what is often called “the Gulf of Mexico oil spill disaster”.

Important note: We do not purport to say that any specific single action or philosophy that we enumerate below would have prevented the Deepwater Horizon disaster or led to its instant cleanup.  What we do assert, however, is that taken collectively and holistically, an intense focus on green thinking would have had a tremendously positive impact on the disaster.

Many companies are incorporating environmental considerations into their thinking about the deliverables of their projects, and some are even integrating this thinking into the operation of that deliverable. However, are they truly following green project management processes to assist them in their decision making process throughout the project and beyond? We assert that Green Project Management can be applied to all projects. Even those that may not appear to be creating a deliverable with an environmental impact still have environmental aspects that can affect their decision making (for example, even if one is developing a new software release there are decisions to be made that affect the environment – decisions such as meeting policies, method of duplicating the software, energy considerations for the servers involved, and so on).

Both TenStep and EarthPM believe that the environment should be considered in any project – and therefore in an organization\’s project management processes. We also think that doing this is not only the right thing to do but that it will benefit the organization.  Both organizations have published various communications which provide thought leadership on this subject (refer to www.green-pm.com and www.earthpm.com.

We’ve decided to apply examples from Green Project Management to the challenges faced (mainly by BP) in the Gulf Coast oil spill. The main thrust of Green Project Management is not that every decision will be made differently or “in favor of” the environment, but instead that each project needs to consider the environment in its decision making process.  This of course includes the conservation of the project’s resources, which should already be part of the project manager’s mission.

What we are suggesting here are some ways in which Green Project Management may have provided BP with key insights that,  taken holistically,  may have done some of the following (in the abstract, anyway):

  • Prevented the disaster or at least limited the extent of the damage
  • Made it easier to repair once it happened
  • Allowed BP and the other responsible parties to deal more skillfully with key stakeholders.

Let’s consider the example of Green Project Management in completing a project to define, develop, and implement the oil rig. Note that some of the examples below may not directly apply to the Deepwater Horizon project, but are provided as examples to demonstrate the principles of Green Project Management.

Project Charter

Have you ever seen a Project Charter template that has a section on environmental concerns?  It’s rare now, but we predict it will become much more prevalent.  Perhaps if the Charter for the Deepwater Horizon project included a detailed section on environmental impact, it would have raised the awareness of the project team and associated stakeholders with regards to improved means to prevent, mitigate (with activities such as relief wells), and respond effectively to spills.  A charter written with an environmental view also may have allowed BP to focus more effectively on the clean up process, because decisions like the purchase of Ocean Therapy boats (see this posting) would be indicated at a Charter level.

BP may also have identified a need to further evaluate its vendors/partners experience in prior, similar projects. Lastly, it may have resulted in a need to further invest in considering alternate approaches with various stakeholder groups, to assure the necessary buy-in prior to undertaking the project.

Project Scope Management and Project Integration Management

If the oil rig required additional drills, or a change in the materials used to create the drill or the oil platform, then scope change management process should have been invoked. Note that the latter could have been a requirements change, part of project scope management. When invoking scope change management, the environmental impact could have been considered, in addition to the impact on all other project management processes (schedule, cost, quality, risk, procurement, etc.) as evaluated through integrated change control. Perhaps a change in materials requirements would result in procuring materials from a different vendor. We discuss this further in the section on procurement management.

Project Management Plan – An Environmental Management Plan component

Existing BP environmental policies – which we’re sure that BP has in great number, considering their size and experience – need to have been used as an input to the project\’s Environmental Management Plan, identifying the environmental policies applicable to the project and the sustainability requirements for the project.

Requirements Management

When gathering requirements for the oil rig, BP could have reviewed its defined project Environmental Plan (linked to the company’s parent Environment Management Plan) and confirmed that the requirements for the oil rig would adhere to the plan. Making it clear to the project team that this linkage exists is a way to reinforce what should be elemental to the team’s behavior but sometimes can slip behind other priorities if not kept in the forefront.

Much has been said about the regulating agency, the MMS and their oversight (or lack thereof) of oil companies.  Ostensibly, the MMS should have been putting proper requirements on the companies doing the drilling.  As is the case with good project management practices, however, the vendor themselves has to ask the question: ‘who are the stakeholders, and what are their requirements?’ Perhaps with this mindset and a well-conceived (excuse the pun) and ethically-responsible environmental management policy – not just at a corporate level, but at a project level – an increased focus on both preventing the spill from happening and being able to effectively clean up after, would have resulted in a more thorough collection and communication of these environmental requirements before beginning to drill.

Cost Management

When estimating project costs, did BP consider costs for implementing any risk response strategies?

As mentioned in the Charter section, one could look at the Kevin Costner-funded Ocean Therapy centrifuge boats as an example.  For a relatively small investment, BP would be buying not only an easy way to clean up after a possible spill, but would gain valuable positive PR by aligning with the high-profile actor and his efforts to protect the Gulf. Perhaps it is too optimistic to think that the oil companies would have identified oil cleanup technology as a part of risk-response, but it certainly is within the realm of reason that cleanup technology and costs would be included in risk contingency plans (the plans that are put into effect if the original risk plan fails).

In fact, a recent news story shows that – although late – the oil industry has pooled their resources and is collaborating on oil spill response.  See this Reuters news story.

Identifying the costs related to the project\’s environmental aspects allows the project manager to discuss the costs with the Sponsor and determine whether the cost is more than offset by the project results. The financial costs of the realized threat are so high in this case – in the tens of billions of dollars and in fact the continued life of the company itself – that a different type of thinking has to be applied.  As is obvious now, BP could have invested more upfront to further mitigate or avoid the risk of spilling oil into the ocean. Even with Green Project Management, if BP\’s decision was not to invest more in a risk response strategy, then perhaps they should have estimated the contingent costs required for a clean-up activity as they are currently undertaking. See the risk management section.

Communication Management – Identify Stakeholders

How thorough was the stakeholder plan and ultimately the Communication Plan prepared by BP for this project? This project appears to have many key stakeholder groups, both internal and external. Was every major stakeholder group – internal BP, NGOs, government, industries/associations (e.g., fishing along the Gulf Coast), etc – identified and considered? Were they all included in the communications as BP developed and implemented the oil rig?

What type of communications plan would allow BP Chairman Carl-Henric Svanberg to say “we care about the small people.\”?  We assert that with properly indentified stakeholders and a thoughtful stakeholder management plan, this likely would not have happened.

Risk Management – Probability and Impact Assessment

Really, this entire incident comes down to the way BP and others managed project risk.  The context is greater than risk management, as you can tell by the number of other headers in this document.  But it really comes down to project risk management. With “greenthink”, risks may be evaluated differently.

If we consider environmental factors that had never been applied, then BP may have identified the risk of the blowout as an extremely low probability of occurrence (based on prior experience, faith in the blowout preventer, competitors\’ experience, etc) but a very high impact when considering the environmental impact.  In fact, a very similar accident occurred in 1979 the Ixtoc.  In that case, the blowout preventer also failed.  So there was a precedent for this type of failure.  It could not be considered a “failsafe” solution.  The assessment could have also included the environmental impact of a blowout that occurred in Santa Barbara, California, in 1969.  Was their assessment of the impact high enough?

With such a low probability, you would have to have a huge impact for the product of probability and impact to give a risk score worth pursuing.  We assert that the probability was considered to be zero and that the impact was tremendously undervalued.  Without considering the environment aspect in project management process of risk management, the product was low enough that the risk mitigation and response was inadequate. As we noted above, Green Project Management may not result in a different decision. However, we are discussing this event because it truly depicts the importance of considering the environment and making sure that all project-related risks are properly identified, quantified, and addressed with the Sponsor and key stakeholders.

Procurement Management

When planning and executing procurement activities for this project, did BP:

  • Validate that their vendors/partners (such as Halliburton) met their environmental requirements?
  • Understand how their vendors/partners would align to BP\’s environmental policies and project approach?
  • Request feedback from vendors/partners on how they would align with environmental policies?
  • Audit that the vendors/partners were actually following the environmental policies?
  • Audit that the deliverables met the defined environmental criteria?

Summary

These examples have been provided to demonstrate how Green Project Management could assist in incorporating environmental thinking in any project. These scratch the surface in factoring the environment into project management processes. Perhaps BP accomplished these and more. Then again, perhaps a more structured approach to including the environment in all project management processes would have uncovered some of the issues and led to some very different decisions during the project, prior to deciding to drill more than five thousand feet deep in the Gulf of Mexico.

We assert that the point of Green Project Management is to view projects through an “environmental lens”. Perhaps, if that happened, some decisions would be made differently, with very different results.

About the Authors

TenStep, Inc, focuses on methodology development, training, and consulting, through its worldwide network of offices. Its focus on green project management (www.green-pm.com) was pioneered by Tom Mochal and Andrea Krasnoff.

Tom Mochal, PMP is President of TenStep, Inc., (www.TenStep.com). Mochal is an expert instructor and consultant on project management, project management offices, development lifecycle, portfolio management, application support, people management and other related areas. He was awarded 2005 Distinguished Contribution Award from the Project Management Institute (PMI).

Andrea Krasnoff, PMP is Director of TenStep Consulting Services. Andrea has more than 20 years experience in project management, program management, portfolio management, and PMOs. She is the Director of TenStep Consulting Services and is a key contributor to the TenStep Green-PM model.

EarthPM is dedicated to the “intersection of green and project management and is a collaboration between Rich Maltzman and Dave Shirley, co-authors of Green Project Management, CRC Press.  EarthPM provides the critical link between project management and environmentalism to increase awareness amongst project managers of the power they have to improve the greenality and effectiveness of their projects – whether or not they are directly involved with the environment.  Through their website EarthPM.com, Rich and Dave provide a variety of blog postings and resources, as well as consulting and course development services in Project Management and Green Project Management.

Rich Maltzman, MSIE, PMP, has more than 30 years of project management experience managing projects, leading project managers, consulting and teaching in Europe, the Middle East and the United States.  Currently, Rich is Senior Manager, Learning and Professional Advancement, at the Global Program Management Office of a major telecom concern. He is currently co-authoring a book with Ranjit Biswas, PMP, entitled “The Fiddler on the Project”, and posts regularly on his blog, Scope Crêpe, http://scopecrepe.blogspot.com.

Dave Shirley, MBA, PMP, has more than 30 years of project management experience in environmental and public health, and the telecommunications industry leading projects, project teams, managing project managers, consulting, teaching and course development.  He is currently developing a graduate course in Environmental Issues.  Dave is currently writing a book on project management for health care professionals.

VN:F [1.9.13_1145]
Rating: 8.3/10 (4 votes cast)
VN:F [1.9.13_1145]
Rating: +1 (from 1 vote)
Powered by WordPress & ecm design