Sunteți pe pagina 1din 4

OIM Quality Assurance Program Charter

OIM Quality Assurance Program Charter


1.0 Program Overview
1.1 Name 1.2 Document Date 1.3 Stakeholders OIM Quality Assurance Program. April 01, 2009 Executive Sponsor: Sara Gomez, Vice Provost for Information Management and Chief Information Officer, Sponsor: Jeanne Marie Isola, Associate Vice Provost Strategic Projects and Portfolios Kerry Lamb, Strategic Projects and Portfolios https://sharepoint.washington.edu/oim/SPP/projects/OIMqa Expand OIM QA practices, grow the number of OIM quality experts, implement continuous process improvement (and keep it simple). The OIM Quality Assurance (QA) Program was developed to provide OIM teams access to resources with experience in Quality Management, Process Improvement, and Quality Assurance. These resources can assist with the development of practices that promote both defect detection and defect prevention in the products and services provided by OIM. To determine the program implementation strategy, interviews with OIM management (starting with Strategic Projects and Portfolios) were conducted to elicit the highest priority quality activities and resource needs, then create action plans based on those priorities. This program will expand the quality activities practiced in OIM, grow the number of OIM quality experts (practitioners), and implement continuous process improvement practices throughout OIM and our partner units. Scope is initially limited to software development and maintenance work performed by OIM (and our partners, as applicable); eventually other areas such as business processes and service quality will be added. Interviews will be conducted with OIM management (starting with Strategic Projects and Portfolios) to elicit the highest priority quality activities and resource needs, then create action plans based on those priorities. Work on the program began in Spring of 2008 and the action plan identifies work through Summer 2009 for Tier 1 deliverables, Winter 2010 for Tier 2 deliverables, and Summer 2010 for Tier 3 deliverables. Some Tier 2 activities are ongoing (e.g., mentoring and assisting with project quality planning). CacTrack project #2582 (Software Quality Assurance) will be used to track time. Quarterly status reports available on the Web site and sent to the OIM Leadership Team, and Status update during Associate Vice-Provost (AVP) meetings as needed. See the Communications Plan on the Web site.

1.4 Program Manager 1.5 Website 1.6 Goal Statement 1.7 Description and/or Background

1.8 Objectives

1.9 Scope

1.10 Schedule

1.11 Time Reporting 1.12 Oversight and/or Reviews Planned

2.0 Program Resources


2.1 Project Team Kerry Lamb, Project Resources and Quality Assurance Manager SPP/OIM Managers Leadership Team (including Jeanne Marie Isola, Project Sponsor) OIM (project) staff

c:\documents and settings\habibi\my documents\copy khushboo.mca@gmail.com\ba (2,5,13)\washington.edu\qapgmcharter.docApril 13, 2009 Page 1 o f 4

OIM Quality Assurance Program Charter 2.2 Hours Estimate 60% allocation of Project Resources and Quality Assurance Manager, suballocated to specific strategic projects, such as WebGrades, eFECS, Financial Desktop. As-needed allocation of resources from the projects (e.g., for WebGrades, eFECS) to perform quality activities. Estimates include all participants and are for only the first three Quality Assurance Priority areas (Consistency/SDLC, Quality consulting, Testing) with deliverables further prioritized into tiers. Tier 1 contains the high-priority deliverables; Tier 2 the medium priority, and Tier 3 the low priority deliverables: Tier 1: 375 hrs Tier 2: 375 hrs Tier 3: 500 hrs Estimated Annual Ongoing Support: .25 FTE (700 hrs for Tier 2 ongoing, about 400 hrs annually)

3.0 Assumptions, Constraints, Dependencies and Impacts


3.1 Assumptions OIM Leadership will provide sponsorship and commitment to quality, and will support recommendations that are created as an outcome of the program, including governance and oversight. OIM Leadership will expect and support follow up projects for continuing to improve OIM Quality Assurance processes, and will commit to increased resource requirements that will be needed in order to implement and sustain the recommendations. OIM Management will create & enforce quality policies, and provide resources for continuous process improvement. 3.2 Constraints Implementation relies primarily on 60% allocation of Project Resources and Quality Assurance Manager (includes project and PMO time), and as-needed allocation of resources from the projects to perform quality activities. Other projects and programs that are related to the OIM Quality Assurance Program include: Joint UW technology and OIM Project Management Practices Work Group Project Management Office (PMO) in the Office of Information Management 3.4 Impacts There will be some learning curve overhead on the part of project teams who are unfamiliar with the best practices identified for the projects. There are no expected impacts on existing systems or infrastructure, except where processes are improved as a result of this program.

