LATEST POSTS

This website is open to anyone interested in Project Portfolio Management (PPM). The site will give you access to material covering latest industry thought leadership, PPM methodologies and techniques, PPM related business challenges, solution / product material, case studies, white papers, book reviews and comments from our PPM experts.

Kick start the PPM Process Part 3 of 9

Requirements capture

Once an understanding of the business has been developed, the processes and demands can be mapped onto the requirements process. It is at this initial stage that high-level stakeholders should be brought into the process. The requirements capture process shoudl itself be high-level, with a more detailed analysis done once a better understanding of what is on offer has been developed. The requirements capture process should involve the following key steps:

1) Determine requirements scope and objectives
2) Decide on the requirements gathering model or methodology
3) Identify the key project stakeholders
4) Build the requirements model
5) Gather project stakeholder needs and information
6) Create a requirements specification, consisting of:
     - business and process requirements
     - people and resources requirements
     - capabilities and functional requirements
     - review infrastructure/IT architecture
7) Test, review and verify the requirements specification
8)Build the requirements into an RFI

In order to ensure best practice the following key considerations should be factored in:

  • ‘Translate’ technical language into business language and vice versa
  • Ensure stakeholder involvement at all levels of the process
  • Draft clear and concise written documentation for all types of stakeholders
  • Ensure that the requirements are quanitifable and measureable
  • Ensure that the requirements are clearly defined in the vision and scope document
  • Prioritise requirements by their relevance importance
  • Verify the completeness of the requirements by formally inspecting the documents generated
  • Identify and remove any software functionality and process steps that do not meet any of the business objectives
  • Establish and enforce a clear and realistic process for change management
  • Analyse risks to avoid unforseen complexities and slippages

The requirements should then be used in a preliminary request for information (RFI), typically sent to a selection of consultants and software vendors. Once the consultants and vendors have demonstrated their ability to meet a broad range of needs (any that do not meet the basics can be removed, leaving a shortlist) then the next stage is to further define the requirements in order to build a solid business case. While moving forward with the selection process there are a number of things to consider both concerning the business and while reviewing the vendors. Each vendor will take a slightly different angle on the processes and solution for implementation, which will generate value in different areas of the business. Reviewing where the biggest issues lie and who is best suited to delivering on these issues will aid in reducing the shortlist further. Without the understanding and evidence of the business case and ROI, a vendor selection many not be possible. Allowing each vendor to put forward information to gain the buy-in of the stakeholders will reduce the probability of failure later in the project.

Comments off

Kick start the PPM Process Part 2 of 9

Readiness Assessment

When implementing a PPM process it is best to keep in mind the following key questions:

  • Executive sponsorship: Are we going to get executive support to implement a Project Portfolio Management process? Will we get adequate funding, people and time to implement this?
  • Culture and organisation structure: How flexible are the staff, can they change their existing mind-set as well as business processes?
  • Project management and business processes: How do we tie our strategic objective to project deliverables, and what will be the impact of PPM on our existing business processes and project management infrastructure?
  • Metrics and performance criteria: Have we established realistic, measurable performance criteria? What will be our ROI and ROO models?
  • Quick wins and credibility: How do we ensure that we get quick wins and quick ROI? How do we ensure that PPM is taken seriously as a change management project? Are our resources going to provide us with the right inputs to go into the PPM infrastructure?
  • PPM staff and experts: Will we have internal or external PPM experts who can manage the whole process of PPM evolution in the organisation, that is, selecting a PPM vendor, establishing success criteria, taking alternative actions if PPM implementation does not go as planned, and monitoring vendor artefacts and processes?
  • Technology: Are our staff technically minded enough to use the software to its utmost capacity?

Comments

Kick start the PPM Process Part 1 of 9

Where to deploy PPM

Having understood the relevant issues that need to be addressed in order to start organising the business for PPM, we now need to translate this into reality.

