| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Conduct Lessons Learned activity in the Post-Deploy phase is to ensure improvement opportunities from the project experience are identified, documented and shared with other project managers so that the organization can use historical information to improve the GIS PMP process, improve future project performance and mitigate risks and issues on future projects.
Lessons learned is a facilitated session with project team members and customers to identify, analyze and document what worked well and not so well during the project. Participants recommend changes/actions determined from the session.
The project manager is responsible for coordinating and documenting the session as well as ensuring that action items are documented and tracked to closure.
Set up meeting to review the project. Invite project team members, sponsor, requestor and other stakeholders.
Lessons learned sessions can be held throughout the project life cycle as applicable. However, a lessons learned session is required by the GIS PMP in the post-deploy phase of a completed project or when a project is cancelled.
The template is required so that the PMO has a consistent format to gather and analyze data to focus process improvement activities and so that the lessons can be shared easily among project managers.
The participants must reach consensus on each score.
Follow detailed instructions located in the Lessons Learned template.
Lessons Learned are filed at: G:\BET\Projects\1- Lessons Learned.
Review test deliverables and submit any best practice candidate materials and process changes to the Testing SME function by placing them in the appropriate file location at G:\BET\Testing Repository\Best Practice Candidates.
NOTE: The statistics tab is used in the monthly project reviews.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
Objectives:
The purpose of the Obtain Project Acceptance Signoff activity in the Post-Deploy phase is to ensure that the sponsor, requestor and the project manager are in agreement concerning the accuracy of the project measurements so that the project can be officially closed.
This activity is the final signoff required on the project and indicates the official closure of the project.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Close Project activity in the Post-Deploy phase is to officially close the project so that all resources are officially released from the project.
This activity includes all tasks which need to be completed to close down the project. NOTE: Some of these tasks may occur earlier in the project, for example, if contractors are no longer needed, they should be released when their work is complete.
Below is a list of tasks which may need to happen (this should not be considered a complete list but rather a place to start):
Release contractors
Return temporary equipment used by the product team (PCs, telephones, etc.)
Update all project documents - some examples are:
Close out action items
Update schedule
Complete checklists where necessary
Archive project documents (see communication management)
Review testing deliverables and submit any best practice candidate materials and process changes to the Testing SME function by placing them in the appropriate file location at G:\BET\Testing Repository\Best Practice Candidates.
Archive project testing deliverables per the Test Repository Process:
Testing materials developed in the Mercury Test Director tool will remain in the tool
Testing materials developed and stored in the project folder will be archived with the rest of the project folder documentation
Submit final project status report reflecting the completed status and providing all completion information (actual deploy date, actual cost, implemented requirements, actual effort and number of defects identified during the Post-Deploy phase)
Update the resource capacity planning sheet
Distribute the Customer Satisfaction Survey to the project sponsor and requestor
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
Objectives:
The purpose of the Reward Team activity in the Post-Deploy phase is to reward and recognize the project team (and others who played a significant role) for their contributions.
Have fun.