Monday

Tag Archives: Value of Project Management

Australian Defence White Paper requires a major increase in project delivery capability.

The Australian Defence White Paper 2016, released today, will require a major increase in project delivery capability across defence.   For the first time, an integrated approach to capital investment planning is being used which will provide the framework for a more coherent and efficient approach to managing the development of future Defence capability. However, whilst a single investment program will reduce the risk of incomplete or fragmented approaches to investment, there will be a corresponding need to seriously ramp up capabilities in program[1] and portfolio management.

Coupled with a more complex (but potentially beneficial) management environment, there is also a major increase in the volume of projects and programs with an expenditure of approximately $195 billion (in today’s terms) planned for the next decade. Some of the projects and programs in the pipeline include:

  • Increasing the submarine force from 6 to 12 regionally superior submarines with a high degree of interoperability with the United States.
  • Three Hobart Class Air Warfare Destroyers (under construction).
  • A new class of nine future frigates.
  • New replenishment vessels.
  • More capable offshore patrol vessels,
  • New manned and unmanned aircraft for border protection.
  • A new large-hulled multi-purpose patrol vessel, the Australian Defence Vessel Ocean Protector.
  • The F-35A Lightning II program.
  • Twelve E/A-18G Growler electronic warfare aircraft.
  • More air-to-air refuellers will be acquired to support future combat, surveillance and transport aircraft.
  • New personal equipment for soldiers.
  • A new generation of armoured combat reconnaissance and infantry fighting vehicles, as well as new combat engineering equipment.
  • A new long-range rocket system to further enhance fire power,
  • Armed medium-altitude unmanned aircraft to enhance surveillance and protection for the land force.
  • Extending the life of and acquiring new weapons and equipment for the amphibious ships.
  • New light helicopters will be acquired to support Special Forces operations.
  • Upgrades to ADF bases and logistics systems, including fuel and explosive ordnance facilities.
  • Upgrade training and testing facilities, health services and information and communications technology.
  • Air lift capability will be increased to comprise 8 heavy lift C-17A Globemasters with additional heavy lift aircraft to be considered in the longer term, 12 upgraded C-130J Hercules, 10 C-27J Spartans and 10 CH-47F Chinook helicopters. Sea lift capability will be strengthened by extending the

Add the White Paper’s commitment to Australian industry involvement in most of these projects and the volume of work that will require effective project governance, management and controls becomes apparent. To download the white papers see: http://www.defence.gov.au/WhitePaper/

Fortunately Australia already has an effective forum focused on improving the capability of government and industry to govern and control its projects and programs.  The Project Governance and Controls Symposium, hosted by the University of Mew South Wales Canberra (ADFA), is focused on developing this capability and providing a forum for exchanging learning and ideas.  The 2016 Symposium is scheduled for May 10th to 12th, see: http://www.pgcs.org.au/

The Australia government has laid out the plans, its up to the project management profession to realise the intent, effectively and efficiently[2].   Watch this space…….


 

[1] Where the term ‘program’ is used to mean a series of projects (of very different types) managed together to achieve benefits that would not be available if they were managed separately. See: www.mosaicprojects.com.au/WhitePapers/WP1022_Program_Typology.pdf

[2] Improving the project delivery capability of Australian government departments is the focus of the separate Shergold report, see: /2016/02/20/the-shergold-report-calls-for-better-governance-and-better-project-controls/

Directing for Performance. The AICD moves beyond conformance.

The Australian Institute of Company Director’s (AICD) inaugural Australian Governance Summit 2016 focuses on ‘directing for performance’. The summit will explore beyond compliance to frame governance as a fundamental driver of performance outcomes.  A view we strongly support. For more information see: http://www.companydirectors.com.au/ags

The AICD have also identified a range of challenges and ‘disruptors’ that will affect organisations in 2016 presenting opportunities to organisations that can adapt and exploit the situation and threats to those who are slow. The vast majority of the threats and opportunities involve the rapidly changing digital economy which will require a radical change in the way most organisations integrate ICT into their businesses. Rather than being an enabler of business, in a connected world IT will increasingly be the business.

The Gartner IT Hype Cycle.
See: http://www.gartner.com/newsroom/id/2819918

One of the major challenges for organisations of all types identified by the AICD is a chronic lack of IT skills among Board members, with many boards populated by Directors who believe the digital economy will not affect their organisation because that are in the (fill in the gap) industry, not the IT industry.  The simple fact of life in the 21st century is that it does not matter if you are in agriculture, mining, manufacturing, personal services or any other business the successful organisations will be driven by the creation and use of information. Successful organisations will be able to find and use the ‘right information’ from the ever increasing torrent of ‘stuff’ being generated minute by minute:

Recognising the challenges and opportunities is one thing, adapting organisations to benefit from the changes is another!  What’s missing from the AICD evaluation this year is a focus on the central role of governing projects and programs to deliver the performance outcomes. Every change needs a project or program to create the ability to change backed up by organisational change capabilities to realise value.

Governing for change is the focus of ISO 21505, a project I’ve been involved with for the last 6 years, due for publication late 2016. It is also the focus of the annual Project Governance and Controls Symposium (PGCS), held in Canberra each May; see: http://www.pgcs.org.au/.

The challenge for organisations of all types and sizes is to adapt their governance and management structures to exploit the rapidly changing world.

Poor Governance creates complexity

