Project CloseOut and Termination Chapter 14 Copyright 2010

Project Close-Out and Termination Chapter 14 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14 -1

Project Termination All activities consistent with closing out the project v Extinction v Addition v Integration v Starvation Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14 -2

Elements of Project Closeout Management Harvesting Gaining Finishing Handing Acceptance the Benefits Over the The Work Product for the Reviewing Product How It All Went Putting it All to Bed Disbanding the Team Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14 -3

Lessons Learned Meetings Common Errors Ø Misidentifying systematic errors Ø Misinterpreting lessons based on events Ø Failure to pass along conclusions Meeting Guidelines ü Establish clear rules of behavior ü Describe objectively what occurred ü Fix the problem, not the blame Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14 -4

Closeout Paperwork • Documentation • Legal • Cost • Personnel Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14 -5

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 -6

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 -7

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 -8

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 -9

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 -10

Project Termination Issues Emotional Staff Client Intellectual Internal Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall External 14 -11

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 -12

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 -13

Final Report Elements q Project performance q Administrative performance q Organizational structure q Team performance q Project management techniques q Benefits to the organization and customer Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14 -14

Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 14 -15