3.3 Dependencies

4.0 Deliverables, Expected Outcomes


Key deliverables are based on the Top 5 OIM Quality Assurance Priorities: 1 - Consistent practices and standards 2 - Quality consulting, mentoring, training, advising 3 - Improved Testing Practices 4 - Reviews of code, design, testing, security, documentation 5 - Requirements Management

c:\documents and settings\habibi\my documents\copy khushboo.mca@gmail.com\ba (2,5,13)\washington.edu\qapgmcharter.docApril 13, 2009 Page 2 o f 4

OIM Quality Assurance Program Charter

4.1 Key Deliverables (Tier 1)

1 - Consistent practices and standards project planning checklist (using both DIS & PM Portal processes) for small, medium and large projects. an organizational Quality Plan for SPP an organizational SDLC (software development life cycle) for SPP, including stage gates an SPP project lessons learned archive consistent deployment practices within SPP tailoring guidelines for determining the appropriate quality activities and acceptance criteria for a project (i.e., project quality plans), and for project SDLCs (using DIS Oversight Levels, other input) 2 - Quality consulting, mentoring, training, advising a project quality activity estimating tool which accounts for DIS oversight levels. a quality activity project planning checklist 3 - Improved Testing Practices an estimating tool for testing activities

4.1 Key Deliverables (Tier 2 - Ongoing)

2 - Quality consulting, mentoring, training, advising Project QA mentoring and help with ongoing quality activities Project assistance with DIS Quality Assurance and Project Management Oversight requirements Project assistance with using, mentoring and training existing resources for project quality activities 3 - Improved Testing Practices Test management & process consulting/mentoring for SPP Projects Project assistance with preparation of test documentation and execution of tests Outreach to non-OIM groups (e.g., Quality SIG, UWTech PMs) to share knowledge about consistent software development, improved testing practices.

4.1 Key Deliverables (Tier 2)

1 - Consistent practices and standards an organizational Software Development Plan for SPP an OIM project lessons learned archive. tailoring guidelines for project software development plans checklists for SPP project document reviews Pilot tailored project software quality plan, tailored project software development life cycle and tailored project software development plan 2 - Quality consulting, mentoring, training, advising quality planning and activity feedback for use in future quality program goals. 3 - Improved Testing Practices Test Plan template (complete) common, standard testing and release practices and terminology.

c:\documents and settings\habibi\my documents\copy khushboo.mca@gmail.com\ba (2,5,13)\washington.edu\qapgmcharter.docApril 13, 2009 Page 3 o f 4

OIM Quality Assurance Program Charter 4.1 Key Deliverables (Tier 3) 1 - Consistent practices and standards consistent SPP status tracking policies consistent production operational behaviors (e.g., scheduling, error detection) consistent SPP software configuration and change management processes. checklists for SPP project process reviews consistent SPP team building practices, training policies, and other management practices & policies 3 - Improved Testing Practices a tester job description family pilot a baseline library of regression test scripts and automated tests 4.1 Key Deliverables (remaining) 4 - Reviews of code, design, testing, security, documentation guidelines for project documentation and process reviews peer reviews of project design, code, test, & technical documentation and product deliverables. security reviews of product deliverables peer reviews of project processes. 5 - Requirements Management simple guidelines for capturing, documenting and managing requirements. an estimating tool for requirements management activities. exploration of an SPP/OIM product requirements repository. 6 - Metrics Defined metrics to collect and analyze Define metrics collection and analysis procedures Collected and analyzed metrics 4.2 Communication Plan 4.3 Success Criteria See the Communications Plan on the program Web site. Completion of the key program deliverables and activities for Tier 1. Positive feedback from the ongoing Tier 2 activities. Leadership team approval to continue to Tier 2 and Tier 3 deliverables.

5.0 Revision History

Date 03/05/09

Who Kerry Lamb

Reason Initial Draft (consolidates information from existing program documents - implementation plan, action plans, communications plan) Added outreach to other groups to Tier 2 Ongoing & modified estimates.

Reviewed

04/01/09

Kerry Lamb

c:\documents and settings\habibi\my documents\copy khushboo.mca@gmail.com\ba (2,5,13)\washington.edu\qapgmcharter.docApril 13, 2009 Page 4 o f 4

S-ar putea să vă placă și