Monday

Tag Archives: Program Manager

If you screw-up, own-up

One of the traits that strong leaders and credible advisers have is the willingness to ‘own up’ to mistakes they’ve made.  No one operating effectively as a project or program manager, or for that matter any type of manager making decisions can expect to be correct 100% of the time.

If you do something new some mistakes are inevitable. If you accept risks, some negative outcomes are inevitable. And time pressures increase the probability of error. And given project management is all about accepting and managing risks to create a ‘new’ product service or result under time and cost pressures – we probably have more opportunity to ‘get it wrong’ than most.

The generally accepted way to deal with ‘your mistake is:

  • Acknowledge it (“my mistake”)
  • Make restitution if needed (eg apologise)
  • Learn from it
  • Move on, only people who have never made anything have never made a mistake.

Conversely if someone makes a mistake involving you look for the best outcome rather than blame of revenge. We have discussed these concepts in a couple of posts:

/2011/10/01/mistakes/

/2008/12/13/learning-from-your-mistakes/

What is rare is a really good example of the basic steps outlined above being implemented.  This changed with a publication on page one of yesterday’s Age (also reported in the Sydney Morning Herald). What could have been a bitter and dragged out defamation case – you probably cannot be more insulting these days than incorrectly accusing a Muslim of being a terrorist – both The Age and the aggrieve person applied common sense and resolved the issue in a way that would appear to have left everyone ‘feeling good’ and with a sense of closure, not to mention thousands of their readers.

If you missed the item, you can read the story at: http://www.smh.com.au/national/fairfax-media-says-sorry-20150303-13ttpd.html

Mistakes are inevitable – strong people deal with them in an appropriate way, The Age’s example being exemplary.  This is a salient lesson we can all learn from.

The Standard for Program Management—Third Edition

The most noticeable thing about the new Standard for Program Management – Third Edition is that is has gone on a major diet! The 2nd Edition was 271 page long (plus appendix), the 3rd Edition is less than half the size at 106 pages plus appendix. Unfortunately the price has not moved in the same direction.

The Standard still provides a detailed understanding of program management and promotes efficient and effective communication and coordination among various project management groups. The major updates include:

  • Program Life Cycle has been assigned its own chapter for the third edition to provide the details of the unique set of elements that makes up the program management phase.
  • The third edition highlights the full scope of program management and clarifies the supporting processes that complete the delivery of programs in the organizational setting.
  • A more detailed definition of program management within an organization is provided, including the fundamental differences between project management and program management.

The major focus of the revision seems to be removing a lot of the ‘project management’ information that is found in the PMBOK® Guide and focusing on the role of program management in organisations, the unique characteristics of program management work and the role of the program manager. A shift from process to principle, that is aligned with the Program Management Role Delineation Study that forms the basis for the PgMP examination.

The framework in the Third Edition is:

  • Introduction
  • Program Management Performance Domains
  • Program Strategy Alignment
  • Program Benefits Management
  • Program Stakeholder Engagement
  • Program Governance
  • Program Life Cycle Management
  • Program Management Supporting Processes

The relationship between the Program Management Performance Domains that makes up the bulk of the standard is illustrated below.

In addition to the core standard, Appendix X4 on Program Management Competencies, and X5 on Program Management Artefacts are very succinct and useful.

A couple of shortcomings in this version of the standard are firstly the limited recognition of the different type of program that organisations run. The PMI standard is very much centred on the ‘strategic program’ defined in the GAPPS typology discussed in our White Paper Defining Program Types. In particular the GAPPS ‘Operational Program’ typology has been largely ignored in the PMI standard.

The other is the classic confusion between the Enterprise level executive management responsibilities that are critical for the support and oversight of the work of the Program Manager and Organisational Governance, typical of documentation produced by working managers. What the standard describes as ‘governance’ is the critical management responsibilities of senior executives to adequately support oversight and manage the process of ‘program management’. Governance is the process of oversighting the whole management system, that is performed by the ‘governing body’ which is the Board of Directors in most commercial organisations and their equivalent in other types of organisation – governors govern, managers manage! For more on this critical distinction see: WP1084 Governance Systems & Management Systems. The contents of the ‘governance’ section are good, just miss-labelled.

