A Project Success Plan (PSP) is different from a Project Management Plan (PMP), sometimes referred to as a Project Execution Plan (or PEP). A PMP is a typically produced by the Project Manager to describe how the project will be managed and controlled in its delivery/execution phase, whereas the PSP is a documented meeting convened by the Project Manager to discuss and agree "what success means" to all key stakeholders. The PSP (like a PMP/PEP) should draw from project artefacts such as the Project Charter and the Customer Brief.
Project Success Plans can Help the Team to "Gel"
Have you ever managed or been involved in a project where, at one point or another, you felt that you were not on the "same page" as other team members? Ensuring everyone on a project team is continually pulling in the same direction can be a challenge. A Project Success Plan can help you to set a solid foundation for stakeholder interactions throughout the project, and to ensure you can detect and rectify any occurrences where stakeholder views and actions start to deviate off plan. In order to ensure everyone starts off on the right foot, it is important to kick off your project communications strategy properly. By this we mean, ensuring that everyone's interpretation of success and their assumptions about the project are aired and discussed in an open group forum, which can be documented and evaluated in a Pareto-type chart format to indicate importance. This is the essence of the Project Success Plan.
The Project Success Plan is a communications planning tool in the project manager's toolkit to get all key project stakeholders on the same page, and understanding each other's prerogatives and drivers for success. This is not always an easy task, since there are likely to be a range of drivers and interpretations of project success amongst your stakeholders. For example, team members who are recipients of the end solution/product may have very different views and expectations of what project success means to those who are focused on delivering the product. It is also likely that some (or maybe all) team members in your project will be working together to achieve a specific objective for the first time. Indeed, the number of stakeholders who have worked together on projects before is an interesting statistic for the project manager to take note of at a project's start. A Project Success Plan meeting should aim to achieve the following outcomes:
- serve as an ice breaker for team members to get to know a little about each other
- discuss and agree the basis for setting the criteria for achieving success;
- team members agree and commit to their roles and responsibilities for the project;
- everyone should understand each other's personality and modus operandi;
- everyone's assumptions about the project and their drivers should be aired, discussed and documented;
- a win/win philosophy and a collaborative approach throughout the project needs to be fostered,
- the team should discuss their collective lessons learned from previous projects/experiences.
The points above are all about communication and common understanding. By understanding how to handle your key/extended teams' communications with each other, stakeholders can avoid accidental and sometimes costly mistakes in communicating information and decisions during the project's life. For example, ensuring that people discuss how meetings, reports and controls should be conducted will help set reporting expectations (e.g. if one person thinks project status reports are "a waste of time", find out why and talk it through).
Because of the emotional focus of a Project Success Plan meeting, it should be held face-to-face whenever possible, however this may not be possible for smaller projects - particularly those that involve geographically disperse stakeholders. In such situations, a virtual conference meeting may be the most practical option. This requires special emphasis from the Project Manager in facilitating the meeting to validate everyone's opinions frequently, ensure good feedback, and level set expectations for the project, since the important signs of body language will be missing.
The Timing of a Project Success Plan.
A Project Success Plan should be completed early in the project's life, as soon as all key members of the project team are in place. Key members are those with a material interest and/or delivery focus in the project. The timing for holding a Project Success Plan meeting can typically be after initial set-up works are complete and the project reaches the start of its detailed planning phase. If stakeholders change during the course of the project, the project manager should include reviewing and updating the PSP with the new stakeholders as part of the Resource Planning.
A Project Success Plan can also be a tool the project manager uses to keep the team focused and engaged. When stakeholders are suffering from project fatigue, the project manager can refer back to the Project Success Plan and use it to motivate the team by reviewing the reasons for the project and what success means to each person.
How should a Project Success Plan be structured; Do All Projects Need One?
All projects will benefit from a Project Success Plan meeting, because it is a mechanism to ensure the following aspects are agreed to:
- Do we all agree on the core reasons for the project's existence?
- Are we all on the same page? Can we agree how to work together (including our roles and responsibilities, team meetings and communication protocols, team member working styles, governance processes and expectations)?
- Are our assumptions about the technical aspects of the project (such as the design, scope, build methodology, work breakdown structure, schedule, budget and method of managing change) clear?
Large, complex projects have many different stakeholders, often spread across many geographic locations. A Project Success Plan for a large project may benefit from being led by a skilled facilitator, and it may need to last several days. Small projects with less complexity will typically not require the same level of detail.
The structure of a Project Success Plan meeting should ensure the emotional success factors are fully aired. It needs to bear relevance to the core Deliverables of the project regarding scope, budget, schedule and quality. An example of a Project Success Plan meeting agenda is shown below (the nature of your project's Project Success Plan agenda will be tailored to the project):
|1. Project Introductions and Executive Summary|
|2. What is the definition of “project success”?|
|3. Our Project Methodology|
|4. Project Fundamentals, Principles & Key Drivers|
|5. Project Assumptions by us all, and how we all work|
|6. Project Scope, WBS, Schedule, Quality and Budget|
|7. Project meeting, governance and review strategy|
|8. Project Organisation and Role Definitions|
|9. Communications Management strategy|
|10. Tracking Benefits after Go Live|
A Project Success Plan is a mechanism to achieve the following positive outcomes for your project:
- Ensure all assumptions about the project, and the meaning of success, are aired and discussed, and any misunderstandings and/or disagreements are resolved early in the project's lifecycle.
- Ensure project team members get to know how to work with each other so that communications throughout the project are efficient and productive
- Assist the project manager in keeping the team focused and engaged, especially on projects of long durations.
Done well, a Project Success Plan meeting can help project managers and the entire team understand how to work together successfully, communicate well with each other, and be a tool to keep the team focused and engaged for the duration of the project.
Planning for success increases your likelihood of a successful project outcome. It is always important to ensure the "facts" of project scope, schedule, design, quality and budget are given due consideration. It is equally important to ensure the emotional aspects of project teamwork - team member expectations, their way of working, their personal aspirations for the project and their assumptions on how the project will unfold - are managed. A Project Success Plan is a method to bring out these emotional aspects. It can be a good platform to ensure the whole team continually pulls in the same direction to make your project a success.
Don't forget to leave your comments below
Gareth Byatt is Head of the IT Global Program Management Office for Lend Lease Corporation. He's a PgMP® and PRINCE2 practitioner, and holds an MBA and first-class undergraduate management degree. Gareth has 13 years of project and program management experience in IT and construction. He can be contacted through LinkedIn.
Jeff Hodgkinson is the IT Cloud Program Manager for Intel Corporation. He is a 30-year veteran of Intel with a progressive career as a Program/Project Manager. Jeff's credentials include PMI's PgMP® and PMI-RMP® (Risk Management Professional) Jeff was 2nd place finalist for the 2009 Kerzner International Project Manager of the Year Award. He can be reached through LinkedIn.
Gary Hamilton is the Manager of the PMO and Governance within Bank of America's Learning and Leadership Development Products organization. Gary has 14 years of project and program management experience in IT, Finance and HR. He holds an advanced MBA degree in Finance and several certifications and credentials program management including PMI's PgMP® (and PMP®.. Gary can be contacted through LinkedIn.