Tag Archives: Benefits Realization

The maturing or ‘agile’

kitten-yogaA deliberately provocative article on Linked-In asks the question is ‘Agile Dead?’; a discussion on how various aspects ‘agile’ invented by different individuals and groups are fading from prominence follows.  Agile is not my area of expertise but the article seems designed to generate attention without really saying anything new.

What the article did prompt in my thinking was the question ‘What is agile?’. Concepts vary from:

  • The Agile Manifesto (which is basically 101 common sense) created to overcome the failures of rigid IT development that required a 100% complete fully detailed plan before people really knew what the problem was (often referred to as ‘waterfall’ development but nothing like the original ideas in the waterfall concept).
  • Through to the agile anarchist community who’s mantra seems to be ‘trust us all of our teams are above average’ and we will make you really nice software without any discipline (a concept that ignores the mathematical fact that 50% of any group have to be below average….).
  • Then there are all of the various ‘agile’ methods from ‘Scrum’ to ‘XP’.

Ergo ‘Agile’ or ‘agile’ can mean virtually anything to anyone.  In contrast to all of these specific variants, I would suggest at its root ‘agile’ is a concept or philosophy rather than a methodology or process; useful philosophies rarely ‘die’.

What is emerging I believe is a gradual understanding that the false concepts of ‘command and control[1] and ‘certainty, based on a fully detailed plan[2] are slowly disappearing from management thinking (although there are still plenty of recalcitrant ‘fossils’ embedded in far too many management structures) – detailed planning months or years in advance of the work, done at a time where the work is imprecisely understood cannot control an uncertain future regardless of contract conditions and the exhortation of management. These ideas are slowly being replaced by an adaptive approach to projects that engages stakeholders and focuses on actually achieving the stakeholder’s objectives and realising benefits, ie, an ‘agile’ approach.