Summary
Overall this is a significantly improved standard – a lot of duplication and redundancy has been removed, and the key functions and processes of program management and what organisations need to do at the enterprise level to support programs are well though through and laid out. This new standard is available in Australia from: http://www.mosaicprojects.com.au/Books.html#PMI

PgMP Credential Update

As at the 1st January 2012 the PgMP exam will become much more difficult! The new exam reflects a substantial refinement to the role of a Program Management Professional. The current exam is focused on 5 domains (Defining, Initiating, Planning, Executing and Closing the Program) which will be assembled under new Domain 2 “Program Life Cycle” as sub-domains with new domains, 1, 3, 4 and 5 added. Out of the total of 72 tasks in the new exam, 26 are new or have major revisions, and another 26 have minor changes. The structure of the new exam is:

1. Strategic Program Management
2. Program Life Cycle
     • Defining the Program
     • Initiating the Program
     • Planning the Program
     • Executing the Program
     • Controlling the Program
     • Closing the Program
3. Benefits Management
4. Stakeholder Management
5. Governance

The good news is people who pass their PgMP under the current regime maintain their PgMP status after the 1st January. There is no requirement to re-sit or upgrade an existing credential.

So if you were thinking that obtaining your PgMP would be a good career enhancing move, the smart option would be to pass your exam this year! To find out more about the changes and the options for becoming a PgMP this year, see: http://www.mosaicprojects.com.au/Training-PgMP.html

PMI PgMP Examination Update

PMI’s Program Management Professional examination will be changing in 2012. PMI have recently completed an updated Role Delineation Study (RDS) focused on the work of Program Managers. The RDS has produced an revised description of the professional role of a PgMP, based on feedback from more than 1,100 program managers from 79 countries, 119 of whom held the PgMP credential.

The new RDS restructures the Program Management Performance Domains and Tasks and as a consequence, the three evaluations for the PgMP credential, the panel review, the examination, and the multi-rater assessment, are being updated to reflect these changes.

PMI are in the process of finalising these changes with a targeted release of the new examination globally on 1 January 2012.

Program Managers who are considering taking the exam in the near term are encouraged to complete their PgMP examination in the next few months using our current resources. For more information on the PgMP course see: http://www.mosaicprojects.com.au/Training-PgM.html. This course is available world wide via our PgMP One-on-One Exam Prep Course.

Based on the updated PgMP Examination Content Outline, that will be released by PMI in the coming weeks, we will be updating our training and examination preparation courses. Our updated courses will be available in Q3 ready for the 2012 exam change.

A Project Manager’s Mangers

Projects are a very effective way of creating the new products, services or results required by organisations to effect change. The concept of a project is well understood, as are the roles and responsibilities of the project manager. A range of international standards exist defining project management processes, with the PMBOK® Guide being the most widely distributed. Despite the range of standards, there is general agreement and consistency across cultures and languages. But projects are only the building blocks of organisational change and improvement, other management structures determine what projects should be undertaken and how their outputs will be used to create beneficial outcomes and value.

The purpose of this post is to look at the three main management processes that govern the project processes; Portfolio management, Program management and the role of Project Directors as the managers of project managers.

Portfolio management
Portfolio management is, or should be, a collective process undertaken by the senior managers within an organisation to select the best mix of projects and programs to achieve the organisations short, medium and long term objectives. Every organisation is constrained by the available funding, the available resources and its inherent capabilities; so for every project selected or continued many others are rejected.

This process defines the organisation for the future; the correct mix keeps the organisation functioning in the present, builds on existing strengths for the mid-term and creates new opportunities for the future. Taking a too conservative and risk adverse stance guarantees others will seize the future and the organisation will fade into insignificance or failure. Taking on too many risks can destroy the business in the short term.

