Day 25 ELC 347/BUS 348/PSA 347.

Slides:



Advertisements
Similar presentations
Facilitated by Joanne Fraser RiverSystems
Advertisements

Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 22.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 21.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Project Closure CHAPTER FOURTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
W5HH Principle As applied to Software Projects
Project Integration Management Sections of this presentation were adapted from A Guide to the Project Management Body of Knowledge 4 th Edition, Project.
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.
Consumer Decision Making and Beyond CHAPTER FIFTEEN.
Chapter 3: The Project Management Process Groups
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.
Project Management for Public Health Professionals February 2011 David Sabapathy, MD, MBA, PEng Department of Community Health Sciences 3 rd floor TRW.
Planning. SDLC Planning Analysis Design Implementation.
Project Closure CHAPTER FOURTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Project Closeout and Termination Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 14 Learning Objectives After completing.
Project Close-Out and Termination
Information Technology Project Management by Jack T. Marchewka Power Point Slides by Jack T. Marchewka, Northern Illinois University Copyright 2006 John.
Project Management Fundamentals Project Organization and Integration
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
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
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
Finishing the Project and Realizing the Benefits Chapter 15 Contemporary Project Management Kloppenborg © 2012 Cengage Learning. All Rights Reserved. May.
Scope Management Chapter 5 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall5-1.
5-1Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Scope Management Chapter 5.
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.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 23.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Last Day.
Welcome to Session 3 – Project Management Process Overview
Scope Management Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 5 Learning Objectives After completing this chapter,
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall o P.I.I.M.T o American University of Leadership Ahmed Hanane, MBA, Eng, CMA, Partner.
Where We Are Now 14–2. Where We Are Now 14–2 Major Tasks of Project Closure Evaluate if the project delivered the expected benefits to all stakeholders.
Chapter 13 Project Termination.
Day 3 in the pmProject Management Project Management (PM) ADJUST.
Project Close-Out and Termination Chapter 14 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall14-1.
Degree and Graduation Seminar Integration Management
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Project Close-Out and Termination Chapter 14 © 2007 Pearson Education.
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 1-1 Organizational Theory, Design, and Change Sixth Edition Gareth R. Jones Chapter.
Chapter 3: The Project Management Process Groups: A Case Study Information Technology Project Management, Fourth Edition Project Execution & Closing Thursday,
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.
12-1 ELC 347 project management Day 24. Agenda Integrative Project –Part 6 (page 378) Due –Completed project plan and presentation due December 1.
 Define and recognize risk  Define the contents of a risk management plan  Conduct a risk identification and prioritization process  Define.
Systems Analysis and Design in a Changing World, 4th Edition
Bus 411 Day 23 Copyright 2005 Prentice Hall.
ELC 347 project management
What are the common reasons software development projects fail?
Project Management Processes
Project Management for Software Engineers (Summer 2017)
Scope management Chapter 5 Copyright ©2016 Pearson Education, Inc.
Scope Management Chapter 5
Bus 411 Day 22 Copyright 2005 Prentice Hall.
Project closeout and termination
Project Management Process Groups
ELC 347 project management
Project Management Processes
Project Close-Out and Termination
Chapter#8:Project Risk Management Planning
Project Close-Out and Termination
Scope Management Chapter 5
Chapter#8:Project Risk Management Planning
Project Close-Out and Termination
Chapter 3 Managing the Information Systems Project
Presentation transcript:

Day 25 ELC 347/BUS 348/PSA 347

Agenda Questions? IP part 6 Due Assignment 8 Corrected Any of the first five sections of the IP project can be resubmitted for rescoring prior to December 13. The recorded score will the average of the original score and the score on the resubmitted section. Please notify me via email which sections you will be resubmitting. Received part 5 & part 1 IP part 6 Due Assignment 8 Corrected 2 A’s, 1 answered wrong questions and 1 MIA Project Closeout and Termination

Remaining Schedule Dec 12 IP Presentation Due (20 Min) “A 15–min Power Point Presentation that is intend to be a pitch to a project “steering” committee that will decide on the fate of the project.” Dec 16 Exam 3 (8 AM to 8 PM) Dec 18 IP Project Due @ Midnight IP Project Peer Evaluations DUE

On time for all group meetings: Put your team members’ names in the spaces provided, one name at the top of each column. Names: Ratings: On time for all group meetings: Helped keep the group cohesive: Number of useful ideas contributed: Quantity of work done: Quality of work done: + Add Total Scores Here:

Project Closeout and Termination Chapter 14 Project Closeout and Termination

Chapter 14 Learning Objectives After completing this chapter, students will be able to: Distinguish among the four main forms of project termination . Recognize the seven steps in formal project closeout. Understand key reasons for early termination of projects. Know the challenges and components of a final project report.

Projects End Naturally or Unnaturally

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 Over the It All Went TIME

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

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

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

Dynamic Factors to Monitor (table 14.1) Static Task-team Sponsorship Economics Environment User

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

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 Figure 14.6 and Table 14.2 Emotional Intellectual Internal External Staff Client

Project Termination Issues - Emotional Staff Client Fear of no future work Change in attitude Loss of interest in remaining tasks Loss of interest in project Loss of project-derived motivation Change in personnel dealing with project Loss of team identity Unavailability of key personnel Selection of personnel to be reassigned Diversion of effort Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

Project Termination Issues – Intellectual Internal External Identification of remaining deliverables Agreement with client on remaining deliverables Certification needs Agreement with suppliers on outstanding commitments Identification of outstanding commitments Communicating closure Control of changes to project Closing down facilities Screening of partially completed tasks Determination of requirements for audit trail data Closure of work orders and work packages Disposal of unused material Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

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 Consider claims as part of the project plan Verify stakeholders know their risks Keep good records throughout the life cycle Keep clear details of change orders Archive all correspondence

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

Summary Distinguish among the four main forms of project termination . Recognize the seven steps in formal project closeout. Understand key reasons for early termination of projects. Know the challenges and components of a final project report.

Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall

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 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 Static Task-team Sponsorship Economics Environment 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

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 Consider claims as part of the project plan Verify stakeholders know their risks Keep good records throughout the life cycle Keep clear details of change orders Archive all correspondence

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