Project Portfolio Management Framework Part 3 of 6

August 3rd, 2007

Resource and Business Capability Analysis

Many portfolio management methods do a poor job of resource balancing. Projects are evaluated, “Go” decisions are made, but resource implications are often not adequately but more important realistically addressed. Many organisations simply consider individual projects one-at-at-time and on their own merits, with little regard for the impact that one project has on the next. Failure to manage the businesses resource capability leads to pipeline gridlock in which too many projects chase too few resources. Prioritization is one thing; the capacity to deliver on these priorities is another. Therefore before we approve and execute the portfolio it is necessary to match up the project portfolio with the corresponding resource requirements. This stage is crucial to determining the businesses capability to undertake the required work in order meeting the portfolio objectives.

The PPM framework needs to provide PPMT with a controlled and predictable method of monitoring resource and business capability against the strategic planning process in order improve the probability of a business being able to meet targets on time and to budget. Resource capacity is particularly challenging simply because so many organizations are lacking the processes to be able to effectively track how much effort is available for project work, and how much of that effort is already committed to initiatives underway. Before we explore the steps involved it is essential to note that the portfolio mix should not exceed the organization’s resource capacity or capability. One of the central components of PPM is its ability to enable the business to implement an equitable balance between the demand and supply of resources. With the support of the PMO has a project knowledge centre the PPMT is able to collect all the relevant information to update the project portfolio and build supply and demand scenarios that then can be fed back into decision making.

This in turn allows the business to make the right project selections and to allocate resources to the highest-priority activities across groups and organization units.

The business resources can typically achieved by implementing the following step process:

Step1 – Determine Resource Demand and Constraints: The first step looks to understand the resource spread between “Business-As-Usual” activity i.e administration, existing projects and the demands of new projects. Essentail here is rooting out so called “invisible projects” are often buried or masked has routine work and soak-up essential resources.

Therefore key issues within this step include:

a) Identifying existing resource demands and constraints
b) Determining resource requirements for new projects
c) Analysing ratio of resources between existing and new projects

Step2 – Create Resource Supply and Demand Scenarios: The next stage is to create resource allocation scenarios. This includes analysing the impact of cancelling active projects, putting them on hold and anlaysing for example their impact across a 3, 6 and 12 months perod. As well as examining delaying or bringing forward projects, and understanding their overall effect on the businesses capacity.

Key issues within this step include:
a) Creating portfolio variants for different allocations of resources
b) Developing resource redistribution scenarios and analysing there impact on the business
c) Determine the need for addition internal and external resources
d) Defining resource development requirements based on skills requirements

Step3 – Allocate Resources: As a result of scenario analysis, changes are made to the existing allocation of resources across both the portfolio as well as the organisations existing “business-as-usual “ activities. Also essential here is to establish metrics and processes that will allow the business to determine at what point in time there will be insufficient or excess capacity for the project portfolio as a whole.

Key issues within this step include:

1) Determining resource allocation for each project
2) Deciding whether to create additional internal or external capability
3) Ongoing capacity management inorder to provide visbility into long-term resource requirements.

Ongoing, responsive capacity management requires constant access to up-to-the-minute data from all related systems. This allows rapid identification of changes to the project portfolio. It also enables modifications to be simulated in response to deviations and bottlenecks, ensuring that the right decisions are made. The resource and business capability analysis process provides decision support for the following issues:

a) Which projects can be executed with available capacity,
b) Where and how can capacity at one organizational unit be reassigned to another and how can a project portfolio be capacity-optimized?

Next week Portfolio Selection, Prioritization and Authorization

The role of a PMO within PPM process – Part 3/3

August 1st, 2007

Therefore PMO therefore assumes two key roles, depending on which needs of the organisation are being served:

• Tactical: The PMO provides direct support to projects in several areas such as scope management, baseline change management, project scheduling, resource management, cost management and project reviews. The PMO provides the information required for decision making and ensures that the decisions are being carried out.

• Strategic: The PMO supports the PPM framework, which in addition supports project prioritisation, performance management and benefits realisation (see Figure 13). The PPMT intersects with the executive stream, allowing the organisation to make strategic ‘go/kill/hold/fix’ decisions on key projects in the context of managing a balanced portfolio
of investments.