Determining the location of the business’s ‘domain’, or in other words, where to deploy the initial PPM process, is critical. Depending on your level of project management maturity, the higher up the organisation the process is to be deployed, the more challenging its implementation will be. The proof-of-benefit (PoB) process discussed later within the chapter articulates the need to prove the initial ROI at a more tactical level within the business, typically at the unit or departmental level. The rationale is to enable the business to construct, test and model the PPM process within a low risk environment as well as understand the change management issues confronting the organisation. Beyond this, the business case built around the PoB is deisgned to enable the business to roll out the PPM process to other parts of the business.

To de-risk the process of organising and deploying a PPM solution, it is essential to deal with ‘chunks’ of activity that prove the value of the solution and process from one stage to the next. Very rarely will a business have all the necessary internal skills to deploy a PPM process. Therefore, to deliver successful PPM and also to strengthen any exisiting in-house expertise, it is recommended that the organisation be in position to recruit outside help in the form of professional consultancy services and software application vendors. We will outline the necessary steps involved in recruiting outside expertise, then we will go into how the business can kick-start the process.

The main areas for consideration include:

a) readiness assessment
b) requirements capture
c) vendor selection process
d) business case considerations
e) the health check
f) measuring the return on investment (ROI) and return on opportunity (ROO)
g) establishing proof-of-benefit (PoB)
h) building a risk management framework.

Understanding the business case through to rollout within the enterprise requires that a number of stages to be followed. Developing an ROI model, understanding the requirements, processes and demands involved, then putting in place a PoB all count as part of the due diligence needed for a successful implementation.

A the process progresses more detail is added to the business case, as when vendors are selected and a roadmap put in place the ROI model becomes clearer, scope changes, opportunities arise or new initiatives are derived from the initial idea.

Next week, we will provide more detail on each area for consideration in the above list.

Comments off

Project Portfolio Management Framework Part 5 of 6

Portfolio, Execution & Monitoring 

Not all projects make the grade and many need to be eliminated even after the portfolio has been approved, because:

a) The projects concerned do not provide sufficient value and are no longer aligned with the business’s objectives.
b) Projects with a higher urgency have been proposed, resulting in a delay to or termination of current projects.
c) A project has been rescoped and integrated within another.
d) Technology has changed, negating the benefits of a planned project.

With only a small percentage of the proposed projects approved and executed, it is crucial that they succeed. Since the business is changing throughout the year, there will also be ongoing changes to the portfolio. This includes the addition of new projects and the elimination of old. This ongoing process of replanning and rebalancing the work, based on changing business needs, is also a part of the portfolio management execution and monitoring process. Portfolio management is therefore more than a one-time event that is performed once a year during your business planning phase. It is a contiual, iterative process that needs ongoing monitoring and course correction. It is essential that the PPMT take proactive steps to resolve problems and keep projects on track by:

a) correcting overlaps and redundancies
b) reviewing and resolving issues and problems
c) monitoring project spending and adjusting budgets
d) monitoring and mitigating project risks
e) managing resource conflicts sch as supply and demand shortfalls
f) reassessing the timing and duration of projects

The PPM selection and prioritisation process is easily emasculated if the portfolio is not actively managed. With projects straying over time, over budget and with business goals shifting and evolving, even originally well conceived projects rapidly become misaligned. However, misalignment must not be feared; it is in fact a natural and expected outcome. The real success of PPM lies in the ability of the PPMT to identify this misalignment and take corrective action. The PPMT must be able to make objective ‘go/kill/hold/fix’ decisions and be able to recognise that a dramatic change in business priorities may eliminate the need for a project, requiring quick project terminatio. As stated earlier, management of the portfolio includes managing the resources, proactively communicating what is going on, reviewing and replanning the remaining work on a regular basis and measuring the results. If new projects are added to the portfolio it will mean that other, previously authorised projects will need either to be eliminated or put on hold. With the help of the PMO, the PPMT needs to document and track individual projects and impelment a course correction process to ensure that the portfolio as a whole accomplishes its objective.

The typical steps involved in executing and monitoring the portfolio include:

