QAPgmCharter

7/30/2019 QAPgmCharter

1/4

OIM Quality Assurance Program Charter

c:\documents and settings\habibi\my documents\copy [email protected]\ba (2,5,13)\washington.edu\qapgmcharter.docApril 13,

2009 Page 1 o f 4


1.0 Program Overview

1.1 Name OIM Quality Assurance Program.

1.2 Document Date April 01, 2009

1.3 Stakeholders Executive Sponsor: Sara Gomez, Vice Provost for Information Management andChief Information Officer, Sponsor: Jeanne Marie Isola, Associate Vice ProvostStrategic Projects and Portfolios

1.4 Program Manager Kerry Lamb, Strategic Projects and Portfolios

1.5 Website https://sharepoint.washington.edu/oim/SPP/projects/OIMqa

1.6 Goal Statement Expand OIM QA practices, grow the number of OIM quality experts, implementcontinuous process improvement (and keep it simple).

1.7 Description and/orBackground

The OIM Quality Assurance (QA) Program was developed to provide OIM teamsaccess to resources with experience in Quality Management, Process Improvement,and Quality Assurance. These resources can assist with the development ofpractices that promote both defect detection and defect prevention in the productsand 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.

1.8 Objectives This program will expand the quality activities practiced in OIM, grow the number ofOIM quality experts (practitioners), and implement continuous process improvementpractices throughout OIM and our partner units.

1.9 Scope Scope is initially limited to software development and maintenance work performedby OIM (and our partners, as applicable); eventually other areas such as businessprocesses and service quality will be added. Interviews will be conducted with OIMmanagement (starting with Strategic Projects and Portfolios) to elicit the highest

priority quality activities and resource needs, then create action plans based onthose priorities.

1.10 Schedule Work on the program began in Spring of 2008 and the action plan identifies workthrough 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).

1.11 Time Reporting CacTrack project #2582 (Software Quality Assurance) will be used to track time.

1.12 Oversight and/orReviews Planned

Quarterly status reports available on the Web site and sent to the OIM LeadershipTeam, and Status update during Associate Vice-Provost (AVP) meetings as needed.See the Communications Plan on the Web site.

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


2/4



2009 Page 2 o f 4

2.2 Hours Estimate 60% allocation of Project Resources and Quality Assurance Manager, sub-allocated to specific strategic projects, such as WebGrades, eFECS, FinancialDesktop.

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 AssurancePriority areas (Consistency/SDLC, Quality consulting, Testing) with deliverablesfurther 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, about400 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, includinggovernance and oversight.

OIM Leadership will expect and support follow up projects for continuing to improveOIM Quality Assurance processes, and will commit to increased resource requirementsthat will be needed in order to implement and sustain the recommendations.

OIM Management will create & enforce quality policies, and provide resources forcontinuous process improvement.

3.2 Constraints Implementation relies primarily on 60% allocation of Project Resources and QualityAssurance Manager (includes project and PMO time), and as-needed allocation ofresources from the projects to perform quality activities.

3.3 Dependencies 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 areunfamiliar with the best practices identified for the projects.

There are no expected impacts on existing systems or infrastructure, except whereprocesses are improved as a result of this program.

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


3/4



2009 Page 3 o f 4

4.1 Key Deliverables(Tier 1)


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, includingstage gates

an SPP project lessons learned archive

consistent deployment practices within SPP

tailoring guidelines for determining the appropriate quality activities andacceptance criteria for a project (i.e., project quality plans), and for projectSDLCs (using DIS Oversight Levels, other input)


a project quality activity estimating tool which accounts for DIS oversightlevels.

a quality activity project planning checklist


an estimating tool for testing activities

4.1 Key Deliverables(Tier 2 - Ongoing)


Project QA mentoring and help with ongoing quality activities

Project assistance with DIS Quality Assurance and Project ManagementOversight requirements

Project assistance with using, mentoring and training existing resources forproject quality activities


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 shareknowledge about consistent software development, improved testing practices.



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 softwaredevelopment life cycle and tailored project software development plan


quality planning and activity feedback for use in future quality program goals.


Test Plan template (complete)

common, standard testing and release practices and terminology.


4/4



2009 Page 4 o f 4



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 & policies3 - 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 andproduct 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

See the Communications Plan on the program Web site.

4.3 Success Criteria 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 Who Reason Reviewed

03/05/09 Kerry Lamb Initial Draft (consolidates information from

existing program documents - implementationplan, action plans, communications plan)

04/01/09 Kerry Lamb Added outreach to other groups to Tier 2Ongoing & modified estimates.

Documents

QAPgmCharter