All projects and programs have four dimensions that in aggregate determine how difficult they will be to manage. The four basic dimensions are:

  • Its inherent size usually measured in terms of value;
  • The degree of technical difficulty in creating the output (complication);
  • The degree of uncertainty involved in the project; and
  • The complexity of the relationships (‘small p’ politics) both within the project team and surrounding the project.

These aspects are discussed in our White Paper: Project Size and Categorisation

Of the four, size and technical difficulty are innate characteristics of the project and are not affected by governance, they simply need to be properly understood and managed.

Uncertainty always exists to a degree and can affect what techniques and what processes should be used for the best effect (what to do) and how to achieve the objective (how to do it). The biggest challenge with uncertainty is making sure all of the key stakeholders are ‘on the same page’ and understand what the currently level of uncertain is, and how the project team are planning to resolve the uncertainties. In combination, these uncertainties create four basic project typologies requiring different management approaches (also discussed in WP 1072). Most residual uncertainties can be managed through risk management processes.

Uncertainty is not the same as ambiguity – at the start of the construction process for the London Olympics there was a very high level of uncertainty concerning the extent and types of contamination affecting the ground and waterways, the best techniques for removing the contaminates, and the total cost and time that would be required to complete the work. However, there was absolutely no ambiguity about the requirement to fully decontaminate and remediate the site and the waterways. As the work progressed, the uncertainties reduced, the extent of the problem was defined, the site was fully remediated and the requirement was achieved.

Complexity is similar to uncertainty; there is always a degree of complexity associated with the many and various stakeholder relationships in and around the project. Internal ‘politics’ can be managed, controlled and used in a positive way provided the organisations governance and internal management disciplines are effective. External stakeholder relationships are more difficult to control and tie into the organisation’s overall corporate social responsibilities (CSR) and public relations (PR) activities.

But this is not the way many practitioners are experiencing complexity. The Project Management Institute (PMI) has recently published its latest Pulse of the Profession® In-Depth Report: Navigating Complexity

The worrying finding is that among the organisations surveyed whose portfolios were filled with what they defined as ‘highly complex projects’, 64 percent cited ambiguity as a defining characteristic of complexity in their projects while 57 percent cited the issue of managing multiple stakeholders. I would suggest neither of these characteristics is a true measure of complexity; but that allowing either to exist to the detriment of a project is a clear indication of weak or non-existent governance.

Ambiguity generally means the people working on the project do not know what they are supposed to achieve or there are different interpretations of what is to be achieved. Given unresolved ambiguity is a guaranteed way to ensure project failure, the open governance question is why are so many organisation allowing their managers to waste money working on a ‘project’ when there is no clearly defined objective? Good governance would require the waste to be stopped until the objective of the project is defined and the associated uncertainties understood. This does not require masses of detail, but does require clarity of vision.

When JFK stated in 1961 that “the United States should set as a goal the landing a man on the moon and returning him safely to the earth by the end of the decade”; no one knew how to achieve this in any detail but there was absolutely no ambiguity associated with what had to be accomplished and when it had to be achieved. What Kennedy did was not ‘rocket science’ (that came later); what he did was to create an unambiguous objective against which all future management decisions could be judged and empower everyone to keep asking “is this decision supporting the achievement of the objective (or not)?” Being a ‘good governor’ Kennedy had sought and received assurances that the goal was achievable before issuing the challenge, but he did not try to tell his engineers and scientists how to do their work. And as the saying goes, ‘the rest is history’.

The second area of complexity, identified in the PMI report, involving diverse politics and views will in part be resolved by creating a clear vision. However, the frequently occurring ‘turf wars’ between executives are very much a symptom of poor governance and control. A well governed and disciplined management team should vigorously debate concepts at the initiation stage, but once an investment decision has been made, recognise that working against the success of the initiative is counterproductive and damages the organisation. A key aspect of governance is creating a management culture that supports the organisation in the achievement of its objectives, turf wars and destructive politics are a symptom of weak executive management and poor governance.

Within the PMI findings, the one area where genuine complexity exists is where a project (or program) has multiple external stakeholders with divergent views and expectations that are frequently ‘unreasonable’ from the project’s perspective. A typical example is the motorists who will appreciate the reduced congestion and travel times after a freeway is widened but complain about the delays caused by the road works and the environmentalists who are opposed to the whole project ‘on principle’, knowing the money would be better spent on ‘clean’ public transport upgrades. Thousands of stakeholders, hundreds of different positions, wants and needs and everyone ringing their local papers and politicians…… this is real complexity.

In these situations there are no easy options, the only way to minimise the damage is carefully planned and implemented stakeholder engagement strategies that combine traditional communication options with more sophisticated corporate social responsibility (CR) and public relations (PR) initiatives. This is hard work and never 100% successful but essential to minimising the effect of complexity and to contribute to achieving a successful project outcome. The Stakeholder Circle® has been designed to provide the data management and analysis needed for this type of heavy duty stakeholder engagement.

Productivity decline should generate more projects

Projects and programs are the key organisational change agents for creating the capability to improve productivity through new systems, processes and facilities. But only if sensible projects are started for the right reason.

Declines in productivity seem to be widespread. In Australia, labour productivity in the market sectors of the economy increased at 2.8% per annum between 1945 and 2001, reducing by 50% to an annual rate of 1.4% between 2001 and 2001.

  • The measure of Labour Productivity is the gross value added per hour of work.
  • The ‘market sectors’ measured exclude public administration, education and healthcare where measurement is almost impossible.

Some of this change can be attributed to macro economic factors, there were massive efficiency gains derived from the shift from paper based ‘mail’ and copy typist to the electronic distribution of information, improved global transport systems (particularly containerisation) and the restructuring of manufacturing post WW2. These massive changes in the last half of the 20th century are not being replicated in current.