Step 1: Gathering project portfolio information
a) collective individual project score cards
b) building a consolidated portfolio score card
c) collecting  project and portfolio resource plans including shortfalls and new demands
d) building a detailed project status report
e) building a detailed portfolio status report

Step 2: Measuring and analysing the project portfolio
a) measuring the performance of ongoing projects
b) measuring the success of completed projects
c) measuring interdependencies between projects
d) measuring overall business value and alignment
e) determining an inventory of projects for portfolio course correction changes

Step 3: Analysing the impact of changes to the project portfolio
a) analysing the impact of projects that may be cancelled
b) analysing the impact of newly identified projects
c) analysing the impact of current projects not achieving objectives
d) analysing the impact of projects that have changed their scope

Step 4: Reviewing portfolio changes and reforecasting
a) filtering new projects against the existing project portfolio
b) reviewing current and new portfolio goals and objectives
c) ensuring individual project business cases are revalidated and aligned with these objectives
d) ranking projects against revised priorities
e) updating the project inventory
f) modelling resource scenarios and analysing the overall impact on the business
g) selecting scenarios and updating the resource schedule

Step 5: Communicating and implementing portfolio changes
a) revalidating business cases for existing authorised projects
b) revalidating business cases for newly authorised projects
c) issuing a new project portfolio review
d) providing guidance on changes to portfolio work
e) communicating with project stakeholders
f) agreeing a timeframe for the next portfolio review
g) making ‘go/kill/hold/fix’ decisions

Being able to take corrective action on projects is a key component of PPM. If a project is not meeting its objectives, it is crucial to identify the root cause, develop an action plan, and then monitor and track to ensure the action is implemented and the issue is resolved. The PPMT must have the ability to intimately understand how projects in the portfolio relate to different business goals and the ramifications if either projects or business goals change. The PPMT needs to track trends and anticipate new opportunities and threats so that project stakeholders can implement measures to avoid misalignment.

Comments off

Project Portfolio Management Framework Part 4 of 6

Portfolio selection, prioritisation and authorisation

One of the most significant challenges of PPM is to understand how the portfolio of projects is selected, prioritised and approved. The primary objectives are twofold:

a) to select and prioritise projects to deliver the highest value
b) to ensure that there is balance in the mix of projects

It is essential that priorities be based on both individual project benefits and the overall impact of the project portfolio. Every project will be treated differently, with some flying through the selection and prioritisation process and others that simply get bogged down.

The selection, prioritisation and approval process will allow the business to address the following key issues:

a) documenting a detailed inventory of projects
b) developing a value ranking for each project against tactical criteria and strategic objectives
c) analysing and identifying project risks vs benefits
d) developing an idea of an optimum or acceptable size of the project pipeline

The project portfolio comprises projects that offer widely differing value. Projects vary by their short and long term benefit, their synergy with corporate goals and their level of investment and anticipated payback. The business needs to develop selection, prioritisation and approval processes by which it is able to evaluate projects according to their health, cost and strategic contribution to the organisation over the short, medium and long term. This part of the PPM framework process brings all the work involved together for review and scrutiny. Projects that do not surface as a part of the process will not have a chance to make it into the final list of authorised work.

The key steps involved within the selection, prioritisation and approval are highlighted in the sub-sections which follow.

Building a project registry

During the gap analysis phase the business builds up a list of projects. This is continued in the selection and prioritisation process in which the business builds up a project registry that allows it to determine the overall complexity and challenge of the portfolio. In other words, the processsets out to answer these questions:

a) Is the project worth doing?
b) What is achievable?
c) Is there sufficient capability and capacity to do this?
d) What is the impact on the business?
e) What are the relative benefits of each programme/project?

Project value: scoring and prioritising

Determining a value for a given project is a crucial step. There is no single definition of the ‘right’ project; however, the project value must be superior to that offered by other projects. The scoring criteria used to select and prioritise projects will however be customised by the business that is implementing the PPM process. The methods that an organisation uses have a big impact not only on the projects that get chosen but also on the projects that get proposed and how they get prioritised. We now briefly explore some of the methods that are used to score and prioritise projects.

