Title | Project Handoff Checklist |
---|---|
Course | Methodologies and Tools For It Project/Service Management |
Institution | Università degli Studi di Salerno |
Pages | 3 |
File Size | 241.8 KB |
File Type | |
Total Downloads | 91 |
Total Views | 150 |
1 2 3...
Project Handoff Checklist
Purpose This document summarizes the handoff requirements for project acceptance.
Maintenance Hand-over Process As projects are being kicked off and targeted for a specific release, the product team uses project lifecycle milestones to gauge the progress of a project, its ability to integrate into the product and its risks to the release itself. The following document outlines the key deliverables that are required to be completed by the projects at the end of three gates (requirements, development and project testing cut-offs). The ability to complete those deliverables by the project is required, and failing to do so on time will be put into consideration by the product team when assessing the risk level of a project.
Exceptions From time to time, situations will arise where it is not feasible for a product-related project to fully comply with the SDLC or to meet all the maintenance handover prerequisites. In these cases, pre-approval for an exception must be sought and accepted. All exceptions must be granted in advance of the project being finalized, i.e. prior to a proposal, CR, SOW, etc. being presented to an existing or potential client. All exception requests must be made to the manager of product development. They must, however, ultimately be approved by the full management team.
Acceptance Acceptance of the above deliverables is at the discretion of the product manager. Irresolvable disputes between a project and the product manager may be escalated to the management team (through the manager of product development) for resolution.
HANDOFF DELIVERABLES REQUIREMENTS CUT-OFF GATE TO DO
ALIGNMENT TO VISION
REQUIREMENTS QUALITY
ADVANCE RELEASE NOTES
DESCRIPTION
Project to have requirements documented in a repository and adhere to the product standards and future vision. The provided list of requirements must be approved by a member of the product team to assure it aligns with both functional and technical roadmap. Project to have the project requirements reviewed by a resource (designated by the product team) to assure the requirements meet the complete business needs. Project must supply marketing material for advance release notes (ARN).
DELIVERABLE
STATUS
COMMENTS
Product Approved Requirements
Please do not hesitate to get guidance from the product team as you proceed with documenting your requirements.
Peer-reviewed requirements
The product team may choose to designate a resource outside the product team.
Word document including illustrations, where applicable
ARN are published to clients after requirements cut-offs
DEVELOPMENT CUT-OFF GATE TYPE
DESIGN
DESCRIPTION
DELIVERABLE
STATUS
COMMENTS
Reference to design document
DEVELOPMENT TESTING COVERAGE
Project confirms that repository has been updated as appropriate, including reference to the design documents Unit test cases checked in and unit test results are documented
Spot test inventory and results
Quantity is not as important as quality of tests
REQUIREMENTS TESTING COVERAGE
Assure test cases are documented and provide testing coverage
QC approved test plan and test cases
TECHNICAL DOCUMENTATION
Initial review of project changes to the: configuration, deployment and installation procedures changes Project to provide draft user documentation (user manual, admin guides and online help) impacts
CM approved deploy and configuration documentation
By test plan, we don’t expect necessarily an actual document but at a minimum an understanding of the number of cycles and the awareness of what is out of scope in your testing To facilitate both the future delivery of date environments as well as project implementations
USER DOCUMENTATION
Reference to the draft documentation
PROJECT TESTING CUT-OFF GATE TYPE
DESCRIPTION
DELIVERABLE
TESTING RESULTS
Provide the project testing results by testing by cycles (pass, fail, deferred)
TEST ASSET
Provide complete list of product assets that were developed to assure proper testing
Asset list and SVN location
KNOWLEDGE TRANSFER
Session with at least one QC representative to assure their ability of testing new requirements
Session completed
USER DOCUMENTATION
Project to provide final documentation: user documentation (user manual, admin guides and online help) impacts
Reference to the documentation
Reference to results
COMPLETE (Y/N)
COMMENTS
This includes a list of outstanding defects that have been added to the ticketing system Those assets need to be usable in date build QC should be expected to be able to test your project requirements with minimal input from your project...