Release Management/2014 Q1 Work Week/Pilot Program Notes: Difference between revisions
(Created page with "* Internal Teams that we want to involve ** Engineering ** SUMO ** QA ** Engagement ** Desktop support ** Dev out reach ** marketing Triage bugs by users Feedback ap...") |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 8: | Line 8: | ||
** marketing | ** marketing | ||
* Needed for success | |||
** Triage bugs by users | |||
** Feedback app on device -> tied to input.mozilla.com | |||
** File a bug directly on app, from screenshot (ask if they want to file bug)auto fill keyword in those bugs | |||
Stakeholders: | Stakeholders: | ||
| Line 23: | Line 20: | ||
* Issue with users - how to get phones flashed; and check with legal on ANY restrictions. | * Issue with users - how to get phones flashed; and check with legal on ANY restrictions. | ||
* Have desktop support insert asset tags with ids onto the device (last time used a flashing script) so we can get this info in update pings, crash reports, and feedback from the device | * Have desktop support insert asset tags with ids onto the device (last time used a flashing script) so we can get this info in update pings, crash reports, and feedback from the device | ||
* Do we want to get phones across all locations ? Last time we | * Do we want to get phones across all locations ? Last time we restricted to locations due to IT availability needed to due flashing restrictions and asset tag on the device | ||
* Global - carriers/ different languages/ apps/ websites | * Global - carriers/ different languages/ apps/ websites | ||
What is the desired output from this program? | What is the desired output from this program? | ||
Latest revision as of 22:59, 29 January 2014
- Internal Teams that we want to involve
- Engineering
- SUMO
- QA
- Engagement
- Desktop support
- Dev out reach
- marketing
- Needed for success
- Triage bugs by users
- Feedback app on device -> tied to input.mozilla.com
- File a bug directly on app, from screenshot (ask if they want to file bug)auto fill keyword in those bugs
Stakeholders: Known Issues:
- Updates: quality, cadence, channels, network issues with installing
- Culture: using a phone that is not as slick as iPhone/Android
- Carriers: not everyone is on T-Mobile (or carrier with SIM cards) so getting people to make the phone their primary device is a challenge, does Mozilla foot the bill for this?
- Issue with users - how to get phones flashed; and check with legal on ANY restrictions.
- Have desktop support insert asset tags with ids onto the device (last time used a flashing script) so we can get this info in update pings, crash reports, and feedback from the device
- Do we want to get phones across all locations ? Last time we restricted to locations due to IT availability needed to due flashing restrictions and asset tag on the device
- Global - carriers/ different languages/ apps/ websites
What is the desired output from this program? What will this program not address? Checkpoints often? Have a cross functional meeting just to check in with users. OTA - didn't work the last time around Should partners be engaged?