In summary, the PMO is the function responsible for coordinating, planning, overseeing and monitoring an organisation’s multi-project environment. Through the PPM process the PMO enforces executive accountability and transparency by connecting the organisation’s projects to the business’s portfolio strategic decision making stream. The information supplied by the PMO flows directly into the PPMT’s funding, selection, prioritisation and resourcing processes.PMOs are becoming a standard feature within many organisations and are viewed as the operational centre supporting any project within the business. They act as the clearing house for project information and the driving force for project delivery.

The main specific responsibilities of the PMO include:

Project management, control, delivery and alignment:

- monitoring project outcomes and communicating this up stream to the PPMT and down stream to project managers
- increasing communication and coordination across projects
- advising the PPMT on the benefits and status of projects
- advising and reporting on the placement of new and elimination of old projects
- endorsing, advising and supporting project managers
- confirming successful delivery and sign-off at the closure of the projects
- managing resource utilisation across the organisation, matching project needs with specialised skills and availability
- ensuring critical projects are on time and within budget by providing objective accountability and review at every stage, from initiation to closure
- using dashboards to enhance the roles of project and programme managers within the enterprise

Financial accounting:

- assisting project managers with budget control
- maintaining financial status reports on all projects
- analysing interfaces and critical cost dependencies between projects and recommending appropriate action
- maintaining a list of stakeholders and their financial interests

Project management support:

- providing a single point of contact for all project information
- training, coaching, guidance and mentoring
- developing and holding project templates and master copies of all project and programme information
- generating all necessary quality management documentation
- maintaining, controlling and updating documentation
- establishing and maintaining an electronic registry of project information for use by both the PPMT and project managers

Methodologies, standards and metrics:

- guardianship of project methodologies (for example, Prince2), standards and metrics
- compiling reports and collecting information from project reviews
- providing a central, customer focused office to care for the concerns of the client, sponsor and project stakeholders
- providing assistance to the PPMT in selecting and analyzing projects
- establishing consistent practices and standards for programme governance arrangements, including project planning, reporting,
- change control, analysing risks and maintaining and updating the risk register

The role of a PMO within PPM process – Part 2/3

July 23rd, 2007

Programme management is the process of managing multiple, ongoing, interdependent projects. The Programme Management Office (PMO) provides a layer above the project management process, focusing on selecting the best group of programmes, defining them in terms of their constituent
projects and providing an infrastructure whereby projects can be run successfully while leaving the job of delivery to the project management community.The focus of the PMO is to coordinate and communicate on all programmes and projects in the enterprise, as well as to be the knowledge centre with regard to training, leadership, mentoring, best practice, project governance standards, and so on that supports managers in the implementation of the tasks and work packages required to achieve
successful project completion.

The PMO’s role within the business is not only to act as a knowledge centre, but also to help marry project management process with the executive streams by working closely with the PPMT. This relationship is designed to help the business to identify the precise measures that need to be taken in order to turn strategic goals into reality, as well as to determine the key performance indicators that show whether goals are being met.

The PMO provides the necessary overview and coordination to deliver projects on time and on budget by managing and reporting on schedules, risks, costs, quality, scope and resources across all projects. At the heart of a PMO is its relationship with the PPMT, the aim being to enable the business to coordinate and integrate complex multi-project initiatives across an entire enterprise. This partnership between the PMO and the PPMT is there to empower the executive decision making stream with the necessary information to help prioritise and balance project initiatives, justify decisions, measure risk vs return and allocate resources in a way that maximises their impact on the business.

One of the main issues when implementing a PPM process is that different layers of management within the business have their own territorial issues and oversights. As stated earlier, the PPMT consists of executives and senior postholders who are charged with responsibility for making all key decisions that affect the project portfolio.

The PMO provides the bridge that joins the operational stream with the strategic stream. The PMO is a body of senior project stakeholders and managers that has responsibility for managing all the business’s projects from an operational perspective as well reporting back to the PPMT on their outcome.

By centralising overall operational responsibility for all the organisation’s projects in the PMO, a complete picture of project activity can be painted. The PPMT is able to utilise the tactical structure of the PMO to collect all the necessary ‘coal face information’ to manage and evaluate the health of the business’s projects.

