Changes

Jump to: navigation, search

QA/Taskboard

2,049 bytes removed, 19:45, 28 October 2013
no edit summary
Congratulations - you're One and Done.
-->
 
== Product Version 0.1 ==
 
=== Mockups ===
One and Done workflow with mockups:
* [[QA/Taskboard/Workflows/Milestone1#Contributors | Workflow for Community Contributors]]
* [[QA/Taskboard/Workflows/Milestone1#MozillaQaTeam | Workflow for Mozilla QA Team Members]]
 
=== User Stories ===
 
==== User Stories for the Mozilla Community Contributor ====
A Mozilla Community Contributor should be able to:
# Understand the One and Done initiative [aka QA Taskboard] and login to get started.
# Create and edit a personal profile to state display name.
# Go through a list of tasks available and filter them based on their area and estimated execution time.
# Pick up one task for execution.
# Read clear instructions on how to do the task.
# Get help from Mozilla QA Mentors assigned to the task.
# Pause work on the task and resume at a later time, perhaps from a different location.
# Login again and view the profile to see the total number of tasks completed so far and the current task under execution.
# Mark the task as abandoned or complete.
# Give feedback on the task.
# See the task completion reflected in profile statistics.
 
==== User Stories for the Mozilla QA team member ====
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).
# Create tasks with clear instructions, estimated execution time, area of interest, and unique URL.
# Discuss a particular task over email by sharing the task's unique URL.
# Save the task in a draft state and publish it as needed for contributors to start work on.
# Make unlimited instances of a task available for contributors to pick up (for example, test case suites on a testday).
# See a list of all tasks completed / abandoned.
 
==== User Stories for the Mozilla Manager ====
A Mozilla Manager (Community, Project, QA, etc.) should be able to:
# Read feedback of contributors after task completion.
# Read metrics of community participation: Number of tasks completed daily (drill down by area of interest, estimated execution time, contributor display name, etc.)
 
== Product Version 1.0 ==
# Actual time taken to execute a task versus expected
# List of top contributors (sorted by total tasks completed)
 
 
=== Development Milestones ===
# [[QA/Taskboard/Version1-Milestone1 | Milestone 1]]
 
 
== Product Version 2.0 ==
* Earn reputation and badges.
* Install a Firefox browser add-on that can show a notification when a matching task is available.
 
A Mozilla Manager (Community, Project, QA, etc.) should be able to:
* Define how reputation and badges should be earned.
 
Metrics:
Confirm
330
edits

Navigation menu