Whilst this decline in the rate of improvement in labour productivity is significant, the capital inclusive index is a more telling statistic. The multi-factor productivity index which includes the capital invested in production, giving a purer measure of the efficiency with which labour and capital are combined to produce goods and services. In the six years leading up to 2001, this measure of productivity grew by an average of 1.5% per annum, in the decade between 2001 and 2011 this reversed and productivity fell by 0.4% per annum.

Around 40% of the decline in the last decade can be explained by massive investments in mining and utilities that have yet to generate a return on the capital invested. The other 60% represents the massive cost of ‘new capabilities’ in general business for relatively small, or no improvement in productivity.

One has only to look at the ever increasing number of ‘bells and whistles’ built into software systems ranging from high definition colour screens to features that are never used (and the cost of upgrading to the ‘new system’) to understand the problem. 90% of the efficiency gain came with the introduction of the new system many years ago, the on-going maintenance and upgrade costs often equal the original investment but without the corresponding improvement in productivity. Another area of ‘investment’ for 0% increase in productivity is compliance regimes. Whilst there may be good social arguments for many of these requirements, the infrastructure and systems needed to comply with the regulations consume capital and labour without increasing productivity.

In Australia general management have been rather slow to appreciate the challenge of declining productivity, the impact being cushioned by a range of other factors that helped drive profitability. But this has changed significantly in the last year or so. There is now an emerging recognition that productivity enhancing organisational change is an imperative; and smart management recognise this cannot be achieved through capability limiting cost reductions.

Organisations that thrive in the next decade will:

  • Enhance customer satisfaction and service,
  • Enhance their engagement with their workforce, the community and other stakeholders,
  • Enhance their products and capabilities, and
  • Improve their labour productivity.

Achieving a viable balance across all four areas will require an effective, balanced strategy supported by the efficient implementation of the strategic intent through effective portfolio, program and project management capabilities that encompass benefits realisation and value creation.

The three key capabilities needed to achieve this are:

  • The ability to develop a meaningful and practical strategic plan.
  • An effective Project Delivery Capability (PDC); see: WP1079_PDC.
  • An effective Organisational Change Management Capability; see: WP1078_Change_Management.

Improving productivity is a major challenge for both general management and the project management community; and the contribution of stakeholder management and project management to the overall effort will continue to be a focus for this blog.

Linking Innovation to Value

In a recent post looking at the The failure of strategic planning  and the overall value delivery chain centred on projects and programs, the link between innovation and the strategic plan was raised briefly. The purpose of this post it to take a closer look at this critical ‘front end’ of the value chain because it does not matter how well you do the wrong projects! The ability to generate sustainable value for an organisation’s stakeholders requires the right projects to be done for the right reasons; and yes, they also need to be done right!

The section of the ‘value chain’ leading into a portfolio management decision to select a project or program as a viable investment is far more complex than the section after. Once a project or program has been selected, it needs to be accomplished efficiently, the outputs transferred to the organisation and the organisation adapt to make efficient use of the ‘deliverables’ to realise the intended benefits and generate value. This flow of work is primarily the responsibility of the project/program sponsor initially supported by project and program management, and then by organisational ‘line management’ until the final transition to ‘business as usual’ operations.

Developing a business case to the point where it can be accepted for investment is more complex, involves a wide spectrum of managers and potentially involves a number loops.

The three elements in this section of the overall ‘value chain’ are a viable strategic plan, a realistic business case that supports an element of the strategy and an effective portfolio management system to optimise the overall portfolio of projects and programs the organisation is capable of investing in.

The key is an effective and viable strategic planning process that is capable of developing a realistic strategy that encompasses both support and enhancements for business as usual, and innovation. Strategic planning is a complex and skilled process outside of the scope of this post – for now we will assume the organisation is capable of effective strategic planning.

The sign of an ineffective, unresponsive strategic planning process is seeing business cases fired off by business units without any reference to the strategic plan or worse projects being started without strategic alignment. The option to bypass the strategic planning may be valid in an emergency but not as a routine option. In a well disciplined value creation process, the portfolio management team simply reject business cases that cannot demonstrate alignment with the organisations strategic intentions. The red arrow in the diagram above simply should not be allowed to occur in anything other then an emergency situation.

The Portfolio/Strategic link (blue arrow)
There is a close link between the portfolio management processes  and strategic planning – what’s actually happening in the organisation’s existing projects and programs is one of the baselines needed to maintain an effective strategic plan (others include the current operational baseline and changes in the external environment). In the other direction, the current/updated strategy informs the portfolio decision making processes. The strategic plan is the embodiment of the organisation’s intentions for the future and the role of portfolio management is to achieve the most valuable return against this plan within the organisation’s capacity and capability constraints.

Routine inputs to the Strategic Plan (light green arrows)
The routine inputs to the strategic planning process come from the ‘organisation’ and include requirements, opportunities, enhancements and process innovations (eg, new software releases). These basic inputs are the core information required for strategic planning and form the majority of the new information in each update of the strategy.

The Innovation / Strategic Plan loop (light blue arrows)
This is the first of the more complex spaces – innovative ideas can come from anywhere in the business and are actively encouraged by leading organisations such as Google and 3M. Conversely, an organisational objective may require innovation to allow it to come to fruition. One of the most challenging objectives in recent times was Kennedy’s commitment to “before this decade is out, [land] a man on the moon and return him safely to earth.” The amount of scientific innovation required to achieve this objective was incredible.

