1 / 64

Project Closure

Project Closure. May 6 th , 2014. …recap::Integrated Change Control. Part of the Project Integration Management Knowledge Area:

brac
Download Presentation

Project Closure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Closure May 6th, 2014

  2. …recap::Integrated Change Control • Part of the Project Integration Management Knowledge Area: • Develop Project Charter, Develop Preliminary Project Scope Statement, Develop Project Management Plan, Direct and Manage Project Execution, Monitor and Control Project Work, Integrated Change Control, and Close Project 2

  3. …recap::PMProcess Group Integrated Change Control and all processes in the Project Integration Area are coordinated within the Project Management Process Groups 3

  4. …recap::Definition ICC is the process necessary for controlling factors that create changes to make sure those changes are beneficial, determining whether a change has occurred, and managing the approved changes, including when they occur. 4

  5. …recap::Timing ICC process is performed throughout the project, from project initiation through project closure. 5

  6. …recap::CMMI – Configuration Management The purpose of Configuration Management (CM) is to establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits. 6

  7. …recap::RUP CCM Workflow 7

  8. …recap:: CCM Conclusions • What are CCM objectives? • Managing change is more than just checking-in and checking-out files. It includes management of workspaces, parallel development, integration, and builds. • Which are the main topics for CCM? • Coordinating the Activities and Artifacts • Coordinating Iterations and Releases • Coordinating Changes to Software 8

  9. …recap:: CCM Conclusions • When CCM is established? • Often institutionalized or established early on in the project lifecycle • CRs, can be raised at any time during the course of the project • Who is responsible for CCM? • Change Control Manager/Configuration Manager • Anyone on the project staff should be able to raise a Change Request 9

  10. …recap:: CCM Conclusions • Who tells us how CCM can be done? • In PMBOK it is ICC • In CMMI it is CM • In the Rational Unified Process, the Configuration & Change Management Discipline 10

  11. Today’s topic Project Closure 11

  12. References PMBOK Managing Iterative Software Development Projects by Kurt Bittner, Ian Spence CMMI RUP 12

  13. Project Lifecycle 13

  14. Why Project Closure? Without a formal closure process, project teams can fail to recognize the end, and then the project can drag on—sometimes at great expense Closure must be done both on project completion and cancelation

  15. What does project closure? Outcomes match the stated goals of the project (when completion is achieved) Customers and stakeholders are happy with the results Critical knowledge is captured The team feels a sense of completion Project resources are released for new projects

  16. Team • One of the highest benefits from project closure is releasing the team • Formal • Post mortem 16

  17. The Project Closure Phase The last phase of the Project Life Cycle Determined by the completion of all Project Objectives and acceptance of the end product by the customer The outputs from Project Closure Phase is input to execute the next projects with much more efficiency and control

  18. Project Closure 18

  19. PMBOK – Closing Process Group • Includes the processes to • Formally terminate all activities of a project or project phase • Hand over the project to maintenance teams • The project can be either completed or canceled 19

  20. Closing Process Group • Contains two processes: • Project Closure: This is the process necessary to finalize all activities across all of the Process Groups to formally close the project or a project phase. • Contract Closure: This is the process necessary for completing and settling each contract, including the resolution of any open items, and closing each contract applicable to the project or a project phase. 20

  21. Project Closure Procedures • Administrative Project Closure includes: • Integrated activities to collect project records • Analyze project success or failure • Gather lessons learned • Archive project for future use 21

  22. Project Closure Procedures • includes: • Product Verification - Work completed correctly and satisfactory • Administrative Closure – Updating contract records to reflect final state and prepare them for archiving • Input for the Contract Closure Process 22

  23. Project Closure Inputs Project Management Plan Contract documentation Enterprise environmental factors Organizational process assets Work performance information Deliverables 23

  24. Inputs: Contract Documentation • Used to perform the contract closure process • Includes • The contract itself • Changes to the contract • Other documentation (such as the technical approach, product description, or deliverable acceptance criteria and procedures). 24

  25. Inputs: Enterprise environmental factors Organizational or company culture and structure Governmental or industry standards Infrastructure Existing human resources Personnel administration Company work authorization system Marketplace info, stakeholder risk tolerance… 25

  26. Inputs: Organizational process assets • Organization’s processes and procedures for conducting work • Standardized guidelines, work instructions, proposal evaluation criteria, and performance measurement criteria, templates… • Organizational corporate knowledge base for storing and retrieving information • Process measurement database, project files,… 26

  27. Inputs: Work performance information Schedule progress Deliverables that have been completed and those not completed Schedule activities that have started and those that have been finished Extent to which quality standards are being met Costs authorized and incurred … 27

  28. Project Closure Outputs Administrative Closure Procedure Contract Closure Procedure Final Product, service or result Organizational process assets (updates) 28

  29. Outputs: Administrative Closure Procedure • All procedures and roles involved in administrative closure • Procedures for transfer to production • Action and activities for stakeholder approval • Confirmation of goals achievement (sponsor, client, stakeholders, etc) • Actions for satisfying all exit criteria 29

  30. Outputs: Contract Closure Procedure • A step-by-step methodology addressing: • Terms and conditions of the contracts and any required completion or exit criteria for contract closure • Activities and responsibilities of the project ALL team members involved in the contract closure process • Actions performed to formally close all contracts associated with the completed project 30

  31. Output: Final Product, Service or Result Formal acceptance and handover of the final product, service, or result that the project was authorized to produce The acceptance includes receipt of a formal statement that the terms of the contract have been met 31

  32. Output: Organizational Process Assets Formal Acceptance Documentation Project Files Project Closure Documents Historical Information 32

  33. Close Process Tools Project Management Methodology Project Management Information System Expert Judgment 33

  34. Before Tailoring Project Closure Understand Iteration Closure Phase Closure … and then Project Closure 34

  35. Iteration Closure Iteration is concluded by the iteration acceptance review, where the formal result of the iteration is agreed upon and recorded This involves considering the results of the iteration and analyzing their impact on the project as a whole 35

  36. Iteration Closure: Measurement and Analysis Absolute progress Risk exposure Estimate to complete Effort profile Cost profile Effort Expended Find/fix rate (tolerance) Defect trends (tolerance) 36

  37. Iteration Closure: Acceptance Review Results Risks Objectives Requirements Adherence to Plan Lessons Learned Rework, external changes, feedback from demo, other deliverables… 37

  38. Iteration Grades Exceptional Passed Passed at risk Unfinished Failed Abandoned 38

  39. Iteration recommendations • For Unfinished, Failed or Abandoned we can have the following recommendations: • Re-plan • De-scope • Extend • Try again • Cancel 39

  40. Acting on Iteration assessment results Never confuse the map with the journey Adopt an attitude that continuous planning is good Mature your process alongside your team Be prepared to cut your losses Be honest 40

  41. Phase Assessment • Differences from iteration assessments: • Judge the project, not a single iteration • Always decide whether to continue or cancel the project • Focus on the delivered value rather than on performance • Assess project against the business case 41

  42. Phase Assessment topics Progress Risk Scope Baseline Performance Plans Business Case 42

  43. Phase Assessment approaches Formal Phase Assessment Extend Iteration Assessment 43

  44. Concluding a Phase Passed Passed at risk Failed 44

  45. Project conclusions Approved Temporary approved Extended Paused Postponed Canceled 45

  46. Project Assessments • Performed not only at project closure • Cover for: • Handle exceptions raised by the iteration assessments • Phase assessments are too far apart • Provide review points for the overall project (might include non-software subprojects) 46

  47. Assessment objectives [1] Confirm that the need for the project has not changed Satisfy the stakeholders of the quality of the products delivered by the project Confirm that the business case is still viable 47

  48. Assessment objectives [2] Authorize the continuation or cancellation of the project Assess the benefits that the project has delivered Assess the overall effectiveness of the project 48

  49. Transition planning

  50. 1. Has the product been implemented and is it producing the expected benefits? 2. Have all deliverables been completed and implemented? If not, has accountability for outstanding items been assigned? 3. Have new workflows and procedures been documented, tested and implemented? 4. Have all outstanding issues been resolved or assigned owners? 5. Have hardware, software and other components been installed?

More Related