Release Management/Goals/2013Q1: Difference between revisions

Jump to navigation Jump to search
Line 23: Line 23:
=== Elevating ===
=== Elevating ===
* {{ok|[lsblakk] Continue working with our intern towards an engineering dashboard, and make sure we don't duplicate Kyle's work}}
* {{ok|[lsblakk] Continue working with our intern towards an engineering dashboard, and make sure we don't duplicate Kyle's work}}
** Sub-goal: {{ok|Determine how to keep longstanding issues on the radar of engineering teams, even once they're untracked (new keywords like topcrash)}}
* {{ok|[akeybl]Continue look into measurements that allow us to compare releases and identify pain points (Matt's user sentiment, Kyle's tracking analysis, etc.)}}
* {{ok|[akeybl]Continue look into measurements that allow us to compare releases and identify pain points (Matt's user sentiment, Kyle's tracking analysis, etc.)}}
** See https://etherpad.mozilla.org/release-quality and https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnSnd5sV2HeVdEZsV05BSlRlVXkxQlF2bThOdDlDTWc&usp=sharing#gid=0
** See https://etherpad.mozilla.org/release-quality and https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnSnd5sV2HeVdEZsV05BSlRlVXkxQlF2bThOdDlDTWc&usp=sharing#gid=0
* {{ok|Determine how to keep longstanding issues on the radar of engineering teams, even once they're untracked (new keywords like topcrash)}}


=== Team Focuses ===
=== Team Focuses ===
* {{ok|Use Asana for tracking non-bug work and coordination}}
* {{ok|Use Asana for tracking non-bug work and coordination}}
Confirmed users
1,798

edits

Navigation menu