User:Gmealer/QA Checklisting Program: Difference between revisions

 
(4 intermediate revisions by the same user not shown)
Line 31: Line 31:
=== Community ===
=== Community ===


Community energy is a precious resource, and we cannot afford to waste it. That which makes us efficient and agile makes the community efficient and agile as well. That which makes us more confident and effective makes the community more confident and effective as well.
Community energy is a precious resource, and we cannot afford to waste it. That which makes us effective, efficient and agile makes the community effective, efficient and agile as well. We are the community.
 
We are the community.


== How do we get started? ==
== 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>
#'''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>
#'''Identify Trackers'''<br><br>Create or find a way to track the list of processes so that they can be easily rearranged. It doesn't matter if the tracker is a wiki, Pivotal, spreadsheet, whatever. Use what works. Create a whole-QA tracker and a tracker for each subteam.<br><br>
#'''Identify Indexes'''<br><br>Create placeholders to index completed checklists 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>
#'''Prioritize Checklists'''<br><br>Add all processes to the tracker. Arrange the list of processes in the order that they should be checklisted. Guidelines for priority are:<br><br>
#'''Prioritize Checklists'''<br><br>Add all processes to the tracker. Arrange the 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 be higher.
#* Processes that can be performed by outside community should be higher.
Line 48: Line 47:
#* Processes that are complex or have a lot of steps should be higher.<br><br>
#* Processes that are complex or have a lot of steps 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>
#'''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>
#'''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>
#'''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 across QA as a whole, add it to each subteam index that applies.<br><br>


== What does a checklist look like? ==
== What does a checklist look like? ==
canmove, Confirmed users
2,041

edits