The organisation’s governance processes and strategic development processes need to both encourage innovation whilst recognising that not every innovative idea will be appropriate for the overall development of the organisation. This requires the implementation of systems to encourage innovation, collect and sort innovative ideas and move the ‘right’ ideas into the strategic plan, where necessary revising and changing the plan to grab the innovative advantage.

The Feasibility loop (orange and yellow arrows)
Having innovative ideas and creative business cases is one thing, validating the feasibility of an idea is altogether different! The ability to test, validate and work-up innovative ideas into practical project specifications is a critical organisational capability. On mega projects the pre-feasibility and feasibility studies may in fact be significant projects in their own right involving considerable expenditure, feeding back to a gateway or portfolio management process to allow the next stage of the project to commence.

Several of the ‘gateways’ defined in most standard ‘gateway processes’ precede the commissioning of the main project and the organisation needs the capability to make informed decisions based on good quality information. This aspect of the value creation chain is industry specific and may be a central function or distributed across different business centres. What matters is the capability exists with the necessary skills to validate ideas and design projects ready for the more traditional project management processes to take over once the project is formally authorised.

Conclusion
The long term viability of any organisation depends on its ability to innovate. Traditional project and program management focus on doing the selected projects/programs ‘right’. But it is the ‘front end’ processes discussed in this post leading up to the investment decision that determine if the ‘right’ project is being selected for the ‘right’ reasons!

The effective governance of an organisation should require its management to invest sufficient skills and resources in these ‘front end’ processes to ensure a steady flow of innovative ideas, feeding into an effective and flexible strategic planning system, linked to a disciplined portfolio management process; to ensure the optimum mix of ‘right’ projects and programs are commissioned and supported.

Advising Upwards for Effect

The only purpose of undertaking a project or program is to have the deliverables it creates used by the organisation (or customer) to create value! Certainly value can be measured in many different ways, improved quality or safety, reduced effort or errors, increased profits or achieving regulatory compliance; the measure is not important, what matters is the work of the project is intended to create value. But this value will only be realised if the new process or artefact ‘delivered’ by the project is actually used by the organisation to achieve the intended improvements.

The organisation’s executive has a central role in this process. There is a direct link between the organisation’s decision to make an investment in a selected project and the need for the organisation to change so it can make effective use of the deliverables to generate the intended benefits and create a valuable return on its investment. The work of the project is a key link in the middle of this value creation chain, but the strength of the whole chain is measured by its weakest link – a failure at any stage will result in lost value.

In a perfect world, the degree of understanding, knowledge and commitment to the change would increase the higher up the organisational ladder you go. In reality, much of the in-depth knowledge and commitment is embedded in the project team; and the challenge is moving this knowledge out into the other areas of the business so that the whole ‘value chain’ can work effectively (see more on linking innovation to value).

To achieve this, the project team need to be able to effectively ‘advise upwards’ so their executive managers understand the potential value that can be generated from the initiative and work to ensure the organisation makes effective use of the project’s deliverables. The art of advising upwards effectively is the focus of my book ‘Advising Upwards’.

An effective Sponsor is a major asset in achieving these objectives, providing a direct link between the executive and the project or program. Working from the top down, an effective sponsor can ensure the project team fully understand the business objectives their project has been created to help achieve and will work with the team to ensure the project fulfils its Charter to maximise the opportunity for the organisation to create value.

Working from the bottom up, new insights, learning and experience from the ‘coal face’ need to be communicated back to the executive so that the overall organisational objectives can be managed based on the actual situation encountered within the work of the project.

The critical importance of the role of the sponsor has been reinforced by numerous studies, including the PMI 2012 Pulse of the Profession report. According to this report, 75% of high performance organizations have active sponsors on 80% of more of their projects (for more on the value of sponsorship see: Project Sponsorship).

If you project has an effective sponsor, make full use of the support. The challenge facing the rest of us is persuading less effective sponsors to improve their level of support; you cannot fire your manager! The solution is to work with other project managers and teams within your organisation to create a conversation about value. This is a very different proposition to being simply ‘on-time, on-scope and on-budget’; it’s about the ultimate value to the organisation created by using the outputs from its projects and programs. The key phrase is “How we can help make our organisation better!”

To influence executives within this conversation, the right sort of evidence is important; benchmarking your organisation against its competitors is a good start, as is understanding what ‘high performance’ organisations do. PMI’s Pulse of the Profession is freely available and a great start as an authoritative reference.

The other key aspect of advising upwards is linking the information you bring into the conversation with the needs of the organisation and showing your organisation’s executive how this can provide direct benefits to them as well as the organisation.

In this respect the current tight economic conditions in most of the world are an advantage, organisations need to do more with less to stay competitive (or effective in the public service). Developing the skills of project sponsors so that they actively assist their projects to be more successful is one proven way to achieve a significant improvement with minimal cost – in fact, if projects are supported more effectively there may well be cost savings and increased value at the same time! And what’s in it for us as project managers? The answer is we have a much improved working environment – everyone wins!!

The value of stakeholder management

One of the questions I’m regularly asked is to outline the business case for using stakeholder management in a business or project. This is a difficult question to answer accurately because no-one measures the cost of problems that don’t occur and very few organisations measure the cost of failure.

The problem is not unique; it is very difficult to value the benefits of an effective PMO, of improving project delivery methods (eg, improving the skills of your schedulers), of investing in effective communication (the focus of my September column in PMI’s PM Network magazine) or of better managing risk. The costs of investing in the improvement are easily defined, but the pay-back is far more difficult to measure.

