Master Project Plan Check List
March 11, 2010|
Project Code |
Project/Application Name |
Project Acronym |
||
|
Project Coordinator |
QCC |
Date Received |
Date Completed |
|
| Document Section | Description | First Review | Second Review | Third Review |
| Mandatory Checks | ||||
| Does the cover page identify the Application with its Name and Project Code? | ||||
| Have the appropriate Authorities approved this deliverable (via signature or appropriate email approval)? | ||||
| Is the Revision History current? | ||||
| Is the Scope clearly stated and consistent with the content of other deliverables? Are the Out-of-Scope items clearly stated? |
||||
| Are the Assumptions clearly denoted including if confirmed or not? | ||||
| Have Constraints been discussed? | ||||
| Is the Project Organization section and associated chart complete? | ||||
| Is there a plan to document all important Communications and to introduce into permanent record? Is there a Distribution List for various topics? | ||||
| Has the Risk Management process to be used been explained? | ||||
| Is there a Process defined and Forum and Schedule for addressing and managing Issues? | ||||
| Is there a Process for Requesting Changes and Tracking Approved Changes into documentation and application? | ||||
| Within document or by reference, is there a Configuration Management (CM) Process overview? If concurrent projects will be performed, how will CM manage/control multiple change environments? | ||||
| Is Responsibility and Accountability assigned for all deliverables? | ||||
| Have the Work Descriptions (specifically for Project Initialization and Site Readiness) been completed? | ||||
| Optional Checks > | ||||
Is the overall Content of this deliverable reasonable?
Is the list of additional Reference Materials included?
Review results for due diligence:
| First Review | Second Review | Third Review | |
| Pass/Fail |
Master Test Plan Check List:
| Project Code | Project/Application Name | Project Acronym | ||
| Project Manager | Reviewer Name | Date Received | Date Completed | |
| Document Section Found in | Description | Rev 1 | Rev 2 | Rev 3 | |
| Mandatory Checks | |||||
| Does the cover page identify the Application with its Name and Correct Project Code? | |||||
| Is the Revision History current? | |||||
| Have the appropriate Authorities approved this deliverable (via signature or appropriate email)? Was the Senior Mngr. approval form submitted with the document? | |||||
| Is there a context diagram and application description depicting the application (or application components) and the boundary interfaces? | |||||
| Does the scope identify the type of tests to be performed and the rationale for the test types that are considered out-of-scope? | |||||
| Does the approach identify the functional test coverage and the groups responsible for the functional testing? | |||||
| Is the number of components by type, and the number of components to be tested identified? | |||||
| Are the minimum dates testing requirements incorporated? | |||||
| Have testing policies been described or referenced? | |||||
| Are assumptions identified and confirmed? | |||||
| Are dependencies identified along with a plan to ensure coordination? | |||||
| Are constraints identified along with a plan to work-around? | |||||
| Are the risks reflective of the stated scope and approach, and the assumptions, dependencies and constraints? Are appropriate risk mitigation plans identified and being implemented? | |||||
| Are responsibilities identified for all phases of the testing process? | |||||
| Has the test environment been defined? | |||||
| Have test tools been identified? | |||||
| If required, is there a description of the security requirements associated with testing? | |||||
| Is there a detailed plan for the creation of test data, and for that data satisfying the test requirements? Are required tools/computer-aids included in the plan? | |||||
| Is there a plan for the aging of test data, and for that data satisfying the test requirements? Are required tools/computer-aids included in the plan? | |||||
| Is there a plan for restoring test data? | |||||
| Is there a detailed plan for the management of test data, including responsible group and a description of the method/process? | |||||
| Is there a plan for managing the configuration of all application components and files during the testing process? | |||||
| Is a process for management of defects described or referenced? | |||||
| Is an approach described for the management of all test documentation? Are specifics provided regarding the structure and naming conventions of a repository? Has data retention been addressed? | |||||
| Is there a Quality Assurance plan to provide confidence that testing is effective? | |||||
| Is there a process for periodic reporting of test status? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for Touch-Point Testing? Are test scenarios and test cases defined? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for Unit Testing? Are test scenarios and test cases defined? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for Software Inspection? Are test scenarios and test cases defined? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for String Testing? Are test scenarios and test cases defined? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for Baseline System Execution Before Conversion? Is there a criteria for selecting a representative processing cycle? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for Baseline System Test After Conversion? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for System Test After Retrofit? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for Integration Testing? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for Production Parallel Testing? | |||||
| If applicable, are objectives, approach, scope, entrance/exit criteria and deliverables addressed for Y2K Test? | |||||
| Based on the information in the plan, are you knowledgeable of what types of test are being conducted and the rational behind the elimination of any tests that are expected? | |||||
| Is the initial testing schedule defined? | |||||
| Have Y2K test scenarios and conditions been developed and individually listed alongside the appropriate scenario in Appendix B? | |||||
| Has an Appendix D been attached that shows the detailed test plans, corresponding to the test scenarios listed in appendix B. | |||||
| Overall Review Checks | |||||
| Is the overall Content of this deliverable reasonable. | |||||
| Is the information contained herein, consistent with that of the project plan? | |||||
| Are the test conducted and subsequent results consistent with the initial information in the beginning of the plan? | |||||
| Do you feel confident that the application was converted and tested properly, based on all information presented in the test plan, and that due diligence requirements for this application have been satisfied? | |||||
Review results for due diligence:
| First Review | Second Review | Third Review | |
| Pass/Fail | |||
| Date | Date | Date | |
| Entered in Database | |||
| Copied to SHAREPOINT Server |