Wikimedia Release Engineering Team/Offsites/2018-01-Sonoma/Retro of previous offsite

QA Tribe

 * Renamed to QA SIG

Tech talks

 * no movement afaict

Process: estimation + bug mgmt + test metrics + test strategy

 * Other than our -kanban board, very little done in these areas
 * kanban has been useful, I (greg) believe
 * test metrics should be looked at (see above in CHG)

How to formalize Code Health group

 * created
 * helping with efforts such as the meaning of code Stewardship
 * no explicit buy-in from c-levels, but we do use the CHG to prepare for things we want approval from them
 * little done on the metrics/dashboards side of things so far

Outcomes

 * Healthy code - MISS, badly defined
 * Metrics - MISS
 * cyclomatic complexity
 * code coverage
 * Support/mandate - PARTIAL
 * "renewed focus on QA" outcomes - ???
 * Code health group
 * It's a good idea to start small, i.e. test with mobile web
 * Management wants long-term vision - HIT (with sunsetting working group/stewardship reviews)
 * Quality vs Quality Assurance - NOT an OUTCOME
 * code health group can assure big Q quality
 * Make developers more quality oriented - MISS? badly defined
 * testing does not provide value, lack of bugs provides value - statement
 * Enable developers to do the best work they can - mission statement
 * test engineer enables the team to test
 * high-level criteria, i.e. success factors
 * couple people on releng + j.robson
 * this is comparable to efforts by the security and performance team
 * reduces duplication of effort
 * code health group documents best practices
 * prescriptive
 * IDEA: adding code-health outcomes to roadmap - MISS
 * extension quality assessment

What does this look like?

 * weekly meeting - MONTHLY
 * core permanent group that is a steering committee - YES
 * steering committee needs to be cross-org - COULD BE BETTER
 * J.R. leads steering committee + liaison from RelEng - YES
 * don't call it qa -- "code health" - YES
 * rotating cast of supporting characters in addition to core - COULD BE BETTER
 * interested in specific areas
 * or has past experience
 * Determine scope within group - YES
 * defining a roadmap for code health - MISS