CIS600 Week 12 Project Closure Essay

Submitted By abhi3dguru
Words: 1428
Pages: 6

Project Closure
CIS600, Spring 2015
Week 12: April 6 and 8, 2015
Dr. Tim Rodgers

CIS600

Don’t Forget
Homework #7 due Friday April 10

Agenda
• PMP exam questions
• Project Closure
• Types of closure
• Performance reviews
• Retrospectives

• PM Simulation

Course Calendar
Week

Date

Topic

Activity

Due

1

Jan 21

2

Jan 26-28

3

Feb 2-4

Scope Planning

A&D (A) case

4

Feb 9-11

Network Planning

A&D (A) case

Homework 1

5

Feb 16-18

Resource Planning

A&D (A) case

Homework 2

6

Feb 23-25

Project Optimization

A&D (A) case

Homework 3

7

Mar 2-4

Project Monitoring

A&D (B) case

Homework 4

8

Mar 9-11

Risk Planning

Introduction
Project Selection and Organization

9

Homework 0

Homework 5
Spring Break

10

Mar 23-25

Project Leadership

TrustWeb case

11

Mar 30-Apr 1

Midterm Exam

PM Simulation

12

Apr 6-8

Project Closure

PM Simulation

13

Apr 13-15

In-Class Case Studies

Cases TBD

14

Apr 20-22

IT Project Management & Agile

Assigned reading

15

Apr 27-29

Outsourcing & International Projects

GlobShop case

16

May 4-6

Wrap-Up

Case Study Presentations

Homework 6
Homework 7

Case Study Report

Where We Are Now

Project Closure Deliverables

Types of Project Closure
Normal
Premature (< 100% of planned scope)
Perpetual
Failed project
Changed priority (new scope)

Premature Closure
What factors would lead you to consider early termination of a project?

Premature Closure
What factors would lead you to consider early termination of a project?
When costs exceed business benefits
When the project no longer meets strategic fit criteria
When deadlines continue to be missed
When technology evolves beyond the project’s scope

Project Termination in the IT Industry
•An estimated 40% of IT application development projects are canceled before completion
•33% of the remaining projects face significant cost and/or schedule overruns or changes in scope
•IT project failures cost US companies and government agencies $145 billion per year

Top 10 Signs of IT Project Failure
1. Project managers do not understand users’ needs
2. Scope is ill-defined
3. Project changes are poorly managed
4. Chosen technology changes
5. Business needs change
6. Deadlines are unrealistic
7. Users are resistant
8. Sponsorship is lost
9. Project lacks people with appropriate skills
10. Best practices and lessons learned are ignored

Shutting Down the Project
Emotional

Intellectual

Will there be future work?
Loss of interest
Jockeying for position

Identify remaining work
Outstanding commitments
Closure of work orders
Agreements with clients and suppliers Key Closing Activities

Wrap-Up Checklist

TABLE 14.1

Elements of the Final Project Report
Executive Summary
Project goals met/unmet
Stakeholder assessment

Review and Analysis
Scope statement
Procedures and systems
Organizational resources

Recommendations
Technical improvements
Corrective actions

Lessons Learned
Retrospectives

Team and Individual Performance

How do you encourage teamwork and collaboration while recognizing individual performance?

Team Performance Characteristics
How would you measure the effectiveness of the project team?

Characteristics of High Performing
Teams
Share a sense of common purpose
Make good use of individual talents and skills
Have balanced and shared roles
Maintain a problem solving focus
Accept differences of opinion and expression
Encourage risk taking and creativity
Set high personal performance standards
Identify with the team

Project Performance Evaluations
•Don’t leave evaluations of individuals to supervisors of the team member’s home department.
•Don’t measure team performance only on time, cost, and specifications. Sample Team Evaluation Survey

TABLE 14.2

Individual Performance Review
How did each team member contribute to team success?

Individual Performance Assessment
Multiple rater appraisal
(“360-degree” feedback)
Solicit feedback concerning team members’ performance from all of the people that their work…