These decisions are too important to delegate to a ‘portfolio manager’; they have to be the responsibility of the chief executive and the senior management group. However, making this type of decision needs viable and reliable data, both on current projects and on the evolving environment the organisation operates within.

Effective strategic planning processes at the executive level should lay out the environment and opportunities. The role of an effective Portfolio Manager should be to provide these decision makers with recommendations and suggestions based on accurate and meaningful data on the status of current and proposed projects and programs. In this context, meaningful data refers firstly to the alignment of the projects and programs to the organisations strategic objectives and secondly the value contribution expected from the project’s outputs; on time and/or on budget are largely irrelevant other than to appreciate the impact of any variance on the value currently expected as a consequence of effectively deploying the project’s outputs.

Portfolio management requires an effective PMO structure to gather analyse and manage the information flows from current and proposed projects and programs. However, given the executive decision making role the Portfolio Manager supports, within an ethical governance framework, it is probably inappropriate for the same person to be directly involved in the management of the projects and programs.

From the perspective of a project or program manager, whilst the Portfolio Manager should have little or no input to the day-to-day running of the work, he or she is a key stakeholder and the critical aspect of managing the relationship is understanding the current value proposition for your project or program and making sure this is communicated effectively.
[for more on Portfolio Management see: White Paper1017 ]

Program management
Programs are created to create a business benefit. Whilst there are several different types of program they all initiate and run multiple projects to obtain benefits that would not be achievable if the projects were managed in isolation. Programs are quite different to large projects. Programs typically create multiple deliverables that achieve a range of benefits desired by the organisation. Whilst not as well defined a project, there is a strong consensus world-wide as to the role of the program manager and the purpose of programs.

If a project is part of a program, the Program Manager is the project managers direct line manager and will have significant involvement in the running of the project. Also, as the project is an integral part of the program, the project manager will be a key player in the program manager’s team. This stakeholder relationship is probably the most important for the project manager to maintain as is the corresponding relationships between the program manager and her project managers.
[for more on program types see: White Paper 1022 ]

Project Director
The role of the Project Director has been somewhat overshadowed by the emergence of portfolio and program management; this is unfortunate. Project directors are managers of project managers. This role should be focused in two areas, firstly providing oversight and governance to projects that are outside of programs (this is probably the majority), secondly providing management input to the organisation’s project managers to help them develop and grow.

PMI recognise the role as the ‘Manager of Project Managers’ in composite and strong matrix organisations. AIPM as a ‘Certified Practising Project Director’ in their competency standards and RegPM credential structure. The role of the Project Director can be subsumed into an appropriate PMO as long as the PMO is focused on driving value and creating excellence.

Unfortunately at the moment, there is very little focus on this aspect of developing project management capabilities within an organisation. Unless there is a renewed focus on developing project managers and project management capabilities within an organisation it will rapidly lose any competitive advantage. Buying in ‘talent’ from elsewhere will become increasingly expensive and is largely counter-productive to the development of an effective corporate culture and enhanced organisational project management maturity.

Where Project Directors exist, they are another important stakeholder for the project manager to work with.

Advising upwards
Each of the managers defined above are important stakeholders and the project manager needs to effectively manage the relationships if their project is to be successful and the PM’s career enhanced. My new book, Advising Upwards: A Framework for Understanding and Engaging Senior Management Stakeholders is focused on the skills needed to build and maintain robust relationships, focused on engaging the support of senior executives, understanding their expectations and managing them through targeted communication. For more on the book and the expected publication date, see: Book Outline.

Summary
The three distinct roles defined above are critically important to the development of effective project management practices within an organisation. However, it is important to note each role is distinctly different and should be separated in a mature organisation, even if they are incorporated into an overall PMO structure.

PMI’s OPM3 assessment processes can help develop an organisations Project, Program and Portfolio management maturity see: more on OPM3

The roles and functions of various types of PMO are discussed in White Paper 1034