There are two reasons why investing in effective stakeholder analytics is likely to deliver a valuable return on investment (ROI).

  • The first is by knowing who the important stakeholders are at any point in time, the expenditure on other processes such as communication can be focused where it is needed most, generating efficiencies and a ‘bigger bang for your buck’.
  • The second is stakeholders are a major factor in the risk profile of the work, their attitudes and actions can have significant positive or negative consequences and understanding the overall community provides valuable input to a range of processes including risk identification, requirements definition and schedule management.

At the most fundamental level, improving the management of stakeholders is directly linked to improving the quality of the organisation’s interaction with the stakeholders and as a consequence, the quality of the goods or services delivered to the end users or client (ie, stakeholders) as a result of being better informed whilst undertaking the work.

Quality was defined by Joseph Juran as fit for purpose, this elegant definition applies equally to the quality of your management processes as it does to your production processes and to the deliverables produced. And the three elements are interlinked; you need good management systems and information to allow an effective production system to create quality outputs for delivery to the client. A failure at any point in the chain will result in a quality failure and the production on deliverables that do not meet client requirements.

Placing stakeholder management within the context of quality allows access to some reasonably well researched data that can be interpolated to provide a reasonable basis for assessing the ‘return’ likely to be generated from an investment in stakeholder management.

Philip B. Crosby invented the concept of the ‘cost of quality’ and his book, Quality Is Free set out four major principles:

  1. the definition of quality is conformance to requirements (requirements meaning both the product and the customer’s requirements)
  2. the system of quality is prevention
  3. the performance standard is zero defects (relative to requirements)
  4. the measurement of quality is the price of nonconformance

His belief was that an organization that established a quality program will see savings returns that more than pay off the cost of the quality program: “quality is free”. The challenge is knowing you fully understand who the ‘customers’ actually are, and precisely what their various requirements and expectations are, and having ways to manage mutually exclusive or conflicting expectations. Knowing ‘who’s who and who’s important’ is a critical first step.

Feigenbaum’s categorization of the cost of quality has two main components; the cost of conformance (to achieve ‘good’ quality) and the cost of poor quality (or the cost of non-conformance).

Derived from: Feigenbaum, Armand V. (1991), Total Quality Control (3 ed.), New York, New York: McGraw-Hill, p. 109, ISBN 978-0-07-112612-0.

The cost of achieving the required level of quality is the investment made in the prevention of non-conformance to requirements plus the cost of testing and inspections to be comfortable the required quality levels have been achieved.

The cost of poor quality resulting from failing to meet requirements has both internal and external components. The internal costs are associated with defects, rework and lost opportunities caused by tying people up on rectification work. External failure costs can be much higher with major damage to an organisation’s brand and image as well as the direct costs associated with fixing the quality failure.

The management challenge is balancing the investment in quality against the cost of quality failure to hit the ‘sweet spot’ where your investment is sufficient to achieve the required quality level to be fit for purpose; overkill is wasted $$$$. But first you and ‘right stakeholders’ need to agree on precisely what fit for purpose actually means.

Also, the level of investment needed to achieve the optimum cost of quality is not fixed. The better the organisation’s quality systems, the lower the net cost. Six sigma proponents have assessed the total cost of quality as a percentage of sales based on the organisations sigma rating.

This table demonstrates that as the quality capability of the organisation improves, the overall cost of quality reduces offering a major competitive advantage to higher rating organisations. Most organisations are rated at 3 Sigma so the opportunity for improvement is significant.

Within this overall framework, the costs and risks associated with poor stakeholder engagement are significant and follow the typical pattern where most of the costs of poor quality are hidden. Using the quality ‘iceberg metaphor’ some of the consequences of poor stakeholder engagement and communication are set out below:

Effective stakeholder analysis and management directly contributes to achieving the required quality levels for the organisation’s outputs to be fit for purpose whilst at the same time reducing the overall expenditure on the cost of quality needed to achieve this objective. The key components are:

  • Effective analysis of the stakeholder community will help you identify and understand all of the key stakeholders that need to be consulted to determine the relevant aspects of fit for purpose.
  • Understanding the structure of your stakeholder community facilitates the implementation of an effective two-way communication strategy to fully understand and manage the expectations of key stakeholders.
  • Effective communication builds trust and understanding within a robust relationship.
    o Trust reduces the cost of doing business.
    o Understanding the full set of requirements needed for the work to be successful reduces the risk of failure.
    o Robust relationships with key stakeholders also contribute to more effective problem solving and issue management.
  • Maintaining the stakeholder engagement effort generates enhanced information that will mitigate risks and issues across all aspects of the work.

Calculating the Return on Investment:

Effective stakeholder management is a facilitating process that reduces the cost, and increases the efficiency of an organisations quality and risk management processes. Based on observations of similar process improvement initiatives such as CMMI, the reduction in the cost of quality facilitated by improved stakeholder engagement and management is likely to be in the order of 10% to 20%.

Based on the typical ‘Level 3’ organisation outlined above, a conservative estimate of the efficiency dividend per $1million in sales is likely to be:

Total cost of quality = $1,000,000 x 25% = $250,000
Efficiency dividend = $250,000 x 10% = $25,000 per $1 million in sales.

