When Is A Project Actually Over?
From the Voices on Project Management Blog
by Cameron McGaughy,
Lynda Bourne, Kevin Korterud, Conrado Morlan, Peter Tarhanidis, Mario Trentim, Jen Skrabak, David Wakeman, Wanda Curlee, Christian Bisson, Ramiro Rodrigues, Soma Bhattacharya, Emily Luijbregts, Sree Rao, Yasmina Khelifi, Marat Oyvetsky, Lenka Pincot, Jorge Martin Valdes Garciatorres, cyndee miller
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.
View Posts By:
Cameron McGaughy
Lynda Bourne
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Wanda Curlee
Christian Bisson
Ramiro Rodrigues
Soma Bhattacharya
Emily Luijbregts
Sree Rao
Yasmina Khelifi
Marat Oyvetsky
Lenka Pincot
Jorge Martin Valdes Garciatorres
cyndee miller
Past Contributors:
Rex Holmlin
Vivek Prakash
Dan Goldfischer
Linda Agyapong
Jim De Piante
Siti Hajar Abdul Hamid
Bernadine Douglas
Michael Hatfield
Deanna Landers
Kelley Hunsberger
Taralyn Frasqueri-Molina
Alfonso Bucero Torres
Marian Haus
Shobhna Raghupathy
Peter Taylor
Joanna Newman
Saira Karim
Jess Tayel
Lung-Hung Chou
Rebecca Braglio
Roberto Toledo
Geoff Mattie
Recent Posts
Project 2030: Skills We Need to Cultivate Now
The Technical Program Manager: How to Stay Relevant in 2025
5 Things Your Operational Plan Should Do
5 New Project Guardrails for Adaptive Leaders
The Leader's Voice: Respect It, Protect It, and Use It Properly!
Categories
2020,
Adult Development,
Agile,
Agile,
Agile,
agile,
Agile management,
Agile management,
Agile;Community;Talent management,
Artificial Intelligence,
Backlog,
Basics,
Benefits Realization,
Best Practices,
BIM,
business acumen,
Business Analysis,
Business Analysis,
Business Case,
Business Intelligence,
Business Transformation,
Calculating Project Value,
Canvas,
Career Development,
Career Development,
Career Help,
Career Help,
Career Help,
Career Help,
Careers,
Careers,
Careers,
Careers,
Categories: Career Help,
Change Management,
Cloud Computing,
Collaboration,
Collaboration,
Collaboration,
Collaboration,
Collaboration,
Communication,
Communication,
Communication,
Communication,
Communications Management,
Complexity,
Conflict,
Conflict Management,
Consulting,
Continuous Learning,
Continuous Learning,
Continuous Learning,
Continuous Learning,
Continuous Learning,
Cost Management,
COVID-19,
Crises,
Crisis Management,
critical success factors,
Cultural Awareness,
Culture,
Decision Making,
Design Thinking,
Digital Project Management,
Digital Transformation,
digital transformation,
Digitalisation,
Disruption,
Diversity,
Diversity,
Documentation,
Earned Value Management,
Education,
EEWH,
Enterprise Risk Management,
Escalation management,
Estimating,
Ethics,
execution,
Expectations Management,
Facilitation,
feasibility studies,
Future,
Future of Project Management,
Generational PM,
Governance,
Government,
green building,
Growth,
Horizontal Development,
Human Aspects of PM,
Human Aspects of PM,
Human Aspects of PM,
Human Aspects of PM,
Human Aspects of PM,
Human Resources,
Inclusion,
Information Technology,
Innovation,
Intelligent Building,
International,
International Development,
Internet of Things (IOT),
Internet of Things (IoT),
IOT,
Knowledge,
Leadership,
Leadership,
Leadership,
Leadership,
Leadership,
lean construction,
LEED,
Lessons Learned,
Lessons learned;Retrospective,
Managing for Stakeholders,
managing stakeholders as clients,
Mentoring,
Mentoring,
Mentoring,
Mentoring,
Mentoring,
Methodology,
Metrics,
Micromanagement,
Microsoft Project PPM,
Motivation,
Negotiation,
Neuroscience,
neuroscience,
New Practitioners,
Nontraditional Project Management,
OKR,
Online Learning,
opportunity,
Organizational Culture,
Organizational Project Management,
Pandemic,
People management,
Planing,
planning,
PM & the Economy,
PM History,
PM Think About It,
PMBOK Guide,
PMI,
PMI EMEA 2018,
PMI EMEA Congress 2017,
PMI EMEA Congress 2019,
PMI Global Conference 2017,
PMI Global Conference 2018,
PMI Global Conference 2019,
PMI Global Congress 2010 - North America,
PMI Global Congress 2011 - EMEA,
PMI Global Congress 2011 - North America,
PMI Global Congress 2012 - EMEA,
PMI Global Congress 2012 - North America,
PMI Global Congress 2013 - EMEA,
PMI Global Congress 2013 - North America,
PMI Global Congress 2014 - EMEA,
PMI Global Congress 2014 - North America,
PMI GLobal Congress EMEA 2018,
PMI PMO Symposium 2012,
PMI PMO Symposium 2013,
PMI PMO Symposium 2015,
PMI PMO Symposium 2016,
PMI PMO Symposium 2017,
PMI PMO Symposium 2018,
PMI Pulse of the Profession,
PMO,
PMO,
pmo,
PMO Project Management Office,
portfolio,
Portfolio Management,
Portfolio Management,
portfolio management,
presentations,
Priorities,
Probability,
Problem Structuring Methods,
Process,
Procurement Management,
profess,
Program Management,
project,
Project Delivery,
Project Dependencies,
Project Failure,
project failure,
Project Leadership,
Project Management,
project management,
project management office,
Project Planning,
project planning,
Project Requirements,
Project Success,
Ransomware,
Reflections on the PM Life,
Remote,
Remote Work,
Requirements Management,
Research Conference 2010,
Researching the Value of Project Management,
Resiliency,
Risk Management,
Risk Management,
Risk management,
risk management,
ROI,
Roundtable,
Salary Survey,
Schedule Management,
Scheduling,
Scope Management,
Scrum,
search,
SelfLeadership,
SelfLeadership,
SelfLeadership,
SelfLeadership,
SelfLeadership,
Servant Leadership,
Sharing Knowledge,
Sharing Knowledge,
Sharing Knowledge,
Sharing Knowledge,
Sharing Knowledge,
Social Responsibility,
Sponsorship,
Stakeholder Management,
Stakeholder Management,
stakeholder management,
Strategy,
Strategy,
swot,
Talent Management,
Talent Management,
Talent Management,
Talent Management,
Talent Management,
Talent Management Leadership SelfLeadership Collaboration Communication,
Taskforce,
Teams,
Teams in Agile,
Teams in Agile,
teamwork,
Tech,
Technical Debt,
Technology,
TED Talks,
The Project Economy,
Timeline,
Tools,
tools,
Transformation,
transformation,
Transition,
Trust,
Value,
Vertical Development,
Volunteering,
Volunteering #Leadership #SelfLeadership,
Volunteering Sharing Knowledge Leadership SelfLeadership Collaboration Trust,
VUCA,
Women in PM,
Women in Project Management
Date

