Added by Kerry Lamb, last edited by Kerry Lamb on Aug 26, 2008  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Overview

  • Date: Monday, August 04, 2008
  • Time: 1:30 pm to 3:30 pm (PST8PDT)
  • Location: EEB 403
  • Attendees: Karen Thomas, Alin Hunter, Jeani Wells, Kerry Lamb, Mary Syre, Dan Walker
  • Agenda
    - Refreshments!
    - Introductions
    - Survey results
    - Brainstorm topics and activities for upcoming meetings
    - Wrap up and next meeting plans

We had a discussion centered primarily on Data Quality, some process, and metrics.

Data Quality 

We added the following Data Quality topics to the areas of interest for future discussions:

  • Domain edits
  • Consistency Edits (intra entity)
  • Relationship edits
  • Time variance
  • Data quality over time (e.g., degradation due to changes to the meaning of data elements)

Issues around data quality include: not always knowing the state of our data, needing processes for validating data on a regular basis (to avoid 'data meaning creep') along with processes to keep those regular tests running and to resolve issues when they are found.

We also discussed looking into the possibility of getting the Data Management Committee (DMC - http://www.washington.edu/provost/oim/dmc/) involved in solving data quality issues, thinking that we could leverage better data quality with process quality.

Metrics

We discussed possible metrics to help us determine if our software is getting better.  The Financial Accounting dashboard was suggested as an example of measuring against targets (see http://www.washington.edu/admin/finacct/office/dashboard/). 

We could come up with 5-6 tangible measurable things to track and tie back to the information model defined in the UW Strategic Roadmap for Information Management and Administrative Systems (https://www.washington.edu/provost/oim/roadmap/), focusing on domains (e.g., Academic) vs. applications.

We could make sure new projects had a line item for measuring quality (e.g., all software must meet x standards of quality).

Other topics for future discussions

  • Accessibility
  • I've got a new project - where do I start to make sure the quality is good?
  • How to prepare for the anticipated interface testing that will be needed with implementation of the UW Strategic Roadmap for Information Management and Administrative Systems (https://www.washington.edu/provost/oim/roadmap/)
  • What are the quality processes already in place throughout the university?  Could we create a repository to share standard methodologies?

Next Meeting

  • Thursday, September 11, 2008
  • Time: 3:30 pm to 4:30 pm (PST8PDT)
  • Location: EEB 303
  • Topic: Kerry Lamb / Dan Walker will discuss testing and the Catalyst GradeBook / Student Web Services project.