Every project and every project management system can benefit from some elements of ‘agile’ (which overlaps with many other concepts such as ‘light’, ‘lean’, and ‘last planner’. The key tenets seem to be:

  • involve your stakeholders,
  • trust your team,
  • don’t waste time planning in detail things you don’t have detailed knowledge of[3],
  • adapt to changing circumstances, and
  • wherever possible avoid a ‘big bang’ approach – iterative and incremental developments mitigate the risk of catastrophic failure.

The agile manifesto certainly highlighted these important concepts but it did not invent them. These elements of fundamental common sense are ignored in far too many situations. What the agile manifesto and the subsequent changes in attitude have done is refocus on the importance of people and relationships in any project.

On the ‘Agile front’, many of the ridiculous excesses promoted by consultants and experts are certainly fading into obscurity. Executives are learning that ‘agile’ is not a cure all ‘silver bullet’ it needs pragmatic management and proper planning the same as everything else, it just the way planning and managing is done that differs; for more on this see: http://www.mosaicprojects.com.au/PDF_Papers/P109_Thoughts_on_Agile.pdf

Certainly there has been a realisation that the agile anarchist’s concept of ‘trust us’ (and their abandonment of any pretence of strategic planning and documentation) really does not work. An appropriate degree of planning, coordination and documentation are essential to achieve success, particularly on larger projects and in the longer term when the inevitable updates and maintenance cut in.

In summary, if ‘agile’ is a philosophy that prioritises people over rigid process, and it will change and adapt over time; it’s not ‘dead’ but it is evolving into a pragmatic management process. Certainly some of the narrowly defined concepts and methodologies branded as ‘agile’ are failing and being abandoned as ‘passing fads’ and new adaptations are emerging, but that’s normal. The core underpinnings of the original Agile Manifesto are still alive and well.

___________________

[1] In the 1950’s Peter Drucker identified the need for a new way of managing ‘knowledge work’, see: http://www.mosaicprojects.com.au/PDF_Papers/P070_A_Simple_View_of_Complexity.pdf

[2] “All models are wrong, but some are useful” (Prof. George E.P. Box), and every estimate used in the plan is wrong to a greater or lesser degree, see: http://www.mosaicprojects.com.au/WhitePapers/WP1051_Cost_Estimating.pdf

[3] For more on ‘rolling wave’ planning see: http://www.mosaicprojects.com.au/WhitePapers/WP1060_Rolling_Wave.pdf

The Shergold Report calls for better governance and better project controls!

Shergold2The recently released report by Professor Peter Shergold, ‘Learning from Failure: Why large government policy initiatives have gone so badly wrong in the past and how the chances of success in the future can be improved’ (the Shergold Report), sets out a framework designed to improve the delivery of major Australian Government programs.  But the framework is not limited to government; the concepts can be usefully applied by any organisation seeking to initiate a major program of works.

The report focuses on making practical recommendations to enhance the capacity of the Australian Government to:

  1. Design and implement large public programmes and projects;
  2. Develop robust and effective governance and accountability arrangements for such programmes and projects;
  3. Understand the broader environment in which programmes and policies are designed and implemented;
  4. Identify, understand and manage risks; and
  5. Provide accurate, timely, clear and robust advice to ministers and within the APS.

Substitute ‘organisation’ for ‘Australian Government’ and ‘senior stakeholders and governors’ for ‘ministers and within the APS’ and the value of the document to the wider community becomes apparent.

The Shergold Report does not make specific recommendations to the government; rather it reaches a series of immutable conclusions based on the narrative in each section and is intended to spark public comment and discussion from a wide spectrum of people both within and outside of the Australian Public Service.

The Shergold Report contains 28 proposals for improvement; the key conclusions are reproduced below are reformatted as recommended good practices for any organisation planning to undertake a major program of works:

Ensuring Robust Advice: Good governance is founded on good policy, and good policy depends on good advice. To this end, executives and managers should be held accountable for the quality of advice they provide. Significant advice should be provided in writing and records maintained.

Decision Making: The importance of decision-making, and the circumstances under which it occurs, underscore the need to have well-functioning support systems in place.

Creating a Positive Risk Culture: Moving the organisation from reactive, defensive risk management; to proactive, performance-focused risk engagement. The major challenge is to embed the new approaches within a strong risk culture. This requires: understanding appetites for risk on individual programs and across the portfolio, appointing a Chief Risk Officer, at a senior executive level, proposals should be supported by an endorsed Risk Management Plan, and preparing a bi-annual whole-of-organisation Risk Assessment for the governing body, analysing the system-wide impact of operational, financial, strategic, legislative and procurement risks faced by the organisation.

Enhancing Program Management: Program and project management are too often seen as control activities; they are actually creative processes!  They require discipline and professional expertise to maintaining single point accountability while being open and flexible to the opportunities of networked governance structures. To achieve this requires:

  • Defined standards of proficiency for project and program managers, with active support through career development opportunities, continued education and participation in professional communities of practice such as the upcoming Project Governance and Controls Symposium.
  • For each project or programs[1], a clear understanding of who accepts end-to-end responsibility for managing implementation (typically the Sponsor[2]), wields delegated authority and where accountability resides.

Opening up to diversity: A diversity of perspectives in the workplace and the boardroom improves performance. Diversity increases critical analysis of information, results in better decision-making and challenges ‘groupthink’. Program advisory groups should be established that include representation drawn from outside the organisation in order to capture a broader diversity of perspectives and knowledge.

Embracing adaptive governance: Organisations that thrive are flexible. They seize opportunities, learn rapidly and recognise that partners will be needed to deliver long-term goals. When they enter uncharted territory they respond fast, start small, test new approaches, watch market responses, learn from doing, scale-up their activity or, if necessary, try again.

Most importantly, they are honest about failure. They recognise that mistakes happen, interrogate why they occurred and set in place remedial measures to ensure that they perform better next time. Failure and its lessons are an inevitable part of entrepreneurial life but are also central to maintaining organisational competitiveness. This means (where possible) new proposals should include a trial or demonstration stage, allowing new approaches to be developed fast and evaluated early. Large projects should incorporate staged decision-making[3].

Conclusions

Good governance is focused on creating good outcomes, not developing a straightjacket of impenetrable and restrictive procedures – the person or organisation that has never made a mistake has never made anything! The art of effectively using project and programs to create a new and desirable future is effective governance, backed by prudent risk management and effective, adaptive delivery and change management processes. The Shergold Report concludes that:

  1. Policy is only as good as the manner in which it is implemented
  2. Policy advice can only be frank and fearless if it is supported by written argument.
  3. Deliberations, oral and in writing, need to be protected.
  4. Deliberative documents need to be preserved, whether written on paper or delivered by digital means.
  5. It is up to ministers (the governing body), not officials (management), to make policy decisions.
  6. The effective management of risk is just as important in the public sector as in the private – perhaps more so.
  7. As the public service fully commits itself to measuring results by outcomes, program management needs to be accorded far greater professional status.
  8. Good governance increasingly depends on collaboration across sectors.
  9. The APS needs to be further opened up. Diversity and external inputs to the organisation.
  10. An adaptive government (organisation) can respond rapidly to changing circumstances without taking unnecessary (and unforeseen) risks.

The one area missing from the Shergold Report is recognition of the importance and difficulty of implementing organisational change (and the disciplines of change management and benefits realisation). The concepts are implicit in many aspects of the report but would have benefitted from direct discussion.

These limitations aside, the Shergold Report is a very deep and well considered document, well worth the effort of reading by both private and public sector mangers and governors. It highlights failures and the learning that can be taken from the experiences to improve future outcomes. To quote Confucius “By three methods we may learn wisdom: First, by reflection, which is noblest; Second, by imitation, which is easiest; and third by experience, which is the bitterest”. Learning from other’s experience may not be the ‘noblest’ option but is far preferable to repeating avoidable mistakes.

We will be commenting further on this report in future posts and I’m sure it will feature prominently in discussions at the upcoming Project Governance and Controls Symposium that is being held in Canberra in May.

Shergold1

The full report can be downloaded from: http://www.apsc.gov.au/publications-and-media/current-publications/learning-from-failure

From a completely different source, the Australian Infrastructure Plan Priorities and reforms for our nation’s future (Feb. 2016), recommendations under Chapter 9 – Governance calls for very similar processes to the Shergold Report.  These reports, and many previous, have consistently promulgated the same message.  We know what needs to be done, understanding why its not being done is the real challenge.


 

[1] To understand the difference between a project and a program see: http://www.mosaicprojects.com.au/WhitePapers/WP1002_Programs.pdf

[2] For more on the role of the Sponsor see: http://www.mosaicprojects.com.au/WhitePapers/WP1031_Project_Sponsorship.pdf

[3] For more on ‘gateway reviews see: http://www.mosaicprojects.com.au/WhitePapers/WP1092_Gateways-Scorecards.pdf

Some ideas for making project management effective and efficient in 2016

SuccessIt’s a New Year and by now most of us will have failed to keep our first set of New Year resolutions! But it’s not too late to re-focus on doing our projects better (particularly in my part of the world where summer holidays are coming to an end and business life is starting to pick up). Nothing in the list below is new or revolutionary; they are just good practices that help make projects successful.

Most projects that fail are set up to fail by the organization and senior management (see:  Project or Management Failures?).  80% of projects that fail don’t have a committed and trained project sponsor. An effective project sponsor will:

  1. Give clear project objectives.
  2. Help craft a well‐defined project scope.
  3. Remove obstacles that affect project success.
  4. Mediate disagreements with other senior stakeholders.
  5. Support the project manager.

The role of the project or program sponsor is outlined in: WP1031 Project & Program Sponsorship.

Customers or end‐users are critically important to the success of ‘their project’. Unfortunately there is an extreme shortage of ‘intelligent customers’.  A ‘good customer’ will:

  1. Help refine the project scope – no one gets it 100% correct first time.
  2. Convey requirements fully and clearly
    (see: WP 1071 Defining Requirements).
  3. Avoid changing their minds frequently.
  4. Adhere to the change management process.

Every project team needs expertise – this is frequently provided by external experts. Subject‐matter experts should:

  1. Highlight common pitfalls.
  2. Help rather than hinder decision making.

The work of the project is done by ‘the team’. A committed and motivated project team will:

  1. Buy into the project’s objectives.
  2. Identify all of the required tasks and ensure the schedule is complete and accurate.
  3. Provide accurate estimates.
  4. Report progress and issues truthfully.
  5. Deliver their commitments.
  6. Focus on achieving the intended benefits
    (see: WP 1023 Benefits and Value).

Finally, the project manager

  1. Recognises that there is no “I” in project and works with the team and stakeholder community to create a successful outcome
  2. Resolves issues and risks that may arise from the 18 items above quickly, efficiently and effectively.

Making Projects WorkAlmost all of the items listed require action by people other than the project manager – this highlights the fact that projects are done by people for people and the key skill required by every project manager is the ability to influence, motivate and lead stakeholders both in the project team and in the wider stakeholder community.

For more on Making Projects Work see: http://www.mosaicprojects.com.au/Book_Sales.html#MPW

Is your steering committee costing $5000 per hour?

The loaded cost of running a committee of senior managers can easily exceed $5000 per hour once the opportunity costs are included.  Productive committees offset this by creating value, hopefully significantly greater than their running costs.  Project and program steering committees should be no different!

Steering_Committee

However, if the steering committee is simply focused on ‘governance’ it is highly unlikely to be generating any significant value.  At the management level where most steering committees operate there is very little governance decision making needed and conformance and assurance usually needs specialists.

The first four functions of governance defined in The Functions of Governance are:

  • Determining the objectives of the organisation: this is done by the organisation’s governing body and implemented through the strategic plan. The project should have been selected because it contributes to achieving the strategic plan, a function of portfolio management, but once the project has started it is rather too late.
  • Determining the ethics of the organisation: this is done by the organisation’s governing body; it is a duty of every manager to support the organisation’s ethical standards and ensure the people they are managing conform. But you do not need a committee to ensure this occurs, just the project manager’s line manager (usually the Sponsor).
  • Creating the culture of the organisation: again this is done by the organisation’s governing body; it is a duty of every manager to support the organisation’s cultural standards and ensure the people they are managing conform. But you do not need a committee to ensure this occurs, just the project manager’s line manager (usually the Sponsor).
  • Designing and implementing the governance framework for the organisation: this should be done before the project is started and include delegations of authority for expenditure and decision making and escalation paths. If it has not been done, one half hour meeting of the sponsor and a few key managers can set the delegations.

In summary, the aspects of governance that determine the way the organisation operates and how the project or program will fit into the overall governance framework does not need a monthly meeting of any type.  There are management responsibilities but these are vested in the responsible line manager, typically the Sponsor (see more on the role of a Sponsor).

The final two functions of governance are ensuring accountability by management and conformance by the organisation.  A steering committee can certainly focus on these aspects of governance but if they do, they are largely wasting their time and most of the $5000 per hour.  There are two fundamental reasons for this:

  1. It is extremely poor governance for a managing entity to seek to provide assurance that the people it is managing are conforming. Assurance oversight should be provided by an independent body.
  2. Most aspects of project surveillance and assurance require high levels of technical skill. It is highly unlikely any of the managers on a steering committee posses these skills (see more on project surveillance).

The organisational entity best suited for the work of surveillance and assurance is a PMO with appropriate support from management. If there is an effective PMO structure in place with the ability to identify shortcomings, backed up by responsible line management there is no need for another committee to second guess the process a few weeks later (see more on PMOs).

Dilbert-committee

Some of the completely unproductive ‘governance’ functions undertaken by ‘steering committees’ include:

  • Validating correct procedures have been followed (properly resourced PMOs are a better and cheaper option).
  • Discussing negative variances and allocating blame (management action is needed not committee discussions).
  • Second guessing management decisions after the event and interfering in the day-to-day running of the project (project professionals are not helped by interference from amateurs – even if they are senior managers).
  • Listening to lengthy reports on what has happened during the last month (effective reporting is all that is needed).

Being involved in this type of activity may make the steering committee members feel important but contributes little or nothing of value in a well governed and structured organisation; if the organisation is not well governed and structured the committee members would be far better off focusing on fixing the real problems.

 

Steering Committees can be highly valuable!

The constitution of most steering committees creates a real opportunity to add value to the overall management of a project or program, but only if the committee focuses on helping craft success. Steering committees typically include members from a range of areas within the organisational affected by the project and its deliverables. Therefore as a group its members are uniquely placed to assist the project manager and sponsor deliver a successful project by helping them steer a path through the organisational politics and stakeholder issues that confront any project or program.

This objective can be achieved by making the members of the steering committee personally responsible for the realisation of value from the organisation’s investment in project, and in particular for dealing with the organisational change and stakeholder issues that are outside of the project manager’s responsibilities. Some of the key responsibilities allocated to the steering committee may include:

  • Responsibility for preparing the organisation for the changes needed to make use of the project’s deliverables and the realisation of value.
  • Managing the interface between the project and the organisational change management work
  • Being available to assist in the management of stakeholder issues escalated from the project and/or identified in areas outside of the direct influence of the project.
  • Ensuring effective benefits management is in place for the life of the initiative (ie, it continues after the project is closed).
  • Dealing with any other aspect of organisational politics that may affect the work of the project or the on-going change initiative.
  • Making value based decisions on complex change proposals, including contributing positively to the resolution of intractable problems, to optimise the value outcome for the organisation.

Obviously the steering committee also needs to take an interest in the project its steering to success. The problem is these are all management activities, not governance activities (for more on this see Does organisational governance exist?).

Effective steering committees work with the project manager and sponsor to identify the external influences causing problems and help the project successfully navigate the organisational stakeholder environment. They also resist the urge to interfere in the actual running of the project or program. There is a world of difference between a collaborative and supportive approach focused on success and the negative approach adopted by so many steering committees that seems to translate ‘governance’ into giving the project manager a ‘hard time’ to ensure compliance with ‘due process’ even if this adds to the existing problems.

Are your organisation’s steering committees worth their hourly running costs?

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

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:

Internet minuteRecognising 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.

Ethics and sustainability

Building ethics and sustainability into a project does not limit its success; in fact the reverse is often true. London’s Crossrail project is turning into an outstandingly successful project despite numerous challenges including finding hundreds of skeletal remains from the Black Death in the excavation for one of its major stations.  One can only hope Melbourne’s Metrorail project to construct a similar heavy rail tunnel under the CBD is as successful.

One factor in the Crossrail success has been the focus of the UK government on developing the skills needed to manage major infrastructure projects focused on the Major Projects Authority. This multi-year investment links proactive oversight and reporting, with research, support and training designed to create an organic capability to make major projects work (more on this later). Another is being prepared to ‘think outside of the square’ to solve major challenges – the focus of this post.

The challenge faced by Crossrail (and to a lesser extent Metrorail) is what to do with millions of tonnes of excavated materials when your project is situated under a major city??  The Crossrail solution has been innovative and coincidentally focused on restoring the environment of my youth.

Wallasea Island unloading wharf

Wallasea Island unloading wharf

Tidal marshlands may not be the scenery of choice for many but the marshes do have a fascination for those of us who grew up playing in and around them. My home and Charles Dickens 150 years earlier were the North Kent marshes.

Pip at the start of Great Expectations: “Ours was the marsh country, down by the river, within, as the river wound, twenty miles of the sea…”  and elsewhere “The dark flat wilderness, intersected with dykes and mounds and gates, with scattered cattle feeding on it… the low leaden line of the river… and the distant savage lair from which the wind was rushing, the sea…”

The landscape is not quite as bleak as it was (but still comes close in winter). The marshes have been drained and there are hops and orchards where there would once have been a windswept wilderness. But the Kent that Dickens knew can still be glimpsed if you know where to look, including the graves where Pip was first confronted by Magwitch in St. James’ churchyard at Cooling.

Seals at Wallasea Island

Seals at Wallasea

However, what may be seen as less than desirable real-estate to people not born on or near the marshes is essential habitat for a vast range of migratory birds and native wildlife.  Unfortunately, in the 150 years since Dickens, the draining, farming and urbanisation of the lands around the Thames and Medway estuaries has destroyed much of this valuable habitat. But the tide is turning.

The Royal Society for the Protection of Birds (RSPB) has been on the campaign trail for the last 30 years to re-establish the marshlands in North Kent and Essex.  One of their earlier successes was to convert the industrial landscape of the Cliffe marshes (my home village) into Cliffe Pools.

Cliffe Pools before the RSPB project

Cliffe Pools before the RSPB project

The chalk hills and clay marshes were home to whiting works from the early 1700s and Portland cement works from 1866. Several years after the last of the factories finally closed, the flooded quarries used to dredge clay and some of the former industrial sites were brought by the RSPB and are now a steadily improving wildlife reserve.

Cliffe Pools after the RSPB project

Cliffe Pools after the RSPB project

On the other side of the Thames, the RSPB and Crossrail have combined in to create a new marshland on a massively larger scale.  Wallasea Island in Essex is an on-going project that has used 3 million tonnes of clay from the Crossrail excavations to start the transformation of drained farmland into coastal wetlands and marshes.  Another 10 million tonnes will be required to complete future stages of the project.  The drained farmland was several meters below the high tide level, protected by sea walls (and under increasing threat from rising sea levels); coastal marshes need to be a bit above sea level. Massive amounts of fill were required for the ‘wild coast project’.

Crossrail solved their problem of ‘what to do with millions of tonnes of excavated spoil’ by shipping the materials to Wallasea Island and working with the RSPB to transform the area. A win-win outcome Crossrail were able to use costal shipping to remove the clay from London minimising road haulage and carbon emissions, and they avoided tipping costs from commercial landfill sites. 80% of the materials were transported by water or rail on a tonne per kilometer basis. The RSPB got a head start on a major project to reinstate a major area of coastal marshland and 1000s of birds are getting a new home.

E+S-5

When completed in 2025, the project will have created 148 hectares of mudflats, 192 hectares of saltmarsh, and 76 acres of shallow saline lagoons.

Wallasea Island is a work in progress, but with at least two major tunnelling projects in London still to come, the Thames Tideway sewage scheme and Crossrail2, and the infrastructure in place to take the excavated spoil completion of this project seems likely.

E+S-6

What is of importance form the perspective of this post is the Crossrail project is 65% complete and on time and on budget – being environmentally friendly and effective are not incompatible!  It will be interesting to see what the Metrorail project does with its excavated spoil.

PMP® exam is changing on 11th Jan. 2016

PMPThis post offers a detailed look at the new PMP examination content and what you can expect to see different in a exam taken after the 2nd November 2015.

Notes:

  1. PMI have moved the start date back from the originally publicised date in November to January 2016.
  2. There will be no changes to the CAPM exam or any other PMI credential other than the PMI-ACP.
  3. Our free daily PMP questions are now aligned to the new exam see: http://www.mosaicprojects.com.au/Training-PMP-Q-Today.html
  4. All PMP of our courses starting from September 1st will be aligned to the new PMP examination, see:  http://www.mosaicproject.com.au/

The starting point for this update is the PMP Role Delineation Study (RDS) completed in April 2015, which has provided an updated description of the role of a project management professional and will serve as the foundation for the updated PMP exam. To ensure its validity and relevance, the RDS update has captured input from project management practitioners from all industries work settings, and regions. The research undertaken to update the RDS included focus groups, expert input and a large-scale, global, survey of Project Management Professional (PMP)® certification holders.

Overview of Changes

The RDS defines the domains and tasks a project manager will perform plus the skills and knowledge that a competent project manager will have. The five ‘domains’ of  Initiating, Planning Executing, Mentoring & Controlling and Closing remain unchanged, although there has been a slight reduction in the importance of ‘closing’ and an increased emphasis on executing (reflected in the allocation of questions). The other major changes are:

  • An emphasis on business strategy and benefits realisation: this new, included because many PMs are being pulled into a project much earlier in its life when business benefits are identified. There is also an increased focus across all of the other domains on delivering benefits (not just creating deliverables).
    See more on benefits management.
  • The value of lessons learned now has added emphasis: lessons should be documents across the whole project lifecycle and the knowledge gained transferred to the ‘organisation’ and the project team. See more on Lessons Learned.
  • Responsibility for the project charter shifted to the Sponsor: Most project managers are not responsible for creating the charter; the Sponsor or project owner is primarily responsible.  The PM is a contributor to the development and is responsible for communicating information about the project charter to the team and other stakeholders once the project starts.
    See more on the Project Charter.
  • Added emphasis on enhancing project stakeholder relationships and engagement: The RDS sees stakeholder engagement as a two way relationship rather than a one-way reporting function. Communication is expanded include an emphasis on relating and engaging with stakeholders. This is the theme of our last post, see: The Elements of Stakeholder Engagement.

Major Content Changes
Changes

A summary of the major content changes is:

Domain 1 Initiating the Project

Percentage of questions unchanged 13% =  26 questions.

Three tasks added:
–  Task 2: Identify key deliverables based on business requirements.
–  Task 7: Conduct benefits analysis.
–  Task 8: Inform stakeholders of approved project charter.

One task deleted:
–  Old Task 2: Define high level scope of the project.

One task significantly changed:
– Task 5: changed from ‘develop project charter’ to ‘participate in the development of the project charter’.

Major changes in the knowledge and skills required for this domain.

Domain 2 Planning the Project

Percentage of questions unchanged 24% =  48 questions.

One task added:
–  Task 13: Develop the stakeholder management plan.

One task significantly changed:
–  Task 2: expanded from ‘create WBS’ to ‘develop a scope management plan (including a WBS if needed)’.

The knowledge and skills required for this domain have been revised but basically cover the same capabilities.

Domain 3 Executing the Project

Percentage of questions increased from 30% to 31% =  62 questions.

Two tasks added:
–  Task 6: Manage the flow of information to stakeholders.
–  Task 7: Maintain stakeholder relationships.

One task deleted:
–  Old Task 6: Maximise team performance.

The knowledge and skills required for this domain have been revised but basically cover the same capabilities with the exception of the addition of ‘Vendor management techniques’.

Domain 4 Monitoring and controlling the project

Percentage of questions unchanged 25% =  50 questions.

Two tasks added:
–  Task 6: Capture, analyse and manage lessons learned.
–  Task 7: Monitor procurement activities.

One task deleted:
–  Old Task 6: Communicate project status to stakeholders.

The knowledge and skills required for this domain have been revised and expanded.

Domain 5 Closing the project

Percentage of questions reduced from 8% to 7% =  14 questions

No new tasks added or significantly changed.

The knowledge and skills required for this domain have been revised but basically cover the same capabilities.

Cross Cutting Knowledge and Skills

Cross cutting knowledge and skills are capabilities required by a project manager in all of the domains.  This areas of the RDS has been increased significantly.  The full list of knowledge and skills is
(* = included in previous RDS):
1.   Active Listening*
2.   Applicable laws and regulations
3.   Benefits realization
4.   Brainstorming techniques*
5.   Business acumen
6.   Change management techniques
7.   Coaching, mentoring, training, and motivational techniques
8.   Communication channels, tools, techniques, and methods*
9.   Configuration management
10. Conflict resolution*
11. Customer satisfaction metrics
12. Data gathering techniques*
13. Decision making*
14. Delegation techniques
15. Diversity and cultural sensitivity*
16. Emotional intelligence
17. Expert judgment technique
18. Facilitation*
19. Generational sensitivity and diversity
20. Information management tools, techniques, and methods*
21. Interpersonal skills
22. Knowledge management
23. Leadership tools, techniques, and skills*
24. Lessons learned management techniques
25. Meeting management techniques
26. Negotiating and influencing techniques and skills*
27. Organizational and operational awareness
28. Peer-review processes
29. Presentation tools and techniques*
30. Prioritization/time management*
31. Problem-solving tools and techniques*
32. Project finance principles
33. Quality assurance and control techniques
34. Relationship management*
35. Risk assessment techniques
36. Situational awareness
37. Stakeholder management techniques*
38. Team-building techniques*
39. Virtual/remote team management

Two skills that have been dropped are knowledge of:
–  PMI’s Code of Ethics and Professional Conduct
(although this continues to have a major influence on the approach PMI
     expects project managers to adopt in the exam and the ‘real world’).
–  Project Management Software

The effect on the exam

PMI have advised that 25% of exam content will be new, focused on new topic areas (ie, the eight new tasks) added to examination, in addition, many other questions will be updated to reflect changes in the descriptions of tasks and changes in the underpinning skills and knowledge requirements.  We will be updating our materials from September 2015 to take these changes into account. Fortunately a large percentage of the ‘new’ materials from the RDS are already part of our PMP course (because we felt they were essentially good practice) or in other training courses we offer – overall this update makes very good sense.

Many aspects of the PMP exam are not changing including the eligibility requirements, formal training requirements, the passing score (which remains secret) and the design of the questions, many of which are scenario based seeking information on what should you do.

There is no change to other PMI exams, the CAPM, PMI-SP and other credentials remain unaltered.

Will there be more changes?

The sort answer if ‘yes’! Changes in the RDS occur every 3 to 5 years and as a consequence, the exam content outline changes, new topics are added, and shift in weighting occur.

In addition, the PMP exam also changes when the PMBOK® Guide is update (this is due in 2017). Changes in the PMBOK® Guide cause changes in terminology, changes to elements of process groups and exam questions are changed to reflect these alterations. However, many other references are used to create PMP content in addition to the PMBOK,  and if the PMBOK has contents not reflected in the RDS this section not examined.

So moving forward, the current version of the exam is active until 1st Nov. 2015; the new version of the exam is available from 2nd Nov. 2015, and the next change will be in mid-to-late 2017.

For this change, there is no change over period (including for re-sits) – the ‘old’ exam applies up until the 1st, the new exam from the 2nd November.  Both before and after the change, your exam results available immediately if you take a computer based test.  For more on the current examination, fees, eligibility requirement, etc, see: http://www.mosaicproject.com.au/pmp-training-melbourne/.

A different set of changes has been announced for the PMI-ACP (Agile) credential (visit the PMI website for more details).

PMI have also announced changes to the way PDUs are earned as part of their Continuing Certification Requirement (CCR) program, effective from the 1st December 2015.  For more on this change see: https://mosaicprojects.wordpress.com/2015/06/06/pmi-pdu-update/