| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
|
Objectives:
The purpose of the Conduct Release Test activity in the Deploy phase is to ensure that a set of standard tests of end-to-end business processes produce the expected results with the new product being released so that when the product is migrated to the production environment it doesn’t break existing functionality.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Finalize Maintenance & Support Turnover Documentation activity in the Deploy phase is to review and update the system documentation created in the Develop & Test phase so that the maintenance & support team will have the information if and when it is needed. The Maintenance & Support Turnover plan should also be reviewed to verify that all turnover tasks have been completed.
This activity is the verification that all tasks identified in the Maintenance & Support Turnover Plan have been completed. This includes, but is not limited to updating or creation of the application disaster recovery report and updating or creation of the WORP page. The project team is responsible for completing these tasks with the assistance of maintenance & support and business continuity team members.
All project documentation must be made available to the production support team. Review the PMP Checklist to see the specific documentation that may be requested by the maintenance & support team.
Related Links:
Link to Application Disaster Recovery Process
Link to WORP Process
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Finalize & Execute the Business Rollout Plan activity in the Deploy phase is to finalize the Business Rollout Plan created in the Develop & Test phase and execute according to the plan so that there is a smooth integration of the product into each of the affected business areas and that it aligns with business area standards and procedures.
This activity includes all tasks which need to be completed for a successful product launch with the business users. This activity is coordinated by the project manager but must be directed by the business lead to ensure the business needs are addressed. It is important to note that there are times when multiple business rollout plans will be required, for example, when a product is being deployed to one region at a time.
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):
Training
Training logistics (travel, room setup, etc.)
Communication
Update processes, procedures, flow charts, SORCAs
Update roles and responsibilities
New equipment setup
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Finalize & Execute the Technical Implementation Plan activity in the Deploy phase is to finalize the Technical Implementation Plan created in the Develop & Test phase and then execute according to the plan so that the deployment goes smoothly.
This activity includes all tasks which need to be completed for a successful product launch in the technical environment. This activity is coordinated by the project manager but the project team must provide the detailed tasks, durations, dependencies and roles.
The project manager might choose to build a separate deployment schedule using MS Project to be used at this critical point during the project life cycle.
It is important to note that there may be times when multiple implementation plans are required, for example, when a product is being deployed to one region at a time.
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):
Setup production environment
Initial and date required project documentation entries in the PMP Checklist (highlighted in red). This is an audit requirement to confirm that the required project documentation has been created (or updated), is complete and accurate at project deployment.
Production change control (Tuesday prior to planned move to production)
Data conversions
Setup of business users environment
User access
Deployment notification
Contingency plan
Move to production (who does what and when, dependencies or a specific order in which code/modules must be migrated, etc.)
Setup war room if applicable
Identify maintenance and support team members and how the product will be turned over to them
Identify and develop production validation tests
Setup training environment
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of Conduct Deploy Quality Audit in the Deploy phase is to review the project folder to ensure that all required documentation exists and is stored correctly so that GIS standards will be met.
The quality audit consists of the following steps:
The project manager completes the quality audit request form and sends it to Quality Assurance (QA).
The audit consists of a review, by Quality Assurance, of the project documentation to verify that:
All required documents have been created and stored in the appropriate project sub-folders
The documents comply with GIS standards
The project manager has signed off on all required documents in the PMP Checklist.
Currently this is an independent audit and does not require the project manager's presence.
Once the audit is completed, a compliance audit report is produced and sent to the project manager.
The QA Corrective Action template is used by the project manager to document steps taken to resolve the non-compliances. This report must be completed with all action items closed, and sent back to Quality Assurance within 30 days after receiving the compliance audit report before escalation occurs.
These reports are used to provide periodic summary reporting for GIS management.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Conduct Readiness Review activity in the Deploy phase is to ensure that all key stakeholders understand the status of the project and product and based on that status, approve the product so that it can be moved to production.
Status should not be a surprise to the stakeholders at this point, but merely dotting the “i’s” and crossing the “t’s”. It is a final check that everything is ready and nothing has been overlooked. The project manager is responsible for coordinating the review and obtaining approval to move forward. This activity is a formal gate review which is performed in two steps – an internal review and an external review. It includes a review of open issues, open test items (reports from TestDirector), risks, and status of business rollout plan and technical implementation plan. Projects with any severity 1 or 2 issues from the customer's point of view can not deploy until those issues are resolved. The project team can decide to be MORE rigid on this rule but the project must meet this requirement.
Prior to the internal review, architects should review and verify the architectural implementation in a pre-production environment. See Green Team Process for more details.
Project manager coordinates and facilitates the review. Those invited to this review should be:
Project team
Affected GIS Managers
TDMs
Infrastructure team leads
CAROT representatives
Review open issues, open test items, risks, and status of business rollout plan and technical implementation plan.
Issues are documented and addressed (tracked to closure).
Meeting minutes* and action items are documented and distributed.
NOTE: The internal review is conducted before the external review.
Project manager coordinates and facilitates the review. The sponsor, requestor, business users and other stakeholders are invited.
These reviews are not technical in nature, but focus on the business.
Issues are documented and addressed (tracked to closure).
Meeting minutes* and action items are documented and distributed.
Project manager obtains the sponsor and requestor’s approval to move to production.
* Meeting minutes must include the following information and a copy of the meeting minutes distribution list must be filed in the "Deploy" project folder:
Date
Name of meeting
List of attendees (including those on the phone)
Decisions
Action items - evidence that they were tracked to closure
Action
Assigned To
Status
Target Date
Actual Date
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
Objectives:
The purpose of the Move to Production activity in the Deploy phase is to move the product to production so that the intended users have access to the product.
The technical implementation plan is the key component to this activity. It will ensure that all tasks occur in the proper sequence and at the proper time.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Validate Production activity in the Deploy phase is to ensure that the new product is working in the production environment as expected so that users do not encounter technical issues.
A small group of business users or project team members run through the production validation tests to ensure everything is working properly. This production validation test should be more than just verification of file moves. It is also important to verify business functionality at this time before general availability is announced. If problems are encountered, the appropriate team members or other technical personnel need to be contacted to research and fix the issues. If problems are encountered, the testing and fixing will be an iterative process. Stakeholders should be notified of problems and kept apprised of the status until issues are resolved. If serious enough problems exist, it may be necessary to implement the project's contingency plan (a component of the Technical Implementation Plan).
Confirm migrations, conversions, and configuration changes were completed successfully
Test the migration of the system to production including proper installation and configuration, operational support procedures and processes, and ability of the system to meet defined service level agreements
Validation of business functionality of the system in production
Test access control for each user group
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
Objectives:
The purpose of the Handoff to Maintenance & Support Team activity in the Deploy phase is to pass the ongoing support of the product to the Maintenance & Support team so that if issues arise, they will be ready to assist users with issues.
Communication that the product has successfully been moved to production is the “trigger” for the Maintenance & Support Team to take over ongoing support of the product. The Maintenance & Support Turnover plan should contain all requirements for the final turnover.
NOTE: Sometimes the Maintenance & Support Team is the project team for a defined period of time.