The formation of a PMO is not only designed drive top-down accountability; it also supports the complete operational framework for managing a multi-project environment. In effect a PMO is an information repository that provides the visibility needed to understand the health of ongoing projects and the potential impact of planned projects – and ensures that all projects are evaluated in the same manner. Without a PMO ‘knowledge centre’, executives and the PPMT are hindered in their ability to make the necessary collective decisions based on the right information.

10 Undeniable Truths of Project Managment

July 17th, 2007

1. Project Scope Is Not Defined On PowerPoint Slides

2. Project Schedules Do Not a Project Plan Make

3. Projects Are Not Managed From Behind a Spreadsheet

Some project managers secretly want to be statisticians. They love to calculate all of the various metrics pertaining to their project such as the percentages of deliverables completed, tasks currently on schedule, tasks that should have started, of variance from budget, etc. These are all good to know. The problem is that they spend so much time summarizing and restating data in their spreadsheets, they never talk to the team members about how the project is going and what problems they are having. Without that connection with the team, they are not managing so much as they are reporting.

4. No Task Longer Than 80 Hours and Not Shorter Than 40

5. No More Than One Person Responsible For a Task

6. Every Task Generates a Deliverable. No Work for Work’s Sake.

7. Large projects should be broken down into sub-projects (if they have long timeframes)

8. Plan for the Worst

The old saying is “the best laid plans of mice and men often go awry”, and they do. Always think through your risk plans. Even if things are going well, a good PM has to ask “what if?” Remember that for each risk you can think of, come up with a way to reduce the likelihood of it happening (mitigation) and have a Plan B if it does (contingency).

9. Make it Fun

IT projects can be daunting events. Have you ever noticed that there are some project managers that people just don’t want to work for? The Project Tyrant that is always changing things, asking for things at the last minute and making demands of people is someone that is hard to support over the long haul of a project. There will be tense times on any project, but the lead comes from the top. When things are at their worst, if the PM can laugh at himself it will relieve the tension of the entire team.

10. In the End it is People

In the end, the key point to be mindful of is that all of the previous techniques exist for one purpose: to produce results with a team of people. All of the techniques in the world will not produce anything if they are not constantly tuned, adjusted and calibrated for the individuals on your team. People are different and they all respond differently in various situations. The most successful senior managers I have run across in my experience were the ones with a unique respect, passion, appreciation and understanding for people.

The role of a PMO within PPM process – Part 1/3

July 16th, 2007

What is the role of the PMO? What is its relationship with the Project Portfolio Management Process and Project Portfolio Management Team (PPMT) as well as the project management process? How can the true potential of the PMO be realised? A project manager is a very different animal to the programme manager. However, the relationship within the business is designed to be mutually complementary. This is also true of the relationship between the PMO and the PPMT. Delivering complex programmes on time and on budget is a major challenge for any organisation. With diverse but interrelated projects, resources, and processes, conflicts are inevitable and success is often elusive. The biggest challenges facing most organisations today are
having the ability to know which of their projects are in trouble at any given time, and how they will get them back on track. With information and people so widely distributed, the critical ability to check project status and proactively identify problems can be next to non-existent. Moreover this is also compounded by disparate levels of project management knowledge, skills, abilities, techniques and methodologies from one business unit and department to another.

Disparate information and poor communication about project interdependencies typically result in:

• project delays: projects run late and do not deliver the desired results
• no standardised method: typically, many organisations have no centralised or enterprise-wide project management method, resulting in fragmented and ad-hoc compliance to project governance standards and procedures
• resource bottlenecks: key resources are chronically overscheduled and there is no clear method for project managers to get the right people for their projects
• out-of-control costs: redundant projects are occurring in different business lines and are costing the organisation more than estimated
• insufficient information: management has little or no insight into what projects are being undertaken, or how well they are being carried out
• no decision framework: projects are undertaken with little or no analysis, with projects having a strong champion or determined evangelist driving other possible investments out of consideration

Therefore businesses that want to improve project outcomes as well as provide critical project information for executives, or institute an analytical project decision process, are turning to the creation of a PMO – a means of managing projects within an enterprise environment.