When Is a Project Actually Over?
By Kevin Korterud
As project managers, we spend a considerable amount of time mobilizing a project to ensure it’s set up for success. To realize value from projects, that same level of attention and focus is also required to successfully end a project. It is key for project managers to have a plan for closure that defines specific activities to wind down and complete essential functions that end the project on a high note.
Here are some essentials to help your project complete successfully so you can enjoy the satisfaction of a job well done:
1. Complete the Project Adoption Schedule
Project managers need to have an objective indicator that signals completion of their projects. In some cases, project managers use indications that determine the completion of the project far too early.
These premature indications can include the installation of technology, signoff of key deliverables or perhaps a subjective decision by the sponsor that the project is over.
One effective means of determining the end of a project is for a project manager to create a schedule for the complete adoption of what the project is creating, e.g., new technology, processes and products. An adoption schedule defines the details around the timeframe, functions and geographies by which the outputs from the project are to be assumed by the various stakeholders.
In essence, a project adoption schedule is a structure that provides an outcome-based path to how the project is supposed to end.
For example, one form of an adoption schedule would be to define the number of users or stakeholder groups that are to use a new technology solution. The adoption schedule would present which geographies would use the new technology over a certain timeframe.
2. Measure Against the Project Business Case
As project managers, we sometimes become so obsessed with on-time, on-budget delivery that we can neglect the rationale that shaped the need for the project. As part of closing out a project, it is important that progress toward the original business case is measured.
The best way to do this on a project is to have business case checkpoints defined from the start to the end of the project. These checkpoints identify and measure the project’s key outcomes. By starting the business case measurement process at the beginning of the project, you eliminate the last-minute rush to determine whether the project was successful from a business perspective.
3. Assure Regulatory Compliance
Even if we do a great job with delivery as well as producing business outcomes, what we do in the area of regulations and other legal mandates is also key. A project that does not comply with regulatory needs stands the chance of diluting its success by requiring additional effort and time to mitigate issues.
As part of project closure planning, schedule timely completion of deliverables required to meet regulatory needs. The effort and schedule allocated for this type of deliverable needs to be given equal importance with other project deliverables.
For example, a project that involves the chemical industry may require material safety data sheets to be filed when a new type of material is introduced into a chemical plant. Even if the introduction of the new chemical material was successful, the project cannot be truly closed until this regulatory deliverable is created.
4. Pay It Forward
Project or program managers sometimes miss out on the opportunity to leverage the fine work we have done to help others in our profession. While it is typical to have a lessons-learned session at the end of the project, quite often those newly created assets, practices and other valuable content are filed away and not leveraged for other projects.
To unlock this potentially untapped source of project management value, work with the Program Management Office or other delivery assurance group to review the completed project and capture artifacts that might assist other projects. This group can take what has been created by your project, refine it and publish the artifact so it can immediately assist other projects.
Have unique activities proven valuable for completing your projects? Perhaps others can benefit from your insights while finishing their project journey. Please comment below!
Posted
by
Kevin Korterud
on: August 11, 2015 09:07 PM |
Permalink
Comments (20)
Please login or join to subscribe to this item
PARAG JAIN
AVP| Credit Suisse
Singapore, Singapore
nice article on official closure.
In the US, all federal government projects evolve into programs. Unlike projects, programs do not have an end date. This is why the US govt has such large debt. :-)
Kevin Coleman
Subject Matter Expert, Author, Speaker and Strategic Advisor| - Insights
Pa, United States
In corporate America, projects evolve into programs when stakeholders want to increase their influence when a good project comes along that has merit!
SANDRINE PAIROT
Senior Consultant at Avertim - Q4R&D Project Manager at GSK| AVERTIM
Bruxelles, Belgium
Thank you for this reminder of the essentials of a project closing process!
Thank you very much for a very nice article and enumerating the project losing process!!!
Suhail Iqbal
Suhail Iqbal PMIATP CIPM FAAPM MPM MQM CLC CPRM SCT AEC SDC SMC SPOC PRINCE2 MCT| PM Training School
Rawalpindi, Punjab, Pakistan
I specially liked the last point "Pay It Forward". This goes by the new concept of meeting the business objectives rather than just delivering the product. Very nice work.
Gail Bertrand
Project Manager| Air Products
Alphen A/D Rijn, Netherlands
I agree with all your points, and to build on the "Pay It Forward" comment, it is good to share those Lessons Learned in personal communications, not only in the stored files and make sure that the people who made the project successful are acknowledged and that any "heroics" performed during the project are applauded and then analyzed to ensure that the root cause can be dealt with earlier on.
Kevin Korterud
Associate Director | Accenture
New Albany, Oh, United States
Thanks all for the great comments! Very glad you liked the content.
Interesting narrative about govt projects...I'm looking right now at how to incorporate iterative processes into public sector projects...a way to delivery to citizens services quicker!
One other way to tell when a project is over is when the coffee runs out! :)
Mark Faggion
Senior PMO Consultant| Shepherdwise
Clayton, Nc, United States
Good article. When I mentor PMs, I use the term "new normal" constantly. You want the results of the project to transition into the normal, everyday life of the stakeholders. Your first three points highlight the drive for a good new normal.
And your emphasis on planning for the END is super important. Too often, the end is only an after thought and treated far too trivially.
Thanks for the solid reminder!
Manas De Amin
Director| Computer Technology Group Kolkata
Kolkata, West Bengal, India
Good article. "Pay it forward" is really a great point.
Thanks Kevin.
Abdullah Al Mamoon
Deputy Managing Director & COO| United Commercial Bank PLC
Dhaka, Bangladesh
Good insights indeed. I think along with all these ending techniques, celebrating project success at the last dot involving all relevant stakeholders could be a very effective way of measuring the success of the project. This would also contribute effectively to set the tone of 'Pay it forward'.
Very important topic, covered well. This is actually (and literally) part of the title of our follow-up book to Green Project Management. The book, Driving Project, Program, and Portfolio Success, features the discussion of the 'scope of view' for a project manager - should they be thinking of the project's product in the long term? Of COURSE they should. This doesn't mean there cannot be a definitive ending of the project, but it DOES mean that we, as project managers, can do a better, more connected job of project management if we just look through to the product of the product in the steady-state in our planning.
Thanks for the posting!
Rich Maltzman, PMP
Kevin Korterud
Associate Director | Accenture
New Albany, Oh, United States
Hi all...thanks for the continuing comments on this article....
Richard...grea3t commentary about thinking of a project as a product...I had one of my clients say that they think there is no such thing as an IT or a business project...every project creates something.
Am already starting the framework for this months blog...'Why I Became A Project Manager"...should make for some great dialog....
Mario Trentim
CEO| PMO Global Alliance
Sao Jose Dos Campos, Sao Paulo, Brazil
Great article, Kevin. I believe it all starts with a good "definition of done" in the beginning. A solid business case with clear benefits drives project success.
Gagan Mathur
Program Manager| Shell India Markets Pvt. Ltd.
Ghaziabad, Uttar Pradesh, India
Nice thoughts on project closure.
Gene Shuman
Associate Professor| George Mason University
Fairfax, Va, United States
The schedules of IT projects, especially for software development, resulting in a product moving into production use should have a tail that corresponds to support for the product after transition to real-world use. It''s a warranty period that should last anywhere from several days to several months.
Given the complexity of IT deliverables, the schedule should cover enough time so that there is confidence in the delivered product and the creation and delivery of a version 1.1 to fix problems experienced by the earliest users and to pay down any technical debt that may have been taken on to meet the go-live date. This can be provided y the project team or a separate operations support team, but the project shouldn't be considered 'done' until then.
Kevin.
Excellent article about closure... yes yes.. a good reminder to determin when a project is really closed. Pay it forward. wish it was always that easy :-)
Thanks for sharing,
Regards,
Paco
Thank you for sharing this blog. I shared this to my Program Manager, Tech Lead, and to the company owner. The company owner got interested and asked me to share this to him.
Kevin Korterud
Associate Director | Accenture
New Albany, Oh, United States
Hi Alberto...glad the blog was valuable to your efforts...perhaps one of my next blogs will be on starting up a project!
Ezara Penning
Systems Administrator I| Lincoln Land Community College
Springfield, Il, United States
Terrific article, thank you!
Please Login/Register to leave a comment.
|
Don't ever take a fence down until you know why it was put up.
- Robert Frost
|