Confirmed users
330
edits
| Line 58: | Line 58: | ||
* QA Taskboard Simple Card View - [[QA/Taskboard/Mockups/simple_card_view]] | * QA Taskboard Simple Card View - [[QA/Taskboard/Mockups/simple_card_view]] | ||
=== | === User Stories === | ||
==== User Stories for the Mozilla Community Contributor ==== | |||
A Mozilla Community Contributor should be able to: | A Mozilla Community Contributor should be able to: | ||
# Create a personal profile to state areas of interest, technical ability, time generally available at hand on a daily basis, etc. | # Create a personal profile to state areas of interest, technical ability, time generally available at hand on a daily basis, etc. | ||
| Line 72: | Line 74: | ||
# Participate in community discussion to make "One and Done" better (similar to [http://meta.stackoverflow.com/ Meta Stack Overflow]) | # Participate in community discussion to make "One and Done" better (similar to [http://meta.stackoverflow.com/ Meta Stack Overflow]) | ||
==== User Stories for the Mozilla QA team member ==== | |||
A Mozilla QA team member should be able to: | A Mozilla QA team member should be able to: | ||
# Define areas of interest within Mozilla QA in which Mozilla Community Contributors may participate (e.g. WebQA, B2G, etc). | # Define areas of interest within Mozilla QA in which Mozilla Community Contributors may participate (e.g. WebQA, B2G, etc). | ||
| Line 90: | Line 92: | ||
# Send thanks to the contributor. | # Send thanks to the contributor. | ||
==== User Stories for the Mozilla Manager ==== | |||
A Mozilla Manager (Community, Project, QA, etc.) should be able to: | A Mozilla Manager (Community, Project, QA, etc.) should be able to: | ||
# Read feedback of contributors after task completion. | # Read feedback of contributors after task completion. | ||
| Line 96: | Line 98: | ||
# Participate in community discussion (similar to [http://meta.stackoverflow.com/ Meta Stack Overflow]). | # Participate in community discussion (similar to [http://meta.stackoverflow.com/ Meta Stack Overflow]). | ||
==== Metrics / Reports ==== | |||
Metrics | |||
# List of tasks in progress but not completed within the expected duration (also known as "hanging tasks" or "long-pending tasks"). | # List of tasks in progress but not completed within the expected duration (also known as "hanging tasks" or "long-pending tasks"). | ||
# Number of unique contributors taking up tasks daily (drill down by area of interest, technical ability, etc.) | # Number of unique contributors taking up tasks daily (drill down by area of interest, technical ability, etc.) | ||
| Line 103: | Line 104: | ||
# Actual time taken to execute a task versus expected | # Actual time taken to execute a task versus expected | ||
# List of top contributors (sorted by total tasks completed) | # List of top contributors (sorted by total tasks completed) | ||
=== Architecture === | === Architecture === | ||