Project Implementation, Closure,
and Evaluation
Chapter 14
14-1
Copyright 2012 John
Wiley & Sons, Inc.
Announcements/Upcoming
Next Week – Chapter 13 Ethics & Leadership
Final Exam – Mon, Dec 8th: 11:30 – 2:30
Today – Chapter 14
•
•
•
•
Implementation Plans
Administrative Closure
Closing the Project
Project Evaluation
Copyright 2012 John 14-2
Wiley &
Generic Project Life Cycle
An IT Project Methodology
2-4
Project Implementation
Focuses on installing or delivering the project’s major
deliverable – the information system that was built or
purchased
Three general tactical implementation plans:
14-5
Direct Cutover
14-6
Direct Cutover
May be appropriate when:
Risks associated with direct cutover:
14-7
Parallel
14-8
Parallel
May be appropriate when:
Risks associated with parallel cutover:
14-9
Phased
14-10
Phased
May be appropriate when:
Risks associated with phased cutover:
14-11
What should be used?
Cutover
Parallel
Phased
14-12
Administrative Closure
14-13
Administrative Closure
14-14
Realities of Project Closure…..
14-15
Project Sponsor Acceptance
Shortsighted vs. Knowledgeable Sponsors
Likelihood of acceptance improved when:
 Acceptance criteria clearly defined in the early stages of project
 Completion of all project deliverables and milestones thoroughly
documented
14-16
From an administrative view, closure allows
for all loose ends to be tied up. From a
psychological perspective, it provides all
of the project stakeholders with a sense
that the project was under control from
the beginning through to its end.
14-17
Administrative Closure – Final Project Report
The Final Project Report includes
14-18
Administrative Closure – Final Meeting/Presentation
The Final Meeting and Presentation
14-19
Closing the Project – requirements include:
1. Verifying that all deliverables and open items are
complete.
2. Verifying the project sponsor or customer’s
formal acceptance of the project.
3. Organizing and archiving all project deliverables
and documentation.
4. Planning for the release of all project resources
(i.e., project team members, technology,
equipment, facilities, etc.).
5. Planning for the evaluations and reviews of the
project team members and the project itself.
6. Closing of all project accounts.
7. Planning a celebration to mark the end of a
(successful) project.
14-20
Project Evaluation
Individual Performance Review





Begin with the individual evaluating his/her performance.
Avoid “Why can’t you be more like….?”
Focus on specific behaviors, not the individual.
Be consistent and fair.
Reviews should provide a consensus on improving performance.
14-21
Project Evaluation - Postmortem Review
Between Project Manager and Project Team
 .
14-22
Project Evaluation – Project Audit
 Preferably performed by an outside Auditor who
should:
•
•
•
•
•
•
Have no direct involvement or interest in project.
Be respected and viewed as impartial and fair.
Be willing to listen.
Present no fear of recrimination from special interests.
Act in the organization’s best interest.
Have broad base of project and/or industry experience.
14-23
Project Evaluation
Evaluating Project Success
14-24