“What is PRINCE2?” Guest Post Richard Batchelor. (Strategy Execution Methodologies series. Post 3)
| Having established, in Post 1 of this series, that strategy is “just another good idea” until it is implemented and churning out results, and that there is no single turn-key methodology for executing strategy, we then turned our attention first to the “go to” methodology: project management. In Post 2, we recognized that there are two dominant project management methodologies: The Project Management Institute’s (PMI’s) approach and PRINCE2?and we explored PMI’s approach. Now, I am no expert in PRINCE2, so I found one to share insights with us. Even better, Richard Batchelor is an international change management consultant, trained project manager (certified in PRINCE2) and certified human resources professional. He has the street cred of many successful change implementations under his belt. Rich has kindly agreed to write an insider’s overview of PRINCE2 for us. So, what is PRINCE2? PRINCE2 project management is a methodology used widely in the United Kingdom, Western Europe, Australia, and New Zealand. It also has some pockets of use through public service organizations in Asia and Africa. It was born of the UK government project methodology that was needed to deliver IT projects in the 1980s and is an evolution of styles and principles first used in the early days of mass IT project installations. The PRINCE2 that we see today is fundamentally that which was launched in 1996 as a standard method in UK government. As its origins are in public service, it places a significant weight on assurance principles for value, risk, and issue management. It also carries with it a bureaucracy of multitudes of documents required throughout the project cycle. As with most project methodology, PRINCE2 is methodical and somewhat linear in its activity cycle. However, it does have some hints of agile and scrum principles, allowing reiterations in an almost cyclic or iterative solutioning method during the activity cycle. This can be a positive or negative—it ensures the best solution is delivered to the client or customer, but can also mean timelines can be stretched and delivery goals pushed back when activity intensifies at times. The name PRINCE2 comes from the acronym for “PRojects IN a Controlled Environment” with the 2 to recognize the second iteration of the methodology (a previous method used was called PROMPTII). It is a closed project environment, supporting a very strict regime of preventing project creep and clearly defining scope at the outset in the Project Initiation Documents. (Since 2009, the PID has been accepted as multiple documents and not necessarily a single publication.) However, the adaptability of the methods do support its application in a variety of purposes and environments—it is extremely objective and the sequence of activity prevents any significant subjectivity, which is good in supporting fairness and transparency for cultural- and people-based projects. The PRINCE2 process The cycle of activity in a PRINCE2 project goes from start-up through initiation, directing, and ultimately to delivery. The directing period is where most activity takes place and I personally call this the project leadership area. This is where the project is fundamentally managed, using planning, delegation, monitoring, and control of activities, maybe even in sequential or concurrent phases. Here you have the assurance elements of risk mitigation, issue resolution, and communications plans. The client is, at the very least, expected to sit on the project board, but is normally the project executive, the term used for sponsor in PRINCE2. They convene regular board meetings and give considerable time to the management of project communications, identification of risk and subsequent mitigations, and identification of issues that have to be carried through the project timeframe. There is also opportunity for discussing exceptions to the project plan, with the project manager, key stakeholders, and the project executive having a board meeting for decision-making and solving project problems. As some of the many documents prepared during the project delivery period fulfill the need to inform progress and completion of activities, little time is necessary for general project discussion at the board meetings. One of the seven core principles of PRINCE2 is that it manages by exception, doing only what is needed at that point in time to keep the project on track for successful delivery. I don’t want to get caught up too much in activity details, as I just want to give you a feel of the PRINCE2 project management methodology, but it is important to highlight some of these elements as it reinforces the earlier comments about objectivity and clear focus for projects using this method. PRINCE2 manages six key variables A PRINCE2 project recognizes six key variables that encase the controlled environment within which it operates:
The seven core principles PRINCE2 accepts that certain tools and techniques used throughout the project should have been obtained elsewhere, namely people management activities, Gantt charts, critical path analysis, corporate quality assurance, and financial control and value analysis. Although utilized within a project to greater and lesser degrees, these are skill sets that are not taught as part of PRINCE2?instead, the concentration is on activity management and the required management of resources to deliver. The other principles include the following:
It is said that, without application of the seven principles, no project is truly a PRINCE2 project. Perhaps that’s all you need to know, but I think any project is much more than the principles it is built upon. It is the convergence of principle, practice, and people to deliver its goal. Rich has extensive experience in managing change on large-scale projects within the public sector. He is PRINCE2 certified and also an active and founding member of the Association of Change Management Professionals, an accredited internationally educated human resources professional and member of the Human Resources Professional Association in Ontario, Canada. You can find Rich’s blog “Making Change Happen” here, his profile on LinkedIn here, and you can follow him on Twitter @RichBatchelor. Any more PRINCE2 professionals out there? Please do comment. The next post in the series is a review of Change Management methodologies and how they fit into strategy execution. |
“What is Project Management,per the Project Management Institute?” (Strategy Execution Methodologies series. Post 2)
| Strategies identify “what” needs to change. Project management provides a structure for “how.” Some go so far as to say that “projects are the vehicles of change.” The most common organizational flow is this:
History for context It is important to realize that project management is a relatively young discipline, born in the height of the industrial age. In the 1950s, project management was formalized in the construction industry to systemize and synchronize heavy engineering projects: “At that time, two mathematical project-scheduling models were developed—the ‘Critical Path Method’ (CPM) as a joint venture between DuPont Corporation and Remington Rand Corporation for managing plant maintenance projects, and the ‘Program Evaluation and Review Technique’ or PERT, developed by Booz Allen Hamilton as part of the United States Navy's (in conjunction with the Lockheed Corporation) Polaris missile submarine program.” (1) A tactical, logistics-based approach made a lot of sense for such initiatives; the strengths of the approach were increasingly modified for private enterprise. These approaches were codified into basically two schools: The Project Management Institute’s (PMI’s) approach, predominantly used in North America, and PRINCE2, which was derived from a UK government initiative. The spheres of influence seem to radiate out of these centers. This post addresses PMI’s approach, and the next post will address PRINCE2. What is “Project Management”—per PMI? PMI provides a definition of “What is Project Management”on its website (2). Here are a couple of relevant excerpts for our discussion:
Discussion In my view, project management is an essential discipline on most incremental change and on all transformational change. The challenge for many organizations is figuring out the answer to the question, “How much project management rigor do we need?” The rigor rises with the degree of difficulty of the project. At the level of transformational change, the requirement at the highest levels expands into program or portfolio management, which provides for a rolled-up and comprehensive view of the current status of all projects supporting the strategy (again against scope, time, and budget). To all the Project Management Professionals (PMPs) out there: if you feel that I have missed anything, please do comment. What’s next? A review of PRINCE2 and then we peer into the murky waters of change management?a younger discipline that is advancing rapidly. Stay tuned… in fact perhaps you’d like to subscribe. If you are not reading this post on my home site you can link over to The Change Whisperer(http://gailseverini.wordpress.com/) and look for the subscribe button top left. References: Related Posts: |
10 tips for becoming a trusted advisor in leading and managing change
Categories:
Change Management
Categories: Change Management
|
To be an effective change agent one needs influence in the organization. Influence is built on many dimensions of trust?trust that the change agent is legitimately qualified and experienced to execute the scope of work, trust that the change agent has the best interests of the organization at heart, and trust in the relationship with the sponsor. |
Securing ROI in break-out strategy (Strategy Execution Methodologies series. Post 1 Overview)
| Most organisations have developed internal processes and capabilities for executing strategy. However, most of these are built for the transitional strategies that organizations face in average years (familiar improvements that modify systems and processes). The break-out from the recession of 2008 – 11 created market disruption and seismic opportunities and threats. Strategies that take advantage of these shifts are typically transformational in nature (i.e., the nature of the change and the inherent risks are radically different). The first execution choice that organisations face is, “Can we really ‘muscle through’, or do we need to change the way we change?” When the risk of failure, or consequences of short-fall are too high, then organisations suddenly get very serious about governance, processes, and capabilities. What is transformational change? We screen for several characteristics that include:
Furthermore, such initiatives often take on the “do or die” proportions of business imperatives. These initiatives warrant additional rigor: an end-to-end (concept to realization) process, more oversight, more accountability, and more follow-through. This series will provide an overview of the conventional best practices for strategy execution, discuss the gaps in their application to transformational change, and explore advancements that can secure and accelerate ROI. The hand-off from Strategy First of all, let’s understand where strategy comes from and how it is deployed into the organization. Every few years, or sometimes in the face of a seismic market shift, organizations do a comprehensive strategic review. This scrutinizes the market for opportunity and the organisation for efficiency. Often consulting firms like McKinsey & Company, Bain & Company, and Boston Consulting Group are brought in to conduct the review and engage the C-Suite in developing the Strategic Plan for the next 3-5-10 years. Once the strategy is complete and approved by the Board, the leadership team re-convenes and the initiatives are divided up. Most of the allocations are logical, assigned to the division in which they will be implemented and overseen by the head of that area (e.g., finance initiatives are taken by the CFO). The trickier assignments are those driven by technology (where the benefits accrue in another department / division) and those that cross silos (where benefits accrue in multiple departments/divisions). With that, the individual divisions / departments assemble their delivery teams. Most often a business lead is assigned, a project manager is recruited (internally or externally) and then the rest of the team is identified and assembled. What are the strategy execution methodologies? Almost without exception, a form of project (program or portfolio) management is deployed. Sometimes change management is also required and integrated. Project Management Project management is a structured process for organizing change. Generally speaking, it deals with the logistics of implementation ( i.e., what needs to be changed, when does this need to be completed, who do we need working on this, what is our budget, and how are we tracking). It creates a governance structure with roles, decision rights and responsibilities, details specifications around objectives and deliverables, and sets up a tracking process. The project work runs concurrently alongside “business as usual”, leveraging the many of the same resources and augmenting with some specialists. In addition, it builds the new system / process / capability while the old one is still in operation, manages the transition over to the new system / process capability, and decommissions the old. Project teams typically include a business owner, often called a sponsor, who is responsible for making decisions, and a project manager who coordinates the work associated with making the change and managing the project. Additional resources often include business analysts and other specialists whose skills are required to build and implement the new “thing”. Subject matter experts (SMEs) from within the organization are often seconded to the project as well, bringing resources such as content specialists (e.g., underwriters if the change is a new insurance product), marketing managers, communications specialists, training coordinators, etc. Further resources often include members of other affected departments, or those who will be instrumental in the success of the initiative, (e.g., a call centre lead and sales representative in the case of a new insurance product launch). The larger the change, the more expansive the project management approach. For example, if a bank decides to break into the insurance market, and the initiative is the launch of a subsidiary, the work is often structured as a portfolio or program where individual projects are grouped into a delivery hierarchy of groups of projects. In this model, one portfolio manager might have three program managers reporting to him/her, and each of the project managers might have a number of project managers as direct reports. Project management seems to have gotten a lot of traction over the past 20 years—most medium and almost all large organizations are using it. The predominant methodologies are The Project Management Institute (PMI), which is common in North America, and PRINCE2, which has real traction in the UK (for reasons that will become obvious in a subsequent post) and in some of Europe. Change Management Change management is a substantively younger discipline than project management (even if we measure from Kurt Lewin’s Change Theory dating from the 1940s). That theory is based on organisational psychology principles regarding how humans transition through change. If it requires changing the work that people do and how they think about that work, then change management needs to be integrated in the implementation approach. Some of the basic ideas include:
A handful of thought leaders and practitioners have been active in this arena since the 1980s. In terms of process maturity: there is considerable consistency in high level principles, some consistency in general application, and very few public methodologies. Next The next three posts will provide a high-level review of the most common project management methodologies (Project Management Institute and PRINCE2) and change management methodologies, together with a commentary on the strengths and weaknesses of the typical application. In the finale, we will look at how they come together (or not) to optimize a holistic delivery approach right through to results realisation. |
“Change leadership” is not THE silver bullet. The Silver Bullet series.
|
Seems like many organizations are looking for the secret to effective strategic execution?the one thing that will fix the so-called 70% failure rate. The problem is (and we all know it deep down), there are no simple solutions for complex problems. In this series, I will look at the conventional “silver bullets” and explore why none work alone and each is only moderately effective in its common form. |