Given the basic costs of establishing an effective stakeholder management system for a $5million business, using the Stakeholder Circle®, (See: http://www.stakeholder-management.com) including software and training will be between $30,000 and $50,000 the efficiency dividend will be:

($25,000 x 5) – 50,000 = $75,000
(or more depending on the actual costs and savings).

The element not included above is the staff costs associated firstly with maintaining the ‘culture change’ associated with introducing an effective stakeholder engagement process and secondly with actually performing the stakeholder analysis and engagement. These costs are embedded in the cost of quality already being outlaid by the organisation and are inversely proportional to the effectiveness of the current situation:

  • If current expenditures on stakeholder engagement are relatively low, the additional costs of engagement will be relatively high, but the payback in reduced failures and unexpected risk events will be greater. The overall ROI is likely to be significant.
  • If the current expenditures on stakeholder engagement are relatively high, the additional costs will be minimal (implementing a systemic approach may even save costs), however, the payback in reduced failure costs will be lower because many of the more obvious issues and opportunities are likely to have been identified under the current processes. The directly measurable ROI will be lower, offset by the other benefits of moving towards a higher ‘Sigma level’.

Conclusion:

The introduction of an effective stakeholder management system is likely to generate a significant ROI for most organisations. The larger part of the ‘return’ being a reduction in the hidden costs associated with poor stakeholder engagement. These costs affect reputation and future business opportunities to a far greater extent than their direct costs on current work. For this reason, we feel implementing a system such as the Stakeholder Circle is best undertaken as a strategic organisational initiative rather than on an ad hoc project or individual workplace basis.

The path to organisational Stakeholder Relationship Management Maturity (SRMM®) is discussed at: http://www.stakeholdermapping.com/srmm-maturity-model

The Capital Crime

A recently published, free e-book, ‘The Capital Crime’ focuses on the massive loss and waste of capital being perpetrated on an ongoing basis in most organizations across the world, through their executive management, failing to effectively ‘manage the management’ of projects and programs.

Cobb described his Paradox more than 15 years ago , but organisations still deliberately set up projects so they are almost guaranteed to fail and waste vast amounts of capital as a result. However, fixing Cobb’s Paradox and doing projects ‘right’ is only part of the answer, a wider capability is needed focused on using capital effectively in support the organisations strategy to generate real value for the organisation’s stakeholders!

We refer to this as ‘Project Delivery Capability’ or PDC; the e-book’s authors use a wider definition, ‘Value Delivery Capability’. Regardless of the name, we agree with Jed Simms, the only piece of the value delivery chain that is understood is the piece in the middle called ‘project management’. The surrounding envelope of organisational abilities to only start the ‘right projects’, set the selected projects up for success and then make effective use of the project deliverables to create value is poorly understood – the strength of a chain is defined by its weakest link, not its strongest!

The consequence of this lack of understanding of the ‘value chain’, at the very top of the organisation, is organisations setting their project up to fail, failing to support projects during their execution, and failing to make use of the project deliverables to generate value. The failure of any of these ‘weak links’ reduces the organisations ability to achieve its strategy and a return on investment. The associated waste of capital caused by sub-optimal project outcomes is the core of the ‘capital crime’ discussed in an easy to read ‘story’ format in the free e-book, ‘The Capital Crime’.

You are invited to download your copy of ‘The Capital Crime’ from: http://www.thecapitalcrime.com/

Management -v- Governance

Some areas of business seem to be confusing the concepts of organisational governance and effective management to the detriment of both processes. One of the important aspects of ‘good governance’ is to create the environment that allows ‘good management’ to be practiced and to require systems that ensure ‘good management’ is practiced at all levels of the organisation’s management, but governance and management are quite different processes undertaken by different groups of people.

As a basic starting point, Governance is the exclusive responsibility of the Board of Directors, or their equivalent, not management – the governing body (typically Directors) directs and governs; managers manage at various levels.

The three primary levels of involvement are:

  • Governance. The governing Board sets the organisation’s objectives, agrees the strategy to achieve the objectives, define policies and rules for the organisation, requires effective management systems, and also requires processes to be in place to ensure these are implemented by management and to provide effective oversight to the governing body. This is the exclusive non-transferable responsibility of the Board.
     
  • Executive management. The executive’s role is creating the organisation capable of achieving these requirements and providing input and advice to assist the governing body’s decision making processes. Developing an effective culture of openness and accountability is a core executive responsibility.
     
  • General management. Senior and operational management’s roles are to develop and maintain the systems and processes needed to make the organisation effective within the parameters set by the executive. This includes supporting middle and lower management so they can effectively manage the work needed to implement the strategy set by the Board.

For some reason, these different roles are being confused in some business domains, including IT and project management to the detriment of the organisation and the respective disciplines. When a group of managers start referring to ‘normal good management’ practices as ‘governance’, they simply create excuses for bad management practice.

A good example is a project steering committee failing to support a project manager by refusing to make a difficult decision. This lack of support can be defined in two different ways:

  • By claiming the committee is a governance body responsible for ‘governing’ the project, usually interpreted as making sure the project does not do ‘wrong things’, the imperative for a timely decision is removed or hidden, the requirement is no wrong doing which translates into not making a wrong decision. If the project fails as a consequence of the lack of decision, it is called a ‘project failure’ not a governance failure.
     
  • Change the description of the same steering committee to the management entity responsible for the overall creation of value within the organisation based on the work of the project they are overseeing, the situation changes. As the management group responsible for implementing and managing the overall Project Delivery Capability (PDC) needed by the organisation to achieve a positive ROI on its investment in the project, the same failure to make a decision can be seen to have a direct impact on the ROI the managers in the steering committee are personally responsible for achieving. This is a management failure and the managers in the steering committee are directly accountable for the delays caused to the project.

Similar issues to the project management obfuscation described above also attach to calling pragmatic and effective management of IT processes ‘governance’ – data security, backups and recovery capabilities, other IT functions and managing the projects needed to enhance IT are not IT governance issues, they are IT management responsibilities.

My personal view is that if the project and IT management practices described above are determined to be a ‘governance’ function, almost everything in management is ‘governance’, fortunately:

  • No one claims the processes used to make sure the accounts department pay the right people the right amount of money at the right time is a ‘governance’ process – it is seen to be a prudent accounting requirement.
     
  • Similarly no one claims the processes used by the stock department to fill orders with the right goods, and ship them to the right customers is ‘governance’; it is simply a customer service process.

IT and project management should be no different!

The art of good governance is for the Directors to ask the right questions of the executive and have sufficient skills to understand the answers. I do not know of a good resource to help in this respect for IT, however, a really useful (and free) guide to help Board’s ask the right questions of their executive about PDC has been published by the Association for Project Management in the UK, it can be downloaded from: http://www.mosaicprojects.com.au/PDF/APM%20GoPM%20booklet.pdf

Once the Board starts asking the ‘right questions’ and sets a strategic framework my feeling is any executive manager worthy of his/her role will start taking appropriate actions and adapting their organisation. If they don’t the Board probably needs to start asking other questions about the suitability of the executive. However, changing the organisation to achieve effective PDC is a major change program in itself and will need time to be effective……

One short term solution that can be used to kick-start the cultural and organisational changes needed to move to an effective PDC is already in the hands of the governing body and executive. If the organisation cannot find a committed senior manager prepared to take personal responsibility for delivering the value promised by a project do not start the work! We know the lack of effective sponsorship is closely aligned to project failure, so it will be far cheaper and preserve shareholder value if projects without effective sponsors are not started. Conversely, if senior managers are responsible for the delivery of value from the projects they are sponsoring, the key people needed to create effective change in an organisation are already involved and have a vested interest in succeeding.

The important thing to remember is the realisation of value from effective benefits management is very much the end of a process. The overall capability to realise value from an investment in a project starts with selecting the right project to do for the right strategic reasons, then doing the work of the project effectively and efficiently before the organisation can implement the changes and generate value. The project manager is only responsible for the bit in the middle – the ‘doing the project right’, a steering committee, sponsor or other management entity is responsible for the beginning and end parts of the overall process as well as supporting the project team. Therefore PDC has to be seen as a general management responsibility.

The management concepts and framework needed to develop an effective PDC within an organisation have been discussed in earlier posts:

  • The concept of ‘project failure’ -v- ‘management failure’ is discussed in our post Project or Management Failures?.
     
  • Similarly, PDC and the organisational aspects of change have been discussed in length in a series of earlier posts, see:
  • An overview of the management framework needed to achieve effective PDC is in our White Paper: PDC Taxonomy – this White Paper is a conceptual framework not a methodology and is evolving, but should still be helpful in separating ‘governance’ from ‘management’.

These ideas are not new, work by the Boston Group in the 1990s reported in our latest blog, the PDC Value Proposition shows the significant increase in ROI when an effective project delivery capability level is achieved by an organisation.

The governance requirement is to ensure management accepts this responsibility and excel in creating value for the organisation.

Project or Management Failures?

Google ‘reasons for project failure’ and you get nearly 5 million responses! The question this blog asks is how many project failures are caused by project management shortcomings and how many failed projects were set up to fail by the organisation’s management?

The Project Delivery Capability (PDC) framework described in our White Paper Project Delivery Capability (PDC) offers a useful lens to separate the failings generated by project performance from those imposed on the project, inadvertently, or otherwise by organisational management.

The list below separates the root cause of failure into four categories based on this model:

Initiation: failures associated with project identification, business case development, requirements definition and portfolio selection; including establishing initial realistic time and cost budgets based on pragmatic risk assessments.

Project: failures associated with the project team failing to apply effective project management processes as defined in resources such as the PMBOK® Guide, ISO 21500 and PRINCE2

Support: failures associated with the lack of effective senior management support to the project (Capability Support), including inadequate sponsorship, failing to provide appropriate resources, inadequate business inputs, lack of direction/decisions and allowing excessive change.

Benefits: the failure to realise the intended value from the project’s deliverables associated with poor organisational change management, end use adoption and cultural resistance (for more on the overall scope of change see our White Paper, Organisational Change Management).

The table below is based on an amalgamation of dozens of lists found through a Google search.

Reason for FailureCause
Inadequate business case
A good business case will clearly demonstrate the business benefit of delivering a project and define the objectives, requirements and goals.
Initiation
Undefined objectives and goals
This is always a problem, if the organisation does not know what it wants, it is impossible to scope a project to deliver the ‘unknown’.
Initiation
Inadequate or vague requirements
This is only a problem if the organisation fails to allow adequate time and appropriate contingencies in the overall scope of the project to define and firm up requirements. Defined requirements are essential for the project to be able to deliver a successful outcome.
Initiation
Unrealistic timeframes and budgets; unachievable objectives
Fact free planning is always a problem. Initial ‘rough order of magnitude’ estimates need appropriate contingencies in the initial business case. The project outputs need to be feasible.
Initiation
Lack of prioritisation and project portfolio management
Causing competing priorities leading to inadequate support and resourcing for projects.
Initiation
Estimates for cost and schedule are erroneous
Estimates should be based on solid foundations. Unrealistic targets are unlikely to be achieved.
Initiation / Project
Failure to set and manage expectations
Unrealistic expectations are unlikely to be fulfilled. From the start of the initiation through the life of the project effective communication to set and maintain realistic expectations is vital.
Initiation / Project
Business politics
Lack of discipline within executive/senior management. Only present is the organisation is poorly governed and lacks a rigorous portfolio management process. Selected projects should be supported by management.
Initiation / Benefits
Cultural and ethical misalignment
Misalignment between the project team and the business or other organization it serves will inevitably cause problems.
Initiation / Benefits
Lack of a solid project plan
The failure to develop an effective project plan guarantees the project will fail. The type of planning required depends on the project methodology. Some specifics are included below
Project
Poor estimating
Failing to use historical information, formulae, and questions to make sure that the estimate is not a GUESStimate.
Project
Poor processes/documentation
Appropriate processes and documentation are essential for project success.
Project
Poor risk management
All projects are inherently risky. Effective risk management reduces the degree of uncertainty to an acceptable level.
Project
Overruns of realistic schedule and cost estimates
This is a project failing. Either due to poor management/motivation of the project team or poor risk assessment (leading to inadequate contingencies) or poor estimating.
Project
Failure to track progress
Tracking progress against the plan and adapting performance is central to effective project management.
Project
Poor Testing
Failing to adequately test project deliverables; including:
– Poor requirements which cannot be tested
– Failing to design a testable system
– Failing to develop a realistic and effective test plan
– Failing to test effectively with skilled staff
– Inadequate time and budget allowed for testing.
Project
Poorly defined roles and responsibilities
The organisations management is responsible for defining roles and responsibilities in the overall management stakeholder community; the project manager is responsible for the organisation within the project team.
Project / Support
No change control process / Scope creep
A lack of effective change management processes is primarily a project failing, however, organisational management should require effective change management to be in place and support the change management processes.
Project / Support
Team weaknesses – Inadequate / incorrectly skilled resources
Having people who are ill-prepared to complete a task can be worse than not having anyone. The organisation is responsible for providing adequate internal resources for the project, the project is responsible for defined training and procuring appropriate contracted resources.
Support / Project
Lack of user input
The organisation is responsible for organising the necessary input from end users. The project is responsible for requesting and defining its needs and making appropriate use of the information provided.
Support / Project
Lack of management commitment / Lack of organisational support
The organisation is responsible for properly supporting the projects it has initiated.
Support
Ineffective or no sponsorship
Ineffective project sponsorship is almost a guarantee of failure.
Support
Poorly managed – project manager not trained/skilled
The organisation is responsible for appointing an appropriate project manager and providing him/her with appropriate support, training and coaching.
Support
Inflexible processes and procedures, templates and documentation
Any imposed process needs to be as light  as practical to meet the governance needs of the organisation without inhibiting the work of the project.
Support
Insufficient or Inadequate resources / lack of committed resources
(funding and personnel)
The organisation is responsible for properly resourcing the projects it has initiated. If the resources don’t exist or are already fully committed elsewhere, this is an initiation failure; if they are simply not made available it is a support failure.
Support / Initiation
Poor communication / Stakeholder engagement
People tend to fear what they don’t know, therefore effective communication with stakeholders is vital if the project is to capture their support, and keep it. The project is responsible for project based communications; the organisation change manager (sponsor) is responsible for communication in support of the overall change initiative.
Benefits / Project
Poor or ineffective organisational change management
The organisation has to implement, accept and use the project’s deliverables to generate value. Failures at the organisational change level mean most of the planned benefits cannot be realised.
Benefits
Stakeholder conflict
The organisation is responsible for properly supporting the projects it has initiated. This includes the ‘through life’ management of stakeholders starting prior to initiation and continuing through to the realisation of the
benefits.
Benefits
Inability or unwillingness to stop a project after approval
‘Death march’ projects destroy value. A key element of effective portfolio management is to stop wasting money and resources on projects that can no longer contribute value to the organisation.
Benefits

Of the 29 causes of failure outlined above, only 7 are exclusively the province of project management. The other 76% involve or are exclusively the province of the organisation’s general and executive management as part of an overall ‘Project Delivery Capability’!

This overall capability of an organisation to realise value from an investment in a project starts with selecting the right project to do for the right reasons, then doing the work of the project effectively and efficiently, and then making effective use of the project’s outputs to create value. Mess up any of the early stages and there are no benefits to manage. If the organisation fails to implement the changes effectively, the potential benefits are not realised.

The project manager is only responsible for the bit in the middle – the ‘doing of the project’, a steering committee, sponsor or other management entity is responsible for the beginning and end parts of the overall process involved in PDC. Even the 24% of failures assigned to project management have a link back to the role of the Project Director within PDC. The organisation should provide oversight, training and support to ensure effective processes are used by their project managers and teams. Conversely, a skilled project manager may be able to overcome some of the organisational failings identified above; by managing upwards and operating effectively within the organisation’s political systems a skilled project manager can cover some failings, others are fundamental and will result in a failure regardless of the efforts of the project team.

Therefore based on this table, it is reasonable to determine PDC is an executive and general management responsibility. The ‘project governance’ requirement within PDC is for the Board to ensure executive and general management accept this responsibility and excel in creating value for the organisation.

Based on this assessment, my personal feeling is we as project practitioners need to stop referring to ‘project failures’  every time a project fails to deliver the expected value and start talking about ‘business failures’ when the organisation’s  management fails to effectively manage or support the work and as a consequence, fails to achieve the intended/expected value.