Project Close-Out and Termination Chapter 14 © 2007 Pearson Education.

Slides:



Advertisements
Similar presentations
Lesson 15: Closing the Project Topic 15A: Close Project Procurements Topic 15B: Close the Project or Phase Administratively.
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
W5HH Principle As applied to Software Projects
Project Sponsorship PM Roundtable December 4, 2006 Slides adapted from Charles Jones, PMP PMI Global Congress NA 2006 presentation.
1 14. Project closure n An information system project must be administratively closed once its product is successfully delivered to the customer. n A failed.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
The Analyst as a Project Manager
Chapter 14. To understand the process of project audit To recognize the value of an audit to project management To determine when to terminate a project.
Planning. SDLC Planning Analysis Design Implementation.
Project Closeout and Termination Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 14 Learning Objectives After completing.
Project Close-Out and Termination
Project Management Fundamentals Project Organization and Integration
Advanced Project Management PM Processes and Framework
Copyright Course Technology 1999
Copyright Course Technology Chapter 16: Closing.
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall13-1 Project Evaluation and Control Project Termination and Closeout Chapter
Software Project Failure Software Project Failure Night Two, Part One CSCI 521 Software Project Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Chapter 4 Performance Management and Appraisal
Finishing the Project and Realizing the Benefits Chapter 15 Contemporary Project Management Kloppenborg © 2012 Cengage Learning. All Rights Reserved. May.
4 th European Project Management Conference, London, 6-7 June 2001 © Human Systems International Limited, Project Closeout Management. More.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
Copyright Course Technology 1999
Computer Calamities The University of California Berkeley Extension Copyright © 2007 Patrick McDermott Field, Tom, “When Bad Things.
BSBPMG505A Manage Project Quality Manage Project Quality Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG505A.
Chapter 13 Project Termination.
Project Management Starting out. What makes projects different to BAU (Business as Usual)?  Change - Projects are the means by which we introduce change.
Day 25 ELC 347/BUS 348/PSA 347.
Module 5 Session 5.2 Visual 1 Module 5 Refining Objectives, Scope, and Other Project Parameters Session 5.2 Reviewing the PAR and refining key project.
Information Technology Project Management Managing IT Project Risk.
Day 3 in the pmProject Management Project Management (PM) ADJUST.
Dr. Rob Hasker. Avoiding failure  Standish Report, 2014 Standish Report 31% projects cancelled before completion 53% projects ~190% of original estimate.
Project Close-Out and Termination Chapter 14 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall14-1.
Modern Project Management
Degree and Graduation Seminar Integration Management
CLOSE PROJECT OR PHASE CLOSING PROCESS GROUP PROJECT INTEGRATION MANAGEMENT.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Software Project Management
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
The Project Management Process Groups
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Outline Risk Identifying risks to your project Change Managing change for your project.
12-1 ELC 347 project management Day 24. Agenda Integrative Project –Part 6 (page 378) Due –Completed project plan and presentation due December 1.
Chapter 13 Project Termination.
Unit 1 What is Project Management
Systems Analysis and Design in a Changing World, 4th Edition
Project Initiation Chapter 2.
ELC 347 project management
What are the common reasons software development projects fail?
Project Management Processes
TechStambha PMP Certification Training
The process of completing each project procurement
Martha Grabowski LeMoyne College
Project Management for Software Engineers (Summer 2017)
Chapter 13 Project Termination.
Project closeout and termination
SE 3800 Note 10 Project Management
Project Management Process Groups
ELC 347 project management
Project Management Processes
Project Close-Out and Termination
Chapter 13 Project Termination © 2012 John Wiley & Sons Inc.
Project Close-Out and Termination
Project Close-Out and Termination
Project Auditing & Termination
Presentation transcript:

Project Close-Out and Termination Chapter 14 © 2007 Pearson Education

Project Termination All activities consistent with closing out the project  Extinction  Addition  Integration  Starvation

Elements of Project Closeout Management Putting it All to Bed Disbanding the Team Finishing Handing Gaining Acceptance for the Product Harvesting the Benefits Reviewing How The Work Product Over the It All Went

Lessons Learned Meetings Meeting Guidelines Establish clear rules of behavior Describe objectively what occurred Fix the problem, not the blame Common Errors  Misidentifying systematic errors  Misinterpreting lessons based on events  Failure to pass along conclusions

Closeout Paperwork Documentation Legal Cost Personnel

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

Dynamic Project Factors 1.Static 2.Task-team 3.Sponsorship 4.Economics 5.Environment 6.User

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

Early Termination Decision Rules  Costs exceed business benefits  Failure to meet strategic fit criteria  Deadlines are continually missed  Technology evolves beyond the project’s scope

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

Project Termination Issues EmotionalIntellectual ClientStaff ExternalInternal

Claims & Disputes Two types of claims Ex-gratia claims Default by the project company Resolved by Arbitration –Binding –Non-binding Standard litigation

Protecting Against Claims oConsider claims as part of the project plan oVerify stakeholders know their risks oKeep good records throughout the life cycle oKeep clear details of change orders oArchive all correspondence

Final Report Elements  Project performance  Administrative performance  Organizational structure  Team performance  Project management techniques  Benefits to the organization and customer