Many organisations, while accustomed to the demands of managing individual projects, are ill-equipped to handle the complexity of larger-scale Programmes. Here are 10 essential elements of programme management. The past decade has seen a considerable increase in the level of awareness, formal education, application and standardisation of project management as a recognisable discipline for accomplishing relatively narrow organisational goals. Yet programme management - in the form of a structured set of methods, tools and techniques - has only recently seen popularity gains. Much of this emergence of interest may be attributed to increasingly demanding business environments and communities.
Organisations can no longer rely on past beliefs, expertise and technology to succeed. The rapid pace of innovation and the rising level of management, stakeholder and consumer expectations demand that companies reassess and reinvent every facet of their existence in order to survive, compete and flourish. Resolving the struggle between tradition and transformation requires a vehicle for managing change that can be trusted. This is the essence of programme management.
Evidence of the growing importance of programme management as a discipline in its own right is reflected in the launch of a formal Programme Management Professional certification by the Project Management Institute. According to the PMI, programme management is defined as: "A group of related projects managed in a coordinated way to obtain benefits and control not available from managing them individually."
Yet, while this definition provides an accurate project perspective, it omits the central purpose of a programme, which is to effect strategic change in an organisation. The scale of such change is implicitly far wider than that of an individual project; Programmes often facilitate change not only within a specific division or department but across an entire organisation.
While there is no clear boundary separating a project from a programme, Programmes generally possess, among other variables, a higher degree of complexity, a larger number of deliverables and a more fluid timeline than projects. Projects, in contrast, have distinct start and end dates as a defining characteristic. What is clear, however, is that Programmes can and do fail for a multitude of reasons.
The challenges of programme management are both considerable and diverse. According to Gartner, "Sixty six percent of large programme initiatives fail to achieve their stated business objectives. Further, they are delivered late or substantially over budget." Meeting these challenges demands full and unrelenting attention, both to the big picture and to the detail. Most programme failures are ultimately people-related, spanning a range of causes, including but not limited to underestimating programme complexity; lack of firm leadership, commitment and sponsorship; poor cross-functional communication; lack of integrated planning; no defined success metrics; poor requirements management; lack of broad change management; misaligned stakeholder expectations; inadequate programme management skills; and lack of resources.
The goal of effective programme management must be to define, organise, plan and execute in such a way that the causes of failure can be minimised. Simply put, this means risk management. Due to the variety and complexity of programme challenges, many of the aforementioned failure sources are interrelated. Therefore, it is possible to properly address many of them by implementing a targeted group of mitigation practices.
Overcoming causes of programme failure requires a variety of skills and methods. From initial evaluation of the programme within a portfolio management framework to the measurement of project outcomes and benefits, there are 10 essential steps that programme managers must take to achieve success. While some of these steps are performed by the programme manager and some may be performed by others, it is the programme manager's responsibility to make sure each step is performed properly.
1. Generate a Solid Business Case
The first phase in the life cycle of a programme is the feasibility stage. For some Programmes, this may also be the last phase. But whether the programme is terminated or continued, a firm basis for arriving at the critical go/ no go decision is needed. This is provided by the business case.
An effective business case should comprise content that aligns with the organisation's project portfolio management framework. In particular, it should reflect those strategic dimensions considered most important by the senior management team and clearly articulate to what extent the programme would address and support these dimensions. This will, therefore, facilitate an objective evaluation of the candidate programme against a range of well-defined scoring criteria. Fundamentally, the business case must address the following questions:
>Why is the programme important and what does it need to achieve? >What is the current state and why does it need to change? >What will the end state look like? The answers to these questions will implicitly include a description of the anticipated outcomes and benefits. These will then need to be weighed against order of magnitude estimates on what it will take to execute the programme, including the level of funding, extent of organisational change, degree of risk and overall timing. Acquiring the right level and quality of data to satisfy the decision makers will often entail an iterative process - multiple reviews and refinements of the business case may be required and, indeed, expected.
This business case development process is conducted during Strategic Enterprise Analysis (SEA). SEA provides the input necessary to come to the right decisions for the organisation. SEA takes a close look at the organisation's business architecture and what the impact to the business is at multiple levels. The decision packages that are generated during SEA allow for early phase-gate decision making, culminating in the final decision package known as the business case.
2. Establish the Right Programme Organisation
While Programmes will differ vastly in terms of team size, best practices identify a number of crucial roles that must exist at the programme leadership and management level in order to ensure proper governance: The success of a programme, like a project, will depend heavily on the quality of sponsorship it receives. The scope and scale of a programme means that sponsorship typically resides not with one person but, rather, is distributed within a governance board or steering committee headed by an executive sponsor. This group provides authority on programme funding, purpose and direction.
The programme manager or director manages the programme plan on a day-to-day basis and defines the overall management process. He or she is responsible for the overall coordination and integration of the programme and, ultimately, for meeting the programme objectives.
The change manager would usually have had significant input into the business case and will be tasked with preparing the business for change. An important element of this role will be to align stakeholders' understanding of programme goals and manage customer expectations.
A risk manager should be appointed to define and implement the risk management process. This may typically include oversight of risk identification, analysis and response within each of the component projects, as well as active monitoring of the overall level of risk exposure.
The business analyst specialises in requirements elicitation, analysis and documentation. In Programmes, this role has added significance in coordinating requirements scope across projects, evaluating change requests and performing quality assurance to verify programme deliverables.
Lastly, the programme office manager sets standards for programme and project management practices; provides administrative support in programme planning, resourcing and communications; and consolidates project progress information in support of programme performance analysis.
3. Build a Well-Defined Programme Architecture
The programme architecture is the road map for getting from the as-is to the to-be state. It provides an outline of how the projects within the programme will deliver the capabilities that result in the required benefits. The programme architecture should clearly define the projects within the programme; ensure projects deliver benefits; and define high-level dependencies.
A benefits map extends the architecture further by incorporating a depiction of how the ultimate strategic objectives for the programme will be met and provides a means for identifying and defining the boundaries of each component project. The architecture, therefore, defines the linkages between goals and benefits, and provides some clarity on the emergent component projects, their deliverables and the major functions required to perform the work of the programme.
Many Programmes suffer from a lack of proper alignment at a high level, which inevitably leads to friction and contention across sub-project teams at some point. Establishing a top-down approach to defining the programme architecture early on is the basis for ensuring effective alignment among stakeholders and the implementation team - and, ultimately, for influencing the division, integration and communication of all programme work. The culmination of a well-defined programme architecture is the establishment of summary tasks for each component project, which provides the crucial linkage to subsequent detailed planning.
4. Manage Stakeholder Expectations
Stakeholders represent individuals and organisations whose interests may be affected by the programme outcomes, either positively or negatively. Stakeholders can both impact or be impacted by the execution of a programme. A typical programme stakeholder group might include internal members (programme director, sponsor, governance board, programme office and customers) and external members (government regulatory agencies, consumer groups, environmental groups and customers).
These stakeholders play a critical role in the success of any project or programme. They can influence Programmes, either helping or hindering depending on the benefits or threats they see. The programme manager must understand the position stakeholders may take, the way they may exert their influence and their source of power. This is a key precursor to forging a deep understanding of needs and concerns, addressing any sources of apprehension regarding the programme goals, and ensuring alignment of perspectives on programme objectives.
Generally, stakeholders mostly want to know about the benefits achieved - and, ultimately, this is what the programme is about. Many Programmes neglect to relay sufficient information on benefits realisation. The programme manager, therefore, needs to ensure there is early capture and communication of organisational benefits from the first completed projects onward.
Addressing stakeholder needs while remaining cognizant of the constraints of the programme boundaries often requires dexterity and sensitivity. A fine balance must be sought between managing out-of-scope requirements and expectations and seeking support for the organisational change and its consequences. Effective programme management demands: strong negotiating skills; an ability to manage cross-functional conflict; a properly balanced approach to coping with multiple interests.
5. Adopt Integrated Programme Planning
The heavily composite nature of a programme requires that a strongly integrated approach to planning be adopted in order to properly reflect deliverable, resource and external dependencies. For example, traditional project scheduling techniques alone will not suffice - the programme schedule can only be considered correct when it properly integrates each component project through task-level interfaces. To achieve a detailed programme definition and execution schedule, a number of vital intermediate steps are needed to ensure the plan is both reliable and scalable:
· Define and verify scope roll up from projects to programme
· Identify and define all cross-project interfaces
· Develop the integrated master schedule
Integrated planning begins with a programme charter - a more detailed artifact than the business case that provides high-level programme scope, objectives and constraints, and outlines the projects, the people involved, the funds needed and the processes to be followed. It describes the transition from current to desired future state, along with the costs, benefits and risks in getting there.
The charter provides the foundation for scoping each of the component projects. Boundaries for each project must be defined as unambiguously as possible to avoid both gaps (omitted work) and overlaps (redundant activities). Contentions frequently occur at this stage of the programme plan development and these must be resolved using a robust issue-management approach.
Work breakdown structures (WBS) must then be developed for each project to the lowest appropriate level of detail. Different approaches for organising the WBS should be evaluated to place appropriate focus in progress monitoring and reporting. Preliminary project schedules should then be examined for cross-project interfaces. These interdependencies must then be fully defined, matched and linked to arrive at the detailed, integrated programme master schedule.
6. Use Scenario-Based Execution Simulation
The complexity of most Programmes makes the use of scenario analysis techniques not only valuable but essential. The techniques are key to establishing greater insight into evaluating possible programme outcomes and also maximising credibility with sponsors and governance boards. Two primary methods are advocated: alternative execution strategy assessment and probabilistic forecasting and analysis.
Alternative execution strategy assessment involves re-shaping the detailed integrated master schedule to consider alternative execution approaches. Here, the WBS and schedules may be adjusted to assess a number of changes, such as alternative technical approaches, sourcing approaches, and programme funding scenarios and related programme scoping variations. This helps assess how programme timing, funding, risk and outcomes might be impacted by adopting different strategies, and offers a more definitive assessment than any prior feasibility study.
Probabilistic forecasting and analysis provides crucially important answers to two fundamental questions that a programme manager and steering committee will have: 1) What is the most likely completion date? and 2) How likely are we to finish by the target date?
Advanced schedule simulation techniques provide the answers to these questions with greater confidence than traditional critical path method scheduling, which only provides a single programme schedule solution. Since a range of possible outcomes will always exist, these outcomes, and their likelihood of occurring, are what probabilistic scheduling will reveal. Further, simulations provide a wealth of valuable knowledge on the sensitivities of any milestone to schedule movements, far beyond the level of a standard critical path analysis.
7. Practice Systematic Risk Management
Effective programme risk management should involve a coordinated, holistic approach. The programme risk manager determines and enforces the preferred methods and steps for each project team and ensures that these are adopted continuously throughout the life of the programme:
Risk identification and analysis should be applied at both the programme and the project level. The core programme team concerns itself with the "big picture" at the programme level itself while the project teams focus on perceived risks at the level of their respective project WBS. Even though the program manager is focusing on the programme level, he or she should not be afraid to cancel a project due to lack of good risk management; in fact, good risk management should be considered a key criteria for ongoing assessment. Also, it is important that all risk identification and analysis be performed in groups to avoid individual bias.
Once a list of risks has emerged, it is typically best to prioritise the list so as to focus the development of response strategies on the most severe risks. Response strategies should then be incorporated into the integrated programme master plan in such as way that they may be properly tracked. Care should be taken to evaluate the potentially cascading and ripple effects that any risk or response strategy might have on other projects within the programme.
Finally, decisions may now be made about responding to risk by utilizing the risk reserves that should be included in the programme budget. The amount of reserve will depend upon a range of factors, but chief among these are the level of estimating confidence and the expected value of the risks.
8. Implement the Right Control Processes
According to Gartner, in 2008, three out of four successful $500,000 projects will be planned and tracked with project office support, while three out of four failed projects will not. And, tracking is of crucially greater importance in Programmes than most projects since the consequences of missing targets are more severe, the likelihood of significant problems is greater, and there are simply more things that might go wrong. Some typical areas of concern for programme management include:
· Are project deliverables meeting requirements?
· Are teams adhering to project schedules?
· Are risks, issues and changes being properly identified and managed?
· Are estimates proving reliable?
· Is project cost and benefit tracking effective?
· Are resources and funding sufficient?
· Are scope, time, cost or benefit changes being managed effectively?
The programme office should provide assistance to the projects in the updating of their plans and progress reporting to the programme. Project reports should contain relevant highlight information in a standardised format to help aggregate the information at the programme level. The impact of any risk, issue or change within a component project needs to be recognised as early as possible in order to manage it carefully and guard against any adverse impact across the programme community. Rigorous and systematic scrutiny of the status of programme interfaces must supplement traditional critical path analysis.
Each project must take responsibility for adhering to timely forecasts of delivery and working within the tolerances set by the programme office. This is required especially for outputs supplied to other projects, which will be affected by any slippages against plans. Indeed, scrutiny of all programme interfaces must be a vital element of the programme manager's control strategy. Any likely exceeding of tolerances should be reported as early as possible to the programme level.
9. Develop Achievable Benefits and Requirements
The attainability of programme benefits is directly linked to the achievability of the stipulated requirements. For a programme to have any chance of success, it is vital that both requirements and benefits be realistic; clearly articulated; understood by all stakeholders; accepted and signed off as viable; and supported by a rigorous change management process.
Benefits management is best led by a dedicated change manager who should ensure that clear pathways link outcomes to strategies, events and assumptions. The change manager should also establish agreed-upon benefits-tracking metrics. Without an agreed-upon measurement system in place, disagreements over the level of success of programme accomplishments will endure to the detriment of the entire initiative. It is advisable to introduce a series of regular, formalized quality checks to validate whether programme outputs are properly meeting needs and to hold regular stakeholder reviews and satisfaction surveys.
Requirements management is ideally led by an accomplished business analyst. This critical role must ensure that the front end of the programme and any later projects are consistent with common practices and processes for requirements elicitation and documentation. In addition, the setting of programme phase-gates will provide appropriate solution assessment and validation cycles where conformance to requirements can be gauged in depth.
Lastly, it is essential to include benefits and requirements impact assessments in the scope change management process in order to counter creeping commitments and maintain control.
10. Facilitate Effective Change Management
Aside from implementing rigorous change control procedures as described earlier, effective management of broader change is required since the programme deliverables will typically impact multiple facets of an organisation. Successful programme managers recognise that the appointment of a change manager can be a prerequisite for facilitating widespread understanding and acceptance of the programme goals, solutions and outcomes. A five-step approach is advocated that helps to shape, steer and realise change:
1. Identify need for change 2. Define compelling vision or "to-be" state 3. Choose a change strategy 4. Engage the support of stakeholders 5. Implement change strategy
The need for change is articulated in the business case but should be based on input from multiple key stakeholders and answer questions such as: "What/where is the problem causing pain or potential crisis?" and "What/where" is the untapped opportunity for gain?
Answers to these questions provide the basis for an inspiring change vision. In choosing a change strategy, the change manager must secure organisational readiness for change by conducting environmental assessments to ensure developed solutions will not impose unsustainable cultural stress.
Engaging stakeholder support requires extensive communication. Facilitating unity of understanding in what will change, how the future will look for both the organisation and for individuals, and how employees can contribute to that goal, are all important elements of transition communications. A detailed communication plan should comprise frequent briefings, updates for all appropriate functions and levels, and regular learning review milestones.
Ultimately, a programme can never suffer from excessive support for change. Substantial effort must be devoted to building consensus from the top with meaningful understanding on the rationale for change, agreement and commitment to the nature and consequences of change, and monitoring and refining of the transition process.
Delivering Programme Success in Your Organisation
More than ever, achieving success in implementing strategic Programmes of change demands attention and expertise across a multitude of programme management domains. Programme managers need a combination of strong leadership, managerial, communication and technical skills to execute these 10 vital steps toward programme success.
Mastering these elements requires focus and commitment - on the part of the programme manager and the organisation. To achieve success, you must closely assess your current state by asking the following questions:
> Are you performing the 10 steps described in this paper on your Programmes? If not, what barriers or obstacles get in the way of executing these steps?
> Do your programme managers know they are responsible for these steps?
> Is it clear who actually performs the steps and is responsible for their execution in your organisation? The programe manager needs to ultimately own the steps, but in some cases, he or she may not actually perform the step. So, make sure that if execution doesn't fall on the programme manager, it's communicated to the person who does own it.
> Is their accountability? How will you make sure these steps occur? Or, do you have the steps instilled in your processes in a way that assures they will occur? And, what checks and balances do you have in place to determine when they are not happening?
Adoption of appropriate processes and tools provides the foundation for success. Structured training and resultsoriented workshops can accelerate skills development, knowledge application and programme execution for everyone involved in the programme. Only through action across all 10 elements will a programme be infused with the right enablers to ensure success in governance, benefits management and stakeholder management.
J. LeRoy Ward, PMP, PgMP, is executive vice president of ESI International,where he heads its worldwide training Programmes and international partnerships.
We can help you achieve your personal and organisational goals by offering the right training solution for you, for more information call 020 7017 7100 or email firstname.lastname@example.org or visit ESI's homepage
Copyright ©Projects@Work. This article first appeared in the August 2008 issue of Projects@Work. Reprinted with permission