|
|
|
# (Ideal) New Feature Checklist
|
|
|
|
|
|
|
|
|
|
|
|
## Pre-implementation and design stage
|
|
|
|
|
|
|
|
1. User Research
|
|
|
|
2. Product Requirements Document
|
|
|
|
|
|
|
|
## Implementation and design stage
|
|
|
|
|
|
|
|
1. New assets and images produced - UX designer/antonela
|
|
|
|
2. New strings are reviewed - Comms/stephw
|
|
|
|
3. New strings are sent for localization - localization coordinator/emmapeel
|
|
|
|
4. Feature added to onboarding - UX designer/Developers - antonela/tbb devs
|
|
|
|
|
|
|
|
## Pre-launch
|
|
|
|
|
|
|
|
1. Release on nightlies
|
|
|
|
2. User testing
|
|
|
|
3. Release on alphas
|
|
|
|
4. User testing/QA
|
|
|
|
5. User facing documentation - Community Team/ggus
|
|
|
|
6. Email to tor-internal (?)
|
|
|
|
|
|
|
|
## Launch
|
|
|
|
|
|
|
|
1. Blog post
|
|
|
|
2. User facing documentation
|
|
|
|
3. Developer facing documentation
|
|
|
|
4. Communication with 3rd parties (eg Tails, Guardian)
|
|
|
|
|
|
|
|
## Post-launch
|
|
|
|
|
|
|
|
1. Moderate blog post comments
|
|
|
|
2. Answer frontdesk queries
|
|
|
|
3. Follow up user testing |
|
|
|
\ No newline at end of file |