Balanced score carding methods
The balanced score card was developed in the early 1990s by Drs Robert Kaplan and David Norton of Harvard Business School. This method enables organisations to clarify their vision and strategy and translate them into action. It provides feedback around both internal business processes and external outcomes in order to continuously improve strategic performance and results. When fully deployed, the balanced score card transforms strategic planning from an academic exercise into the nerve centre of an enterprise. The majority of currently available portoflio management software tools provide the capability for defining both financial and non-financial metrics.

Earned value analysis (EVA)
Earned value analysis is a measurement and management technique that integrated technical performance requirements and resource planning with schedules, while taking risk into consideration.

In other words, EVA is a management technique that relates resource planning to schedules and to technical cost and schedule requirements. All work is planned , budgeted, and scheduled in time phased ‘planned value’ increments, constituting a cost and schedule measurement baseline.

Earned value analysis also provides an objective measurement of how much work has been accomplished on a project. Using the EVA process, the management team can readily compare how much work has actually been completed against the amount of work it was planned to accomplish. Again, all work is planned, budgeted, and scheduled in time phased ‘planned value’ increments, constituting a performance measurement baseline.

Net present value (NPV)
The net present value of an investment (in this context, a project) is the difference between the sum of the discounted cash flows which are expected from the investment, and the amount which is initially invested. NPV is an effective way of expressing how much value a long term project investment will result in, and it has become an industry standard method. However, there are some limitations to NPV measurement:

a) Although it is widely used for making investment decisions, it does not account for flexibility or uncertainity after the project decision has been made.
b) NPV is unable to deal with intangible benefits. This inability decreases its usefulness for handling strategic issues and projects.

Cost/benefit analysis (CBA)
Cost/benefit analysis is the weighing-scale approach to decision making. All the positive elements (cashflows and other intangible benefits) are put on one side of the balance and all the negative elements (the costs and disadvantages) are put on the other. Whichever weighs the heavier wins. However, it can bring with it mistakes and problems:

a) A frequently made mistake in the CBA method is to use non-discounted amounts for calculating the costs and benefits.
b) Caution should be exercised with people who claim that ‘if you can’t measure it does not exist/has no value’.
c) Especially in more strategic investments, frequently the intangible benefits clearly outweigh the financial benefits.
d) Risk must often be considered as a factor in making the decision.

Other scoring and prioritisation models
Other types of models applicable to project scoring and prioritisation, as well as techniques employed to make ‘go/kill/hold/fix’ decisions include:

a) expected commercial value (ECV)
b) productivity index (PI)
c) strategic buckets method
d) risk-reward bubble diagram

For a full breakdown of scoring methods we recommend the excellent White Paper series written by Drs R Cooper and S Edgett of Stage Gate.

Identifying and measuring project risks

Every project has risks, so it is essential to identify mitigation procedures and contingenices. By identifying project risks, those managing  the execution process are given advance warning of problems that might arise and are able to put in place adjustment steps. For example, the risks of implementing a multi-year, multinational project, complete with major process redesign, may be quite significant. The combination of project value and risk assessment allows the portfolio to be selected in a meaningful way, and enables the PPMT to compare and prioritise competing proposals.

Key risk variables include:

a) project interdependencies within the portfolio
b) resource capacity/capability vis-a-vis demand
c) changes in business strategy vis-a-vis operational activities
d) changes in business processes that conflict with the PPM process
e) governance risk in relation to board and management performance with regard to ethics, community stewardship, and company reputation
f) strategic risks resulting from errors in strategy, such as chosing a technology that can’t be made to work
g) operational risks, including those resulting from poor implementation, or process problems such as those of production and distriution
h) market risks, including in relation to competition, foreign exchange and commodity markets, interest rates, liquidity and credit
i) legal risks, arising from statutory and regulatory obligations, including contract risks and litigation brought against the organisation

