IV

519 views
478 views

Published on

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
519
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

IV

  1. 1. Project IV&V Statement of Work Template STATEMENT OF WORK Independent Verification and Validation Review Services Date: Month Day, 20XX Entity: (State Agency Name) User Contact Information: (Project Sponsor’s Name), Project Sponsor (Street Address) (City, State, Zip) Phone: (Telephone Number) Project: Independent Verification and Validation Review Services for the (Project Name) Project Introduction: (Provide a short history of the project, including any pertinent dates.) (Provide a brief description of the project solution (e.g., in-house development, contractor development, COTS implementation, etc.), as well as a description of the extent of the project effort (e.g., work locations, implementation locations, etc.)) (Provide a statement of the Project Sponsor’s determination of the complexity of the project (i.e., high, medium, or low), as well as, a description of the project’s management and oversight structure and composition.) Scope of Work: This Statement of Work (SOW) defines the IV&V Review Services required by the (Agency Name) in support of the (Project Name) Project. This definition includes the periodicity of the IV&V Reviews and a description of the IV&V tasks to perform during the course of each review. The IV&V Review of the (Project Name) Project is not to be a continuous, integral process within the project itself. Rather, it is a periodically performed, adjunct activity that does not fall within the day-to-day managerial oversight or control of the (Project Name) Project Management Team. Respondents to this Statement of Work (SOW) should not view their role as providing a “continuous presence” within the (Project Name) Project, such as might be the case with Quality Control and Assurance services. 1
  2. 2. The IV&V Service Provider will provide detailed, structured reports of findings of deficiencies and recommendations for their remediation to the Project Sponsor and the Project Management Division (PMD) of the Virginia Information Technologies Agency (VITA). The Project Sponsor will distribute copies of the reports to the Internal Agency Oversight Committee (IAOC) and Project Manager; PMD will distribute copies to the (Secretariat Name) Oversight Committee, the Commonwealth Chief Information Officer (CIO) and Information Technology Investment Board (ITIB). In addition, the IV&V Service Provider will make presentations to the IAOC; the PMD will forward copies of such presentations to the (Secretariat Name) Oversight Committee, the CIO and ITIB. The IV&V Service Provider will provide periodic, independent analyses of the IV&V Review Areas identified in Attachment 1 by accomplishing the corresponding IV&V Task Items identified in Attachment 2. These analyses will serve to identify, inform and educate the project team, and the various oversight agencies, committees and boards of any areas of weakness and risk to the project, as well as the proposed and recommended solutions for their remediation and/or mitigation. Reports and presentations will address technical, financial, and managerial aspects of the project at specified critical milestones. The required minimum IV&V Reviews are shown in the following table: Task Deliverable Time Period Develop an IV&V Review Plan To be completed within 15 business days IV&V Review from the date the IV&V Service. Plan Provider is notified of IV&V Task Order approval. Conduct Initial Initial IV&V Review To be completed at the completion of the IV&V Review Report detailed project plan and preferably before project execution begins. 2
  3. 3. Task Deliverable Time Period Conduct In- In-Progress IV&V For High Complexity Projects: At a Progress IV&V Review Report(s) minimum, projects that have a duration Review(s) of less than 9 months, one in-progress review during project execution is required. Projects that have a duration of greater than 9 months require quarterly reviews (at a minimum). If testing is a component of the high complexity project, then a System and Acceptance Test Planning and Execution IV&V Review and Report are required prior to product implementation. For Medium Complexity Projects: At a minimum, one in-progress review during project execution. Projects with schedules that are greater than 18 months duration will schedule semi-annual reviews. For Low Complexity Projects: In- Progress IV&V Reviews are not required. Conduct a Project Closeout IV&V At project closeout to validate the Project Review Report completion of the project. Closeout IV&V Review Post No Specified Format An optional review and report that Implementation contracting agencies may wish to engage Review IV&V service providers to perform 6-12 months after project closeout. This review focuses on the results and impact of the project deliverables as they relate to the business. In addition, the Project Sponsor and the IV&V Service Provider may agree to include additional reviews as necessary. Deliverables: For each IV&V Review Area evaluated, the IV&V Review Report should contain the status of the (Project Name) Project, including any pertinent historical background 3
  4. 4. information. The report should also contain a detailed analysis of each applicable IV&V Review Area, which answers at least the following questions: • What are the current processes, procedures, practices and technology? • What is good about the current processes, procedures, practices and technology? • What about the current processes, procedures, practices, and technology needs improvement? • Is there measurable progress since the last IV&V Review? • Is the project within established budget, schedule and performance parameters? • What standard is the development organization following (Commonwealth, industry best practice (IEEE, SEI, ISO, etc.), internal agency, contractor)? • Is the project documentation accurate and up-to-date? The IV&V Service Provider should quantify responses to the above questions whenever possible. The IV&V Review Report should contain findings, both positive and negative. The IV&V Review Report should also contain detailed recommendations in each IV&V Review Area specifying what (Agency Name) and/or (Development Organization Name) can do immediately and in the long term to improve the success probabilities of the project. Any technologies, methodologies, or resources recommended should reflect industry “best practices” and be appropriate for the unique circumstances and constraints of the (Project Name) Project. The recommendations should also specify a method of measuring progress against the recommendations. The in-progress IV&V Review Reports should also contain any additional and/or modified recommendations at the same level of detail as the initial recommendations. All findings and recommendations should be traceable (with a clear and consistent method of identification/numbering) from the time first reported by the IV&V Service Provider until closure. The IV&V Service Provider should provide details specifying what (Agency Name) and/or (Development Organization Name) is doing that can be recommended as a best practice for the Commonwealth. Additionally, primarily at project closeout IV&V reports, a description of lessons learned from (Agency Name) and/or (Development Organization Name) should be provided. Where applicable, the IV&V Review reports should be prepared consistent with the template provided as Attachment 3. When the template is not applicable, the Project Sponsor must approve the methodology and processes used in the analysis and preparation of the report prior to its use and the IV&V Service Provider should provide a description of the methodology and processes in the final deliverable. All IV&V Review related standards, processes, procedures, plans, and applicable reference material should be available upon request. The IV&V Service Provider will deliver final copies of all deliverables simultaneously to the Project Sponsor and to the PMD on the delivery schedule provided in the following table. 4
  5. 5. TASK DELIVERABLE DUE DATE Develop IV&V Plan IV&V Plan (Date) Conduct Detailed Project Detailed Project Plan (Date) Plan IV&V Review IV&V Review Report Conduct In-Progress In-Progress IV&V Review (Dates) IV&V Reviews Reports Conduct Test Planning Test Planning and (Dates) (if not coincident with the delivery of one of the In- and Execution IV&V Execution IV&V Review Progress IV&V Review Reports) Reviews Reports Conduct Closeout IV&V Closeout IV&V Review (Date) Review Report Prepare and deliver Formal presentations on Coincident with reports and as required, with at least ten (10) presentations to IAOC each Review Report business-days notice. The Project Sponsor reserves the right to extend the due date of any deliverable if appropriate, due to document size, schedule or changes in scope. The IV&V Service Provider must notify the Project Sponsor of any anticipated delay of a deliverable, as far in advance of the due date as possible. The IV&V Service Provider should provide all deliverables in hardcopy form and in electronic form, using the following software standards (or lower convertible versions): DOCUMENT TYPE FORMAT Text Document Microsoft Word 2003 Spreadsheets Microsoft Excel 2003 Microsoft PowerPoint Presentation 2003/Visio 2003 Project Management Microsoft Project 2002 Schedule: Event Date Release SOW (Date) Response Due (Date) Award Decision (Date) Work Begins (Date) Acceptance: The Project Sponsor will accept or reject the individual IV&V Review Reports and Presentations. The IV&V Service Provider will provide draft reports and presentations to the Project Sponsor prior to release of the final versions. The Project Sponsor cannot approve, modify, or reject a report prior to submission but may provide comments and feedback on drafts within five (5) business days of receipt of a draft. The IV&V Service Provider will submit final draft reports to the Project Sponsor for final deliverable acceptance. The Project Sponsor will review and return comments within five (5) business days of receipt of each final draft report. The IV&V Service Provider will then submit final reports within two (2) business days. 5
  6. 6. The Project Sponsor shall not unduly withhold acceptance of deliverables. The Project Sponsor must approve all deliverables. In all cases, payment to the IV&V Service Provider will be contingent upon the Project Sponsor approval of each deliverable. No IV&V Review will be complete until the Project Sponsor has received and approved all review-related documentation. Each respondent to this SOW must include a description of the actions it will take to produce the deliverables and obtain approval. The Project Sponsor must approve, in writing, changes to milestones, deliverables or other material changes to the task order prior to implementation of any changes. Conflict of Interest Exclusion: Any contractor (and its subcontractors) serving in the role of an IV&V Service Provider for the (Project Name) Project is prohibited from soliciting, proposing or being awarded any initiation, planning, execution and control or closeout phase work (excluding IV&V services) on the (Project Name) Project. Personnel: Respondents to this SOW must include the experience and skills of representative personnel who the respondent would propose as members of the IV&V Team for the (Project Name) Project. The respondent and (Agency Name) agree that qualified and experienced personnel are critical to the performance of an IV&V Review and that they will not be removed from this task without prior approval from (Agency Name) and that (Agency Name) will have the right of refusal for any personnel assigned to the IV&V Team. After task award, the IV&V Service Provider shall secure written approval from (Agency Name) prior to making any changes in IV&V Team personnel. The IV&V Service Provider will notify (Agency Name), in writing, of any changes in the personnel assigned to the IV&V Team. The qualifications of new personnel should be comparable with those of the replaced personnel. After task award, (Agency Name) may request replacement of IV&V Team personnel. Such requests will be in writing. Respondents to this SOW must include the experience and skills of representative personnel who the respondent would propose to perform an IV&V Review of a major IT project. These personnel must have a minimum of thirty-six (36) months cumulative experience within the past seven (7) years performing the duties necessary to complete one or more phases (e.g., project management, planning, development, testing, implementation) of a full system, product or service development lifecycle. At least 50% of the IV&V Team Members must have a minimum of twenty-four (24) months cumulative experience within the past seven (7) years performing audit level IV&V reviews. At least one IV&V Team Member must have a Project Management Professional (PMP) Certification. At a more detailed level, the IV&V Team personnel must collectively demonstrate the knowledge and experience to: 6
  7. 7. • Review the technical, financial and management aspects of the project in relationship to the project management policies, standards and guidance of the Commonwealth of Virginia. •Analyze project management; Work Breakdown Structure development and execution, schedule development and execution, resource planning and management, budget formulation and execution, workflow management and reporting, progress tracking. •Review and analyze project management planning documents; e.g., Project Plan Executive Summary, Project Performance Plan, Work Breakdown Structure, Resource Plan, Project Schedule, Budget Plan, Procurement Plan, Risk Management Plan, Communications Plan, Change and Configuration Management Plan, Quality Management Plan. •Review and analyze project, product development documents; e.g., Project Status Reports; Change Control Requests; Issue Log; and Issue management documentation. •Review and monitor development processes, procedures and practices to ensure they are documented, implemented, and analyzed for improvement. •Assess the project’s Configuration Management function by reviewing CM reports and making recommendations regarding appropriate processes and tools to manage product changes. •Assess the project’s Quality Management function by reviewing QM reports and making recommendations regarding appropriate processes, procedures, practices and tools to assure product quality. •Assess the project’s Risk Management function by reviewing RM reports and making recommendations regarding appropriate processes, procedures, practices and tools to manage product planning, development, and implementation risks. •Perform a detailed review of project deliverables and acceptance criteria for accuracy, completeness, and adherence to contractual and functional requirements. •Perform a detailed review of the product documentation (Requirements, Design, Training, Test, and Management Plans, etc.) for accuracy, completeness, and currency. •Perform a detailed review of the product architecture for feasibility, consistency, and adherence to industry, Federal or Commonwealth standards. •Inventory and review application software, for completeness and adherence to programming standards for the project. 7
  8. 8. •Analyze application, network, hardware and software operating platform performance characteristics relative to expected/anticipated/contractually guaranteed results and industry standards. •Review the processes, procedures and practices used within the project for tracking business and technical requirements to their source and review the processes, procedures and practices established during the planning phase for requirements traceability throughout the subsequent development and implementation phases. Review the traceability of product requirements through the design, development, testing, and training tasks of the project. •Assess and recommend improvement, as needed, to assure the planned operations and maintenance performance of the product. •Assess and recommend improvement, as needed, to assure product testing is being performed adequately through review of test plans or other documentation and through direct observation of testing where appropriate. •Assess and recommend improvements, as needed, to assure appropriate user and developer training is planned and accomplished. •Review product hardware and software configurations and report on any compatibility and obsolescence issues. •Review and analyze product performance studies to determine if the product is performing as planned. •Effectively document IV&V Review findings and recommendations, observed best practices and captured lessons learned. It is desired that each IV&V Team Member possess the following: •A minimum of 4,000 hours experience within the past ten (10) years in risk assessment and mitigation strategy/technique development. The hours of experience do not need to be continuous. •A minimum of 14,000 hours experience development experience within the past fifteen (15) years in the full system, product or service development lifecycle. The hours of experience do not need to be continuous. It is desirable that at least one IV&V Team Member have: •A minimum of one (1) previous engagement managing an IV&V review whose scope included meeting Federal or State administrative and technical regulations. 8
  9. 9. • At least 10,000 hours experience within the past seven (7) years in the technical environment employed by the project. The hours of experience do not need to be continuous. Contract Period: (Agency Name) anticipates that the start date of these IV&V Services will be (Date) and the end date will be (Date). (Agency Name) and the IV&V Service Provider may negotiate contract extensions as required. Payment: An invoice submitted upon acceptance of each IV&V Review Report assigned to the IV&V Service Provider. Travel and expenses are to be invoiced separately. An invoice may be submitted to the Commonwealth provided written acceptance has been provided to the contractor from the contracting agency of each IV&V Review Report assigned to the IV&V Service Provider. Travel costs may be reimbursed to the contractor in accordance with the terms of Contract VA-030815 provided travel occurs as a result of either of the following: 1) travel is required of the contractor outside of the primary work place (contracting agency) and has been pre-approved by the contracting agency, or 2) out-of-state (outside of VA) travel related expenses as negotiated by the contracting agency and the contractor in accordance with the referenced Contract terms. Such travel related costs (e.g., lodging, air fare, car rental, parking, meals and incidentals expenses) will be reimbursed by the Commonwealth to the contractor provided travel costs do not exceed 15% of the total order cost of services) and rates are in accordance with travel rates as established by the Department of Accounts in the Commonwealth’s State Travel Regulations. Authorized travel and related expenses as permitted by the referenced Contract shall be invoiced as they occur and separate from the invoices for IV&V services. Invoices shall not include billing for project management or oversight of the IV&V Service Provider for the successful delivery of the contracted IV&V Review Reports. Criminal Background Checks Required: Yes: X No: ___ Controls and Guidelines: The IV&V Service Provider must obtain prior approval from the Project Sponsor for travel outside of the Richmond Metropolitan Area. The Project Sponsor will not unduly withhold travel approval for the purpose of, interviewing major project personnel, reviewing major project documentation or observing major project activities. Scheduled Work Hours: On an as needed basis, to be coordinated with the (Agency Name) Project Sponsor and (Project Name) Project Manager. 9
  10. 10. Cost Type Requested (fixed price, hourly rate, etc.): Respondent must show hourly rates and include a not to exceed amount. Other: None Facility, equipment, etc., to be provided by User Entity: (Agency Name) has limited workspace, furniture and equipment available and only on a temporary basis. Permanent office space, furniture and equipment are the responsibility of the IV&V Service Provider. While on-site at the project location (Agency Name) will provide access to a copier, fax, the agency LAN and the internet (for up to two connections). (Agency Name) will also provide temporary desk space. The IV&V Service Provider must provide any cell phones, personal computers or laptops required by the IV&V Review Team. The VITA technical staff supporting the agency’s network must verify that any personal computers or laptops meet minimum-security configuration standards (e.g., current virus protection) before any equipment may be connected to the agency’s LAN. (Agency Name) will also provide access to all (Project Name) Project related information, including, but not limited to, technical documentation and project status and financial data and to project and contractor personnel for information related to the project. 3 Attachments: Attachment 1: IV&V Review Areas Attachment 2: IV&V Review Areas and Task Items Attachment 3: IV&V Review Report Template 10
  11. 11. Attachment 1: Mandatory IV&V Review Areas (See Note 1) DETAILED PROJECT IN-PROGRESS TEST PLANNING AND REVIEW AREA CLOSEOUT REVIEW PLANNING REVIEW REVIEWS EXECUTION REVIEWS PLANNING 1 Feasibility Studies 2 Business Case 3 Procurement 4 Project Complexity X X X X PROJECT MANAGEMENT 5 Project Sponsorship X X X X 6 Management Assessment X X X X 7 Project Management X X X X 8 Business Process Reengineering X X 9 Risk Management X X X X 10 Change Management X X X X 11 Communication Management X X X 12 Configuration Management X X X X 13 Project Estimating and Scheduling X X X X 14 Project Personnel X X X 15 Project Organization X X X 16 Contractors and External Staff X X X 17 Oversight of Contractors X X X X QUALITY MANAGEMENT 18 Quality Management X X X 19 Process Definition and Product Standards X X X 11
  12. 12. Training 20 User Training and Documentation X X 21 Developer Training and Documentation X X Requirements Management 22 Requirements Management X 23 Security and Privacy Requirements X 24 Requirements Analysis X 25 Interface Requirements X 26 Requirements Allocation and Specification X 27 Reengineering X Development Environment 28 Development Hardware X 29 Development Software X System Development 30 High-Level Design X 31 Detailed Design X 32 Coding X 33 Unit Testing X 34 Integration Testing X 35 System Testing X 36 Interface Testing X 37 Acceptance Testing X 38 Implementation X Data Management 39 Data Conversion X 40 Database Design X Operating Environment 41 System Hardware X 42 System Software X 43 Database Software X 44 Hardware and Software Environment Capacity X Operations 45 Change Tracking X 12
  13. 13. 46 User Satisfaction X 47 Goals and Objectives X 48 Documentation X 49 Operational Processes X Note 1: Those Review Areas marked with an “X” are mandatory for the type of review shown. All other Review Areas are discretionary. 13
  14. 14. This page intentionally left blank. 14
  15. 15. Attachment 2: IV&V Review Areas & Task Items PLANNING IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Assess the methodologies used for the technical feasibility study FS-1 verifying it was objective, reasonable, measurable, repeatable, consistent, accurate and verifiable. Assess the methodologies used for the economic feasibility FS-2 study verifying it was objective, reasonable, measurable, Feasibility repeatable, consistent, accurate and verifiable. Studies Review the system requirements (e.g., system requirements specification, feasibility study report, business rules description) in the RFP, Vendor Proposal, and Contract SOW to validate FS-3 whether the requirements can be satisfied by the defined technologies, methods, and algorithms defined for the project (feasibility). Review and evaluate the Business Case for the project to Business Case BC-1 assess its reasonableness. Verify that the procurement strategy supports Agency and PROC-1 Commonwealth project objectives. Review and make recommendations on the solicitation PROC-2 documents relative to their ability to adequately inform potential vendors about project objectives, requirements, risks, etc. Verify that the evaluation criteria are consistent with project objectives and evaluation processes are consistently applied; PROC-3 verify all evaluation criteria are metrics based and clearly articulated within the solicitation documents. Procurement Verify that the obligations of the vendor, sub-contractors and external staff (terms, conditions, statement of work, requirements, technical standards, performance standards, development milestones, acceptance criteria, delivery dates, PROC-4 etc.) are clearly defined. This includes verifying that performance metrics have been included that will allow tracking of project performance and progress against criteria set by the agency and the Commonwealth. Verify the final contract for the vendor team states that the PROC-5 vendor will participate in the IV&V process, being cooperative in the coordination and communication of information. Verify that the assigned project complexity level is current and Project PC-1 accurate. If the project complexity level is not current and/or Complexity accurate, then reassign a project complexity level to the project. 15
  16. 16. PROJECT MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Assess agency sponsor buy-in, participation, support and PS-1 commitment to the project. Project Verify that open pathways of communication exist among all PS-2 Sponsorship project stakeholders. Verify that agency sponsor has bought-in to all changes that PS-3 impact project scope, cost, schedule or performance. Verify that lines of reporting and responsibility provide adequate MA-1 technical, financial and managerial oversight of the project. Evaluate project progress, resources, budget, schedules, and Management MA-2 reporting. Assessment Assess coordination, communication and management, to verify MA-3 agencies and departments are not working independently of one another. 16
  17. 17. PROJECT MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Verify that a project management plan exists and that the plan is PM-1 followed. Evaluate the project management plan maintenance procedures PM-2 to verify that they are developed, communicated, implemented, monitored and complete. Evaluate project reporting processes, procedures, and actual PM-3 project reports to verify that project status is being accurately traced using project metrics. Verify that milestones and completion dates are planned, PM-4 monitored, and met. Verify the existence and institutionalization of an appropriate project issue tracking mechanism that documents issues as they PM-5 arise, enables communication of issues to proper stakeholders, documents a mitigation strategy as appropriate, and tracks the issue to closure. Evaluate the status of the schedule being reported for the project on the Commonwealth Major IT Project Status Report PM-6 Dashboard. Note: Prior to selecting this task contact PMD to Project avoid duplicative effort. Management Verify that the Critical Path Milestones described for the project on the Commonwealth Major IT Project Status Report Dashboard are those approved by Agency Management, PM-7 including the date when the Critical Path Milestones received approval from Agency Management. Note: Prior to selecting this task contact PMD to avoid duplicative effort. Evaluate the system’s planned life-cycle development methodology or methodologies (waterfall, evolutionary spiral, PM-8 rapid prototyping, incremental, etc.) to see if they are appropriate for the system being developed. Evaluate the status of each Measure of Success being reported PM-9 for the project on the Commonwealth Major IT Project Status Report Dashboard. Verify that the Measures of Success for the project incorporate PM-10 input from the system’s users and customers. Verify that the Internal Agency Oversight Committee (IAOC) has PM-11 approved the Measures of Success, including the date when the Measures of Success received approval from the IAOC. PM-12 Determine if the project has remained within its approved scope. For each change in the approved scope of the project verify the PM-13 date the change was approved and by whom. For each change in the approved scope of the project, evaluate the description of the change, the reason for the change, and PM-14 the impact of the change, particularly on the cost and schedule baselines of the project. 17
  18. 18. PROJECT MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate the project’s ability and plans to redesign business BPR-1 processes to achieve improvements in critical measures of business performance, such as cost, quality, service, and speed. Verify that the reengineering plan has the strategy, management Business BPR-2 backing, resources, skills and incentives necessary for effective Process change. Reengineering Verify that resistance to change is anticipated and prepared for by using principles of change management at each step (such BPR-3 as excellent communication, participation, incentives) and having the appropriate leadership (executive pressure, vision, and actions) throughout the reengineering process. Verify that risk management processes and procedures exist and are being followed. Evaluate the project’s risk management RM-1 processes and procedures to verify that risks are identified and quantified and that mitigation plans are developed, communicated, implemented, monitored, and complete. Verify that a list of risk events is maintained and that the RM-2 probability of occurrence and impact are measured for each event. Risk Verify that a mitigation approach has been documented for each RM-3 Management risk event listed. Determine if any risk events have been dropped from the list and RM-4 the reason why. Verify that the top five risk events identified for the project are RM-5 those being reported for the project on the Commonwealth Major IT Project Status Report Dashboard. Verify that the Internal Agency Oversight Committee (IAOC) has RM-6 reviewed the project Risk Assessment(s), including the date(s) when the Risk Assessment(s) were reviewed by the IAOC. Verify that change management processes and procedures exist and are being followed. Evaluate the project’s change CHM-1 management processes and procedures to verify they are Change developed, communicated, implemented, monitored, and Management complete. Evaluate the project’s organizational change management CHM-2 processes and procedures to verify that organizational resistance to change is anticipated and prepared for. Verify that communication processes and procedures exist and are being followed. Evaluate the project’s communication Communication processes and procedures to verify they support COMM-1 Management communications and work product sharing between all project stakeholders; and assess if communication plans and strategies are effective, implemented, monitored and complete. 18
  19. 19. PROJECT MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Review and evaluate the configuration management (CM) processes and procedures associated with the development process. Verify that configuration management (CM) processes CM-1 and procedures exist and are being followed. Evaluate the project’s configuration control processes and procedures to verify that they are effective, implemented, monitored and complete. Verify that all critical development documents, including but not CM-2 limited to requirements, design, code and test are maintained under an appropriate level of control. Verify that the processes and tools are in place to identify code CM-3 versions and to rebuild system configurations from source code. Configuration Verify that appropriate source and object libraries are Management CM-4 maintained for training, test, and production and that formal sign- off procedures are in place for approving deliverables. Verify that appropriate processes and tools are in place to manage system changes, including formal logging of change CM-5 requests and the review, prioritization and timely scheduling of maintenance actions. Verify that mechanisms are in place to prevent unauthorized CM-6 changes being made to the system and to prevent authorized changes from being made to the wrong version. Review the use of CM information (such as the number and type CM-7 of corrective maintenance actions over time) in project management. 19
  20. 20. PROJECT MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate the estimating and scheduling process of the project to ensure that the project planning assumptions, budget, and PES-1 resources are adequate to support the work-breakdown structure and schedule. Examine historical data and data sources to determine if the project has been able to accurately estimate the schedule, labor PES-2 requirements and cost of product, service or system development efforts. Examine historical data and data sources to determine if the PES-3 project has been able to accurately apply Earned Value Management to the project. Examine historical data and data sources to determine if the PES-4 project has been able to accurately accumulate the actual costs of tasks completed for the project. Examine historical data and data sources to determine if the PES-5 project has been able to accurately determine the earned value of tasks completed for the project. Examine historical data and data sources to determine if the PES-6 project has been able to accurately accumulate the budgeted Project cost/planned value of tasks for the project. Estimating Examine historical data and data sources to determine if the and PES-7 project has been able to accurately calculate Schedule Scheduling Variance. Examine historical data and data sources to determine if the PES-8 project has been able to accurately calculate Cost Variance. Compare and evaluate the status of the planned and actual costs being reported for the project on the Commonwealth Major PES-9 IT Project Status Report Dashboard. Note: Prior to selecting this task contact PMD to avoid duplicative effort. Validate that the Planned Costs To Date reflected for the project on the Commonwealth Major IT Project Status Report PES-10 Dashboard are the same as those approved by the Internal Agency Oversight Committee. Validate the Actual Costs To Date figures reported for the project on the Commonwealth Major IT Project Status Report PES-11 Dashboard. Note: Prior to selecting this task contact PMD to avoid duplicative effort. Evaluate the nature and amount of cost variance between the PES-12 budgeted and actual costs to the project to date. Verify that Internal Agency Oversight Committee (IAOC) PES-13 approved the Planned Costs for the Project, including the date when the Planned Costs received approval from the IAOC. 20
  21. 21. PROJECT MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Examine the job assignments, skills, training and experience of PP-1 the personnel involved in program development to verify that they are adequate for the development task. Project Evaluate the project’s personnel planning for the project to verify Personnel PP-2 that adequate human resources will be available for development and maintenance. Evaluate the project’s personnel policies to verify that staff PP-3 turnover will be minimized. Verify that lines of reporting and responsibility provide adequate PO-1 technical, financial and managerial oversight of the project. Project Verify that the project’s organizational structure supports Organization training, process definition, risk management, quality assurance, PO-2 configuration management, product testing and any other functions critical for the project’s success. Evaluate the use of contractors or other external sources of CES-1 project staff (such as IS staff from another State organization) in project development. Verify that the obligations of contractors and external staff (terms, conditions, statement of work, requirements, standards, CES-2 development milestones, acceptance criteria, delivery dates, etc.) are clearly defined. Contractors Verify that the contractors’ software development methodology and CES-3 and product standards are compatible with the system’s External Staff standards and environment. Verify that the contractor has and maintains the required skills, personnel, plans, resources, procedures and standards to meet CES-4 their commitment. This will include examining the feasibility of any offsite support of the project Verify that any proprietary tools used by contractors do not CES-5 restrict the future maintainability, portability, and reusability of the system. Verify that project management oversight of contractors is OC-1 provided in the form of periodic status reviews and technical interchanges. Verify that the project management has defined the technical Oversight of and managerial inputs the contractor needs (reviews, approvals, Contractors OC-2 requirements and interface clarifications, etc.) and has the resources to supply them on schedule. Verify that the project management staff has the ultimate OC-3 responsibility for monitoring project cost and schedule. 21
  22. 22. QUALITY MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate and make recommendations on the project’s quality QM-1 assurance (QA) processes, procedures and organization. Verify that QA has an appropriate level of independence from QM-2 project management. Verify that the QA organization monitors the fidelity of all defined QM-3 processes in all phases of the project. Verify that the quality of all products produced by the project is QM-4 monitored by formal reviews and sign-offs. Verify that project self-evaluations are performed and that QM-5 measures are continually taken to improve the process. Quality Monitor the performance of the QA contractor by reviewing its Management processes and reports and performing spot checks of system QM-6 documentation; assess findings and performance of the processes and reports. Verify that QA has an appropriate level of independence. QM-7 Evaluate and make recommendations on the project’s Quality Assurance plans, procedures and organization. Verify that the QA vendor provides periodic assessment of the QM-8 CMM activities of the project and that the project takes action to reach and maintain the next CMM Level. Evaluate the mechanisms that are in place for project self- QM-9 evaluation and process improvement. Review and make recommendations on all defined processes PDPS-1 and product standards associated with the system development. Verify that all major development processes are defined and that Process PDPS-2 the defined and approved processes and standards are followed Definition in development. and Verify that the processes and standards are compatible with Product PDPS-3 each other and with the system development methodology. Standards Verify that all process definitions and standards are complete, PDPS-4 clear, up-to-date, consistent in format, and easily available to project personnel. 22
  23. 23. TRAINING IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Review and make recommendations on the training provided to UTD-1 product users. Verify that sufficient knowledge transfer occurs for the maintenance and operation of the new product. Verify that training for users is instructor-led and hands-on and is UTD-2 directly related to the business process and required job skills. User Training Verify that user-friendly training materials and help desk services and UTD-3 are easily available to all users. Documentation Verify that all necessary policies, processes, and documentation UTD-4 are easily available to users. Verify that all training is given on time and is evaluated and UTD-5 monitored for effectiveness, with additional training provided as needed. Review and make recommendations on the training provided to DTD-1 system developers. Verify that developer training is technically adequate, DTD-2 appropriate for the development phase, and available at Developer appropriate times. Training and Verify that all necessary policies, processes and standards Documentation DTD-3 documentation are easily available to developers. Verify that all training is given on time and is evaluated and DTD-4 monitored for effectiveness, with additional training provided as needed. 23
  24. 24. REQUIREMENTS MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate and make recommendations on the project’s process REQ-1 and procedures for managing requirements. Verify that system requirements are well defined, understood REQ-2 and documented. Evaluate the allocation of system requirements to hardware and REQ-3 Requirements software requirements. Management Validate that software requirements can be traced through REQ-4 design, code and test phases to verify that the system performs as intended and contains no unnecessary software elements. Validate that the relationships between each software REQ-5 requirement and its system requirement are correct. REQ-6 Verify that requirements are under formal configuration control. Evaluate and make recommendations on project policies and SPR-1 procedures for ensuring that the system is secure and that the privacy of client data is maintained. Security and SPR-2 Evaluate the project’s restrictions on system and data access. Privacy SPR-3 Evaluate the project’s security and privacy risk analyses. Requirements Verify that processes and equipment are in place to back up SPR-4 client and project data and files and archive them safely at appropriate intervals. Verify that an analysis of user needs and objectives has been performed to verify that requirements of the system are well RA-1 understood, well defined, and satisfy any regulatory requirements. Verify that all stakeholders have been consulted to the desired RA-2 functionality of the system, and that users have been involved in prototyping of the user interface. Verify that all stakeholders have agreed to all changes that RA-3 impact project cost, schedule or performance. Verify that performance requirements (e.g. timing, response time RA-4 and throughput) satisfy user needs. Verify that user’s operations and maintenance requirements for Requirements RA-5 the system are completely specified. Analysis Concept documentation evaluation: Validate that the concept documentation satisfies user needs and is consistent with acquisition needs. Validate constraints of interfacing systems and constraints or limitations of proposed approach. Analyze system requirements and validate that the following satisfy user needs: RA-6 a. System functions b. End-to-end system performance c. Feasibility and testability of the functional requirements d. System architecture design e. Operation and maintenance requirements and environments f. Migration requirements from an existing system where applicable. 24
  25. 25. REQUIREMENTS MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Verify that all system interfaces are exactly described, by IR-1 medium and by function, including input/output control codes, data format, polarity, range, units, and frequency. Verify those approved interface documents are available and that appropriate relationships (such as interface working groups) IR-2 Interface are in place with all agencies and organizations supporting the Requirements interfaces. Verify that all external and internal system and software IR-3 interface requirements have been identified. Verify that each interface is described and that the interface IR-4 description includes data format and performance criteria (e.g., timing, bandwidth, accuracy, safety, and security). Verify that all system requirements have been allocated to either RAS-1 a software or hardware subsystem. Verify that requirements specifications have been developed for RAS-2 all hardware and software subsystems in a sufficient level of detail to ensure successful implementation. Verify that performance requirements (e.g., timing, response RAS-3 time, and throughput) allocated to hardware, software, and user interfaces satisfy user needs. Verify that the internal and external interfaces specify the data formats, interface protocols, frequency of data exchange at each Requirements RAS-4 interface, and other key performance requirements to Allocation and demonstrate compliance with user requirements. Specification Verify that application specific requirements, such as functional RAS-5 diversity, fault detection, fault isolation, and diagnostic and error recovery satisfy user needs. Verify that the user’s maintenance requirements for the system RAS-6 are completely specified. Validate that there are objective acceptance testing criteria for RAS-7 validating the requirements of the requirements specification documents. If a legacy system or a transfer system is or will be used in Reengineering RE-1 development, verify that a well-defined plan and process for reengineering the system is in place and is being followed. 25
  26. 26. DEVELOPMENT ENVIRONMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate new and existing development hardware configurations DH-1 to determine if their performance is adequate to meet the needs of system development. Determine if hardware is maintainable, easily upgradeable, and compatible with the agency’s existing development and processing environment. This evaluation should include, but is Development DH-2 not limited to CPUs and other processors, memory, network Hardware connections and bandwidth, communication controllers, telecommunications systems (LAN/WAN), terminals, printers and storage devices. Current and projected vendor support of the hardware should DH-3 also be evaluated, as well as the agency’s hardware configuration management plans and procedures. Evaluate new and existing development software to determine if DS-1 its capabilities are adequate to meet system development requirements. Determine if the software is maintainable, easily upgradeable, DS-2 and compatible with the agency’s current hardware and software environment. Evaluate the development environment as a whole to see if it shows a degree of integration compatible with good development. This evaluation should include, but is not limited Development DS-3 to, operating systems, network software, CASE tools, project Software management software, configuration management software, compilers, cross-compilers, linkers, loaders, debuggers, editors, and reporting software. Language and compiler selection should be evaluated with DS-4 regard to portability and reusability (ANSI standard language, non-standard extensions, etc.) Current and projected vendor support of the software should DS-5 also be evaluated, as well as the agency’s software acquisition plans and procedures. 26
  27. 27. SYSTEM DEVELOPMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate and make recommendations on existing high-level HLD-1 design products to verify the design is workable, efficient, and satisfies all system and system interface requirements. Evaluate the design products for adherence to the project design HLD-2 methodology and standards. Evaluate the design and analysis process used to develop the design and make recommendations for improvements. High-Level HLD-3 Evaluate design standards, methodology and CASE tools used Design and make recommendations. Verify that design elements can be traced back to system HLD-4 requirements. Determine if the relationship between the design elements and HLD-5 the requirements are specified to a constant level of detail. Verify that all design products are under configuration control HLD-6 and formally approved before detailed design begins. Evaluate and make recommendations on existing detailed DD-1 design products to verify that the design is workable, efficient, and satisfies all high-level design requirements. Evaluate the design products for adherence to the project design DD-2 methodology and standards. Evaluate and make recommendations on the design and DD-3 analysis process used to develop the design. Evaluate and make recommendations on the design standards, Detailed Design DD-4 methodology and CASE tools used. Verify that design elements can be traced back to system DD-5 requirements and high-level design elements. Determine if the relationship between the design elements and DD-6 the high-level design elements are specified to a constant level of detail. Verify that all design products are under configuration control DD-7 and formally approved before coding begins. 27
  28. 28. SYSTEM DEVELOPMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate and make recommendations on the standards and C-1 processes currently in place for code development. Evaluate the existing code base for portability and C-2 maintainability, taking software metrics including but not limited to modularity, complexity and source and object size. Evaluate code documentation for quality, completeness C-3 (including maintenance history) and accessibility. Evaluate the coding standards and guidelines and the projects compliance with these standards and guidelines. This C-4 evaluation should include, but not be limited to, structure, Coding documentation, modularity, naming conventions and format. Verify that developed code is kept under appropriate C-5 configuration control and is easily accessible by developers. Evaluate the project’s use of software metrics in management C-6 and quality assurance. Verify and validate that code components satisfy the detailed C-7 design. Validate that the logic, computational, and interface precision C-8 (e.g., truncation and rounding) satisfy the requirements in the system environment. Evaluate the plans, requirements, environment, tools, and UT-1 procedures used for unit testing system modules. Evaluate the level of test automation, interactive testing and UT-2 interactive debugging available in the test environment. Verify that an appropriate level of test coverage is achieved through the testing process, that test results are verified, that the UT-3 correct code configuration has been tested, and that the tests are appropriately documented, including formal logging of errors found in testing. Validate that the unit test plan satisfies the following criteria: Traceable to the software requirements and design; External consistency with the software requirements and design; Internal consistency between unit requirements; Test coverage of Unit Testing UT-4 requirements in each component; Feasibility of software integration and testing; and Feasibility of operation and maintenance (e.g., capability to be operated and maintained in accordance with user needs). a. Validate that the results of the Unit Testing of each software configuration item indicates that the item correctly implements the software design for the item as documented in the software design documentation for that item. b. Document the results as required by the test plan. UT-5 c. Validate that the results of the Unit Testing of each software configuration item satisfies the test acceptance criteria as specified in the Unit Test Plan. d. Document discrepancies between actual and expected test results. 28
  29. 29. SYSTEM DEVELOPMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate the plans, requirements, environment, tools, and IT-1 procedures used for integration testing of system modules. Evaluate the level of automation and the availability of the IT-2 integration test environment. Verify that an appropriate level of test coverage is achieved through the test process, that test results are verified, that the IT-3 correct code configuration has been tested, and that the tests are appropriately documented, including formal logging of errors found in testing. Validate that the integration test plan satisfies the following criteria: Traceable to the software requirements and design; External consistency with the software requirements and design; Internal consistency between unit requirements; Test coverage IT-4 of requirements in each component; Feasibility of software Integration integration and testing; and Feasibility of operation and Testing maintenance (e.g., capability to be operated and maintained in accordance with user needs). Verify that the test organization has an appropriate level of IT-5 independence from the development organization. a. Validate that the results of the Integration Testing of each software configuration item indicates that the item correctly implements the software design for the item as documented in the software design documentation for that item. b. Document the results as required by the test plan. IT-6 c. Validate that the results of the Integration Testing of each software configuration item satisfies the test acceptance criteria as specified in the Integration Test Plan. d. Document discrepancies between actual and expected test results. 29
  30. 30. SYSTEM DEVELOPMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate the plans, requirements, environment, tools, and ST-1 procedures for system testing of the system. Evaluate the level of automation and the availability of the ST-2 system test environment. Verify that a sufficient number and type of case scenarios are ST-3 used to ensure comprehensive but manageable testing and that tests are run in a realistic, real-time environment. Verify that test scripts are complete, with step-by-step ST-4 procedures, required pre-existing events or triggers, and expected results. Verify that test results are verified, that the correct code configuration has been used, and that the test runs are ST-5 appropriately documented, including formal logging of errors found in testing. Validate that the system test plan satisfies the following criteria: Traceable to the software requirements and design; External System Testing consistency with the software requirements and design; Internal consistency between unit requirements; Test coverage of ST-6 requirements in each component; Feasibility of software integration and testing; and Feasibility of operation and maintenance (e.g., capability to be operated and maintained in accordance with user needs). Verify that the test organization has an appropriate level of ST-7 independence from the development organization. a. Validate that the results of the System Testing of each software configuration item indicates that the item correctly implements the software design for the item as documented in the software design documentation for that item. b. Document the results as required by the test plan. ST-8 c. Validate that the results of the System Testing of each software configuration item satisfies the test acceptance criteria as specified in the System Test Plan. d. Document discrepancies between actual and expected test results. 30
  31. 31. SYSTEM DEVELOPMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate the plans, requirements, environment, tools, and IT-1 procedures for interface testing of the system. Evaluate the level of automation and the availability of the IT-2 system test environment. Verify that a sufficient number and type of case scenarios are IT-3 used to ensure comprehensive but manageable testing and that test are run in a realistic, real-time environment. Verify that test scripts are complete, with step-by-step IT-4 procedures, required pre-existing events or triggers, and expected results. Verify that test results are verified, that the correct code configuration has been used, and that the test runs are IT-5 appropriately documented, including formal logging of errors found in testing. Validate that the interface test plan satisfies the following criteria: Traceable to the software requirements and design; Interface External consistency with the software requirements and design; Testing Internal consistency between unit requirements; Test coverage IT-6 of requirements in each component; Feasibility of software integration and testing; and Feasibility of operation and maintenance (e.g., capability to be operated and maintained in accordance with user needs). Verify that the test organization has an appropriate level of IT-7 independence from the development organization. a. Validate that the results of the Interface Testing of each software configuration item indicates that the item correctly implements the software design for the item as documented in the software design documentation for that item. b. Document the results as required by the test plan. IT-8 c. Validate that the results of the Interface Testing of each software configuration item satisfies the test acceptance criteria as specified in the Interface Test Plan. d. Document discrepancies between actual and expected test results. 31
  32. 32. SYSTEM DEVELOPMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate the plans, requirements, environment, tools, and AT-1 procedures for acceptance testing of the system. Verify that acceptance procedures and acceptance criteria for each product are defined, reviewed, and approved prior to tests AT-2 and that test results are documented. Acceptance procedures must also address the process by which any software product that does not pass acceptance testing will be corrected. Verify that a sufficient number and type of case scenarios are AT-3 used to ensure comprehensive but manageable testing and that tests are run in a realistic, real-time environment. Verify that test scripts are complete, with step-by-step AT-4 procedures, required pre-existing events or triggers, and expected results. Verify that test results are verified, that the correct code configuration has been used, and that the test runs are AT-5 appropriately documented, including formal logging of errors found in testing. Validate that the acceptance test plan satisfies the following criteria: Traceable to the software requirements and design; External consistency with the software requirements and design; Internal consistency between unit requirements; Test coverage Acceptance AT-6 of requirements in each component; Feasibility of software Testing integration and testing; and Feasibility of operation and maintenance (e.g., capability to be operated and maintained in accordance with user needs). Verify that the acceptance test organization has an appropriate AT-7 level of independence from the subcontractor. Validate that appropriate acceptance testing based on the AT-8 defined acceptance criteria is performed satisfactorily before acceptance of software products. Verify that the process by which any software product that does AT-9 not pass acceptance testing should be corrected has been defined and documented. a. Validate that the results of the Acceptance Testing of each software configuration item indicates that the item correctly implements the software design for the item as documented in the software design documentation for that item. b. Document the results as required by the test plan. AT-10 c. Validate that the results of the Acceptance Testing of each software configuration item satisfies the test acceptance criteria as specified in the Acceptance Test Plan. d. Document discrepancies between actual and expected test results. Implementation I-1 Review and evaluate implementation planning. Verify that all software products required to install and operate I-2 each software component being implemented by the project are present in the software component’s installation package. Validate that all site-dependent parameters or conditions to I-3 verify supplied values are correct. 32
  33. 33. DATA MANAGEMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate the agency’s existing and proposed plans, procedures DC-1 and software for data conversion. Verify that procedures are in place and are being followed to DC-2 review the converted data for completeness and accuracy and to Data perform data cleanup as required. Conversion Determine conversion error rates and if the error rates are DC-3 manageable. Make recommendations on making the conversion process DC-4 more efficient and on maintaining the integrity of data during the conversion. Evaluate new and existing database designs to determine if they DBD-1 meet existing and proposed system requirements. Recommend improvements to existing designs to improve data DBD-2 integrity and system performance. Database Evaluate the design for maintainability, scalability, concurrence, Design DBD-3 normalization (where appropriate) and any other factors affecting performance and data integrity. Evaluate the project’s process for administering the database, DBD-4 including backup, recovery, performance analysis and control of data item creation. 33
  34. 34. OPERATING ENVIRONMENT IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate new and existing system hardware configurations to SH-1 determine if their performance is adequate to meet existing and proposed system requirements. Determine if hardware is compatible with the agency’s existing processing environment, if it is maintainable, and if it is easily System upgradeable. This evaluation should include, but is not limited SH-2 Hardware to CPUs and other processors, memory, network connections and bandwidth, communication controllers, telecommunications systems (LAN/WAN), terminals, printers and storage devices. Evaluate current and projected vendor support of the hardware, SH-3 as well as the agency’s hardware configuration management plans and procedures. Evaluate new and existing system software to determine if its SS-1 capabilities are adequate to meet existing and proposed system requirements. Determine if the software is compatible with the agency’s existing hardware and software environment, if it is System maintainable, and if it is easily upgradeable. This evaluation SS-2 Software should include, but is not limited to, operating systems, middleware, and network software including communications, file-sharing protocols, etc. Current and projected vendor support of the software should SS-3 also be evaluated, as well as the agency’s software acquisition plans and procedures. Evaluate new and existing database products to determine if DBS-1 their capabilities are adequate to meet existing and proposed system requirements. Determine if the database’s data format is easily convertible to Database other formats, if it supports the addition of new data items, if it is DBS-2 Software scaleable, if it is easily refreshable and if it is compatible with the agency’s existing hardware and software. Evaluate any current and projected vendor support of the DBS-3 software, as well as the agency’s software acquisition plans and procedures. Evaluate the existing processing capacity of the planned HSEC-1 hardware and software environment and verify that it is adequate for projected system. Evaluate the historic availability and reliability of the current HSEC-2 hardware and software environment, including the frequency Hardware and and criticality of failures. Software HSEC-3 Evaluate the results of any volume testing or stress testing. Environment Evaluate any existing measurement and capacity-planning Capacity HSEC-4 program and evaluate the hardware and software environment’s capacity to support future growth. Make recommendations on changes in processing hardware, storage, network systems, operating systems, COTS software, HSEC-5 and software design to meet future growth and improve system performance. 34
  35. 35. OPERATIONS IV&V TASK APPLICABLE REVIEW AREA TASK DESCRIPTION # (X) Evaluate the system change request and defect tracking CT-1 processes. Change Evaluate the implementation of the product change request and Tracking CT-2 defect tracking process activities and request volumes to determine if processes are effective and are being followed. User Evaluate user satisfaction with the product to determine areas US-1 Satisfaction for improvement. Goals Evaluate impact of the product on operational goals and and GO-1 performance objectives. Objectives Documentation DOC-1 Evaluate operational documentation. Evaluate the implementation of operational processes including Operational OP-1 backup, disaster recovery and day-to-day operations to verify Processes the processes are being followed. 35
  36. 36. Attachment 3: Report Template for IV&V Reviews The attached template is used by service providers to report on Independent Verification and Validation Reviews for major IT projects. This template will be included as Attachment 3 in all SOWs sent to providers or potential providers. 36
  37. 37. This page intentionally left blank. 37
  38. 38. COMMONWEALTH OF VIRGINIA Report on the (Enter Type of IV&V Review) Independent Verification and Validation (IV&V) Review Of (ENTER NAME OF MAJOR IT PROJECT) (Enter Date of Report) (Enter Name of Agency) Table of Contents 38

×