Possible topics for future meetings (in no particular order):
I've got a new project - where do I start to make sure the quality is good?
Bug tracking demos
Test Plans / Test plan template to use for new projects
Ask someone from the Identity & Access Management team and/or WASP (Web Application Security Peer Working Group) to discuss Risk Assessment / Threat Analysis
Quality planning & project start up
Common agreement regarding acceptable quality levels and how to measure (internal and vender packages - what are we willing to accept? to risk?)
Data Quality (domain edits, consistency edits (intra entity), relationship edits, time variance, data quality degradation over time)
Metrics
Accessibility
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?
What are teams doing to improve software quality around the UW?
What's happening in the Seattle quality community?
Page Operations
Browse Space