Close Out The Forgotten Phase
Close Out The Forgotten Phase
Close Out –
The Forgotten Phase
In the long run, taking the time to close out a
project properly will save time and reduce the
Paula K. Martin, chances of making the same mistake twice.
Martin Training Associates
Karen Tate,
Griffin Tate Group, Inc.
W
ell, you’ve planned the project; you Let’s examine each of these elements of close out and
even involved the whole team in the what you need to do to effectively close out a project.
planning process. You executed the
plan and delivered the final deliver- Final status report
able to the customer. You finished on The first thing you need to do is compile the final
time and within budget. Great job! status report for the project. This report should be no
The customer seems pleased. You let out a big sigh of more than two pages long and should capture the final
relief because the project is done, right? Wrong. results of the project compared to the planned results.
I’m sure you’ve heard the phrase that the party isn’t For example, it should contain actual milestone-com-
over until the fat lady sings. Well, the project isn’t over pletion dates vs. the planned dates, total spending vs.
until close out is complete. Although it’s hard to sus- the budget, total staff effort hours vs. the plan, and so
tain the energy for close out when team members have on. It should also summarize any approved changes
a million other things to do and are ready to move on to made to the project plan. The final status report
the next project, close out is an essential phase and not should be distributed to all project stakeholders, the
something that should be skipped. It is during close out same people who received the status reports through-
that we compare “how we did” to “how we said we out the project.
would do” — did we meet the goals and objectives that
both parties agreed to during planning and updated Customer satisfaction evaluation
through the change-management process? The next step is to determine the customer’s level
Activities completed during close out include: of satisfaction with the project. The best way to do
• Generate the final status report for the project that this is through a survey form. The survey should ask
shows how the team has performed vs. the plan the customer to rate the degree of satisfaction with
• Determine the customer’s level of satisfaction the final deliverable, the schedule and the costs, and
with the final deliverable and with the project process it should address the project management process:
as a whole planning, monitoring, change control, etc. Send this
• Ask the sponsor and key stakeholders to evaluate to the customer, and then arrange a meeting, in per-
the project process son or over the phone, to discuss the project.
• Evaluate both the project and the team processes To create a survey form, construct a set of state-
• Compile the lessons learned for the project ments that can be rated on a scale of 1–7, with 1
• Make recommendations on how to improve the meaning strongly disagrees and 7 meaning strongly
project system agrees. Here are some sample statements that you
• Complete the close-out report might want to include that address project results:
• Archive the project records for future project teams. • The final deliverable met my acceptance criteria.
Lessons-learned List
Project Name: Project Leader:
ject management process.
• The leader did a good job of facilitating
Lesson # Description of Incident Date of Incident Description of Lesson Learned
and monitoring the team process.
• The project was worth my investment
1 Describe the incident or When did the What did you learn from
trigger that caused a incident occur? the incident?
of time.
lesson to be learned. • We worked well together as a team.
What went right or what The more information you solicit from the
went wrong? team, the better, but don’t make the survey
2 too long (no more than 25 statements) or
3 people won’t bother filling it out. Compile
the survey data into a summary form to pre-
4
sent to the team at the lessons-learned meet-
5 ing, where you’ll get the team’s inputs for
the +/∆ form.
■ Figure 3. This list is a useful tool for capturing the team’s learning as it occurs. Make sure
enough detail is captured so that you can recall what happened later, why it happened and
Lessons-learned meeting
what your learned from the incident at the time.
You’ll need the survey results from the
customer, sponsor, other stakeholders and
you’ll know what to do differently. For example, if the team members, the final status report, the customer and
sponsor says the project planning process was inefficient, sponsor +/∆ forms, and the lessons-learned list you’ve
ask what parts of the process were inefficient. Did it take been keeping throughout the project. This list captures
too much time? If so, which parts were too lengthy? How the team’s learning as it occurs, so that you don’t forget
would he or she recommend the planning time for the those lessons when you get to the close-out phase. A
next project be shortened? sample lessons-learned list is shown in Figure 3.
Set this list up before you start planning and update it
Stakeholder evaluation as incidents occur that provide lessons to the team.
It’s also helpful to get feedback from the other stake- Make sure you capture enough detail so that you can re-
holders, such as the resource managers. If you have several call what happened later, why it happened and what you
stakeholders, try combining the survey form with the +/∆ learned from the incident at the time.
form so that you don’t have to sit down with each one indi- Now you’re ready to get the team together to review
vidually. Simply add two columns next to each statement, the project and discuss lessons learned. Review the
label one column “Went Well” and the second column final status report with the team and discuss the reasons
“Ideas for Improvement”. A sample stakeholder evaluation for any variances from the approved plan. Also discuss
form is shown in Figure 2. the approved changes made to the project and the rea-
To the degree that it is possible, try to have a core set sons for those changes. Is there any way these could
of questions that are answered by the customer, sponsor, have been anticipated in the planning stage? What
team members and other stakeholders, so that you can would you do differently the next time to minimize
compare the results. Then add questions that are specific change orders?
to those groups. Next, review the project management process. Here
are some questions to address:
Team evaluation • Were the project objectives met?
Next, the team evaluates both the project and the lead- • Were they the right objectives?
ership of the project. If you have a formal 360-degree • Was the quality plan effective for creating a final de-
feedback program in place, you can use that for your liverable that met the customer’s acceptance criteria?
leader evaluation. However, you’ll still want the team to • Was the risk assessment process effective? Was there
evaluate the project management process. anyone missing from the risk assessment process that
Create a survey, like the ones you created for the cus- should have been included?
tomer and sponsor, with statements directed at the pro- • Were there too many reviews? Not enough? Were they
ject team. If you’re using an online project room, you effective in assuring the quality of the final deliverable?
can poll the team online and let the program calculate the • Were the right people on the team? Were the stake-
results for you. Otherwise, you’ll need to compile the re- holders well represented?
sults yourself. Here are some examples of statements that • Were our resource commitments met (time, effort,
you might want to include for the team evaluation: money)? If not, why not?
• The team’s involvement in planning was effective. • Were our estimates accurate? Did we have enough or
• The leader performed well as a facilitator of the pro- too much contingency?