canmove, Confirmed users
2,041
edits
User:Gmealer/QA Checklisting Program: Difference between revisions
Jump to navigation
Jump to search
User:Gmealer/QA Checklisting Program (view source)
Revision as of 23:41, 31 December 2011
, 31 December 2011no edit summary
No edit summary |
|||
| Line 3: | Line 3: | ||
The QA Checklisting Program is an ongoing effort to document our processes in a way that will make us more effective as a team and more accessible to the Mozilla Community. | The QA Checklisting Program is an ongoing effort to document our processes in a way that will make us more effective as a team and more accessible to the Mozilla Community. | ||
The program involves creating checklists and associated | The program involves creating checklists and associated concise documentation for repeated processes, especially those that we expect to share with community members or that are of interest outside our team. | ||
== Why should we do this? == | == Why should we do this? == | ||
| Line 32: | Line 32: | ||
We are the community. | We are the community. | ||
== How do we get started? == | |||
#'''Brainstorm Processes'''<br><br>Brainstorm at the whole-QA level as well as the subteam level. Identify all processes that are performed on a regular basis. Don't attempt to figure out if they should be checklisted yet, just get everything on the table.<br><br> | |||
#'''Identify Trackers'''<br><br>Find a way to track the list of processes in a way that they can be easily rearranged. It doesn't matter if you use a wiki, Pivotal, spreadsheet, whatever. Use what works. Create a whole-QA tracker and a tracker for each subteam.<br><br> | |||
#'''Prioritize Checklists'''<br><br>Arrange each list of processes in the order that they should be checklisted. Guidelines for priority are:<br><br> | |||
#* Processes that can be performed by outside community should higher. | |||
#* Processes that directly involve external teams or the community should be higher. | |||
#* Complicated processes should be higher. | |||
#* Processes with a low margin of error should be higher. | |||
#* Processes performed frequently should be higher.<br><br> | |||
#'''Schedule Urgent Checklists'''<br><br>Some processes are either vital to the team, or so time-sensitive that they should be documented immediately. These are urgent checklists, and will likely already be at the top of the prioritized list. Move them to the top if necessary, and schedule resources now to create these.<br><br> | |||
#'''Identify Indexes'''<br><br>Create placeholders for checklist indexes on wiki for QA and for each subteam. Don't concentrate too much on initial organization; a flat list for each placeholder is fine. As processes get added, organization will become more obvious.<br><br> | |||
#'''Create Checklists'''<br><br>Create urgent checklists first. Other checklists can be created opportunistically the next time the process is performed, or scheduled off the list in priority order when resources are available.<br><br> | |||
#'''Add to Indexes'''<br><br>As each checklist is created, it should be added to the appropriate index. If a checklist is shared between subteams but not whole-QA, add it to each index that applies.<br><br> | |||