The senior executive responsible to the agency and the State CIO/OCIO for the project.
A Quality Assurance (QA) provider's assessment of the project's use of project management best practices, as well as their assessment of deficiencies or gaps in the application of those best practices that may have an adverse impact on the project. Findings are assumed to require corrective actions.
The work of one or more professionals responsible for monitoring and assessing the health and effectiveness of project management plans and processes as well as an overall assessment of a projects's short and longer term risks. To preserve independence, the QA provider(s) report outside the project management organizational structure, generally to the project's Executive Sponsor and the State CIO. In Washington state government, independent Project QA is considered different than product or technical quality assurance which might include testing and other independent verification and validation activities.
A tool to assist agencies and the Office of the Chief Information Officer to assess the cost, complexity, and statewide significance of an anticipated information technology project (RCW 43.105.245).
A project subject to State CIO/OCIO oversight based on risk/severity assessment, a statute or some other factor as determined by the State CIO.
A document that describes how the QA Practitioner will deliver its service.
A Request for Proposal, a Request for Quote and Qualification, an interagency agreement proposal or an agency recruitment or any other effort that is intended to result in the acquisition or hire of a QA resource.
For the purposes of project investment, approval, oversight and quality assurance, the start of the project is at the beginning of planning.
For the purpose of go live readiness, supporting organizations include the agency(s) and any vendor(s) who are involved in operations and support of the ongoing system/investment. Processes include any unique to the time immediately after go-live as well as those on-going processes required to effectively operate and maintain the system/investment once it is implemented into production.
The total project cost, also known as the comblined level of efffort, includes all associated costs, from planning through closeout, of state, vendor, or both, in order to purchase, acquire, gather and document requirements, design, develop or configure, plan or conduct testing, and complete implementation of the project.