Test Pilot: Difference between revisions

Jump to navigation Jump to search
1,415 bytes added ,  29 January 2016
Added stuff
mNo edit summary
(Added stuff)
Line 2: Line 2:


Test Pilot combines iterative prototyping, user research, and an opt-in user-facing testing platform. Each phase is designed evaluate new feature concepts quickly and at low cost.
Test Pilot combines iterative prototyping, user research, and an opt-in user-facing testing platform. Each phase is designed evaluate new feature concepts quickly and at low cost.
'''Test Pilot will let us take larger risks with product concepts, giving us a cheap avenue to test and validate product concepts.'''


= How does Test Pilot Work =
= How does Test Pilot Work =
Each phase of Test Pilot consists of prototype building and evaluation through user testing. Only in the third phase is any prototype deployed to the Test Pilot application itself.


[[File:Test-initiator-journey-summary.png|800px]]
[[File:Test-initiator-journey-summary.png|800px]]
<br/><br/>
The following diagram provides a more detailed view of the process:
[[File:Test-initiator-journey.png|800px]]
[https://wiki.mozilla.org/images/e/ee/Test-initiator-journey.png View full diagram]
= Who Builds and Manages Test Pilot? =
Test Pilot is run by two groups of people: the '''Build Team''' responsible for day to day engineering, UX, and product processes and '''Mission Control''', a group of cross-disciplinary members of the Firefox team tasked with steering individual projects and the Test Pilot project as a whole.
Team members are amplifiers for people participating in the program.  When a person or group submits an idea to Test Pilot they are starting a process in which they should expect to be involved until a conclusion is reached.
Test Pilot team members help participants progress through the Test Pilot process in whichever ways are needed - from boiling an idea down to get at a measurable core concept, documenting an idea thoroughly, iterating on designs and prototypes, assisting with coding, communicating with appropriate teams around Mozilla, and helping uplift a successful idea to its next stage in life.  An analogy could be made between Test Pilot team members and consultants.




= Goal =


* Test Pilot will let us take larger risks with product concepts, giving us a cheap avenue to test and validate product concepts.


= Communications =
= Communications =


=== Team ===
=== Build Team ===
{| class="wikitable"
{| class="wikitable"
|-
|-
Confirmed users
174

edits

Navigation menu