Project Close-Out and Termination
15
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-1 Project Close-Out and Termination Chapter 14
description
Project Close-Out and Termination. Chapter 14. Project Termination. All activities consistent with closing out the project Extinction Addition Integration Starvation. Harvesting the Benefits. Handing. Finishing. Gaining . Over the. The Work. Acceptance. Product. Reviewing How . - PowerPoint PPT Presentation
Transcript of Project Close-Out and Termination
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-1
Project Close-Out and Termination
Chapter 14
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-2
Project Termination
All activities consistent with closing out the project
Extinction
Addition
Integration
Starvation
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-3
Elements of Project Closeout Management
Putting it All to Bed
Disbanding the Team
Finishing Handing Gaining Acceptance
for theProduct
Harvesting the Benefits
Reviewing How
The WorkProduct
Over the
It All Went
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-4
Lessons Learned Meetings
Common Errors Misidentifying systematic errors Misinterpreting lessons based on events Failure to pass along conclusions
Meeting GuidelinesEstablish clear rules of behaviorDescribe objectively what occurredFix the problem, not the blame
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-5
Closeout Paperwork
• Documentation
• Legal
• Cost
• Personnel
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-6
Why are Closeouts Difficult?
Project sign off can be a de-motivator
Constraints cause shortcuts on back-end
Low priority activities
Lessons learned analysis seen as bookkeeping
Unique view of projects
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-7
Dynamic Factors to Monitor
1. Static
2. Task-team
3. Sponsorship
4. Economics
5. Environment
6. User
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-8
Early Warning Signs of Project Failure
• Lack of viable commercial objectives
• Lack of sufficient authority to make decisions
• New product developed for stable market
• Low priority assigned to the project by management
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-9
Early Termination Decision Rules
Costs exceed business benefits
Failure to meet strategic fit criteria
Deadlines continue to be missed
Technology evolves beyond the project’s scope
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-10
The Top 10 Signs of IT Project Failure
10. Best practices and lessons learned are ignored 9. Project lacks people with appropriate skills 8. Sponsorship is lost 7. Users are resistant 6. Deadlines are unrealistic 5. Business needs change 4. Chosen technology changes 3. Project changes are poorly managed 2. Scope is ill-defined 1. Project managers don’t understand users’ needs
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-11
Project Termination Issues
Emotional Intellectual
ClientStaff ExternalInternal
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-12
Claims & Disputes
Two types of claims• Ex-gratia claims• Default by the project company
Resolved by• Arbitration
– Binding– Non-binding
• Standard litigation
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-13
Protecting Against Claims
o Consider claims as part of the project plan
o Verify stakeholders know their risks
o Keep good records throughout the life cycle
o Keep clear details of change orders
o Archive all correspondence
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-14
Final Report Elements
Project performanceAdministrative performanceOrganizational structureTeam performanceProject management techniquesBenefits to the organization and customer
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14-15