Identifying portfolio risks starts with an evaluation of the specific project portfolio environment. What business decision criteria have been established? What working assumptions regarding the organisation’s current business processes and decision points might increase risk for the portfolio? Managers should refine this evaluation iteratively, as they plan, assess and manage their portfolio.

Prioritising. balancing and approving the project pipeline

By creating a ‘value proposition’ for each project and then evaluating projects according to their health, cost and strategic contribution to the organisation over the short and long term, the business is able to build a realistic picture of the project pipeline. Understanding project value and risk enables the business to construct a portfolio that is balanced. For example, high value projects are clearly the most sought after, but their risks, if too high, may dilute their attractiveness. Conservative projects may quell fears of losing an investment, but if the returns are too low, they may undermine the company’s ‘future state’ vision.

It is essential to eliminate overlapping and redundant projects and select the most value-producing projects for execution, ensuring that funds are directed towards the most deserving initiatives. However, it is also important to reorganise that the project portfolio will be comprised of projects that offer widely differing values but collectively strive to achieve the overall strategic objectives. Projects within the portfolio will have varying short and long term benefits, specifically as regards their synergy with corporate goals, and their level of investment and anticipated payback.

Use of scoring methods as outlined above will enable the PPMT to select clear criteria for how projects are to be prioritised. For example, the criteria need to include:

a) support for strategic goals
b) short and long term value to the business
c) risk/return/future payoffs
d) resource demand and impace
e) financial impact
f) timescale

The criteria should be defined, understood and able to be evaluated on a consistent basis form project to project. The prioritisation criteria therefore focus on both tangible and intangible benefits, allowing the PPMT to accurately measure the value of the business’s projects, and determine their long term strategic orientation as well as their operational impact. Prioritisation should aggregate new project ideas and categorise existing projects as mission-critical, highly desirable or desirable in order to compare their value and level of importance to the business. There are huge differences between projects, yet too often we see a failure to recognise the differences and handle each accordingly. Types of categorisation are:

a) Tactical projects deliver competitive advantage today. They have low risk, medium-skill requirements and deliver on the existing business plan.
b) Administrative projects deliver on currently promised service levels and support existing strategic projects. By their nature, they are low risk, low-ROI projects requiring moderate skills.
c) Strategic projects deliver competitive advantage in the future. They have high risk, high-skill requirements and look to reduce the gap between the business’s current state and its future vision.
d) Innovation projects are smaller, experimental projects that may deliver possible competitive advantage tomorrow. They are usually high risk and often require resources that the organisation does not yet possess.
e) Future vision projects are contingent upon strategic and innovation projects. These projects have a high risk and high-skill contingency.

Project types can also be categorised by level of importance, for example:

a) mission-critical projects are essential to successful delivery. If the project is not successful there are major implications for the business.
b) Highly desirable projects are important but not essential. If the project is not successful there are serious (but not major) implications.
c) Desirable projects are all those that do not meet the mission-critical or highly desirable criteria.

The approval step is where you determine the actual work to be funded. When this has been approved the projects concerned will then be included within the final portfolio plan. It is important to remeber that the business will never have enough funding to cover all of the proposed work and that not all of the projects prioritised will be approved. After projects have been categorised, prioritised, allocated funding, and resourced, the portfolio plan is ready to be approved and should be published to the business. It is essential to publish this plan at every level within the business so that the individual stakeholders understand the importance of what they are working on and its strategic value to the business. Once the portfolio plan is in place the PPMT and the PMO manage its delivery. The PMO feeds back metrics such as costs, risk, schedules and milestones to the PPMT. The PPMT continually reassesses project performance against strategic objectives and repriorities, adding new and terminating old projects where necessary. The PPMT also provides two-way feedback with executives, ensuring the planning cycle remains on track and aligned with the business’s objectives.

Next week, Portfolio execution and monitoring

Comments off

« Previous entries · Next entries »