Confirmed users
1,094
edits
Sescalante (talk | contribs) (first draft) |
Sescalante (talk | contribs) (updated draft) |
||
| Line 16: | Line 16: | ||
|- | |- | ||
| UX/Design | | UX/Design | ||
* Deliver UX assets/work necessary to progress work in backlog | * Deliver UX assets/work necessary to progress work in backlog | ||
* Responsible for attending Planning meetings & Reporting impediments | * Responsible for attending Planning meetings & Reporting impediments | ||
| Line 31: | Line 30: | ||
* Add EPM for the project and partner projects that you engage with | * Add EPM for the project and partner projects that you engage with | ||
|- | |- | ||
| | | Engineering | ||
* Self-organizing and self-managing; team determines how much work they can commit to from the Product Backlog during each Iteration Planning meeting | * Self-organizing and self-managing; team determines how much work they can commit to from the Product Backlog during each Iteration Planning meeting. | ||
* IRC Channel #Loop | * IRC Channel #Loop | ||
| | | | ||
| Line 41: | Line 38: | ||
* team (possibly with areas/specialties) | * team (possibly with areas/specialties) | ||
|- | |- | ||
| Partner teams | | Engineering Partner teams | ||
* ex: webRTC | * ex: webRTC | ||
**IRC Channel #media | **IRC Channel #media | ||
** Team mailing list: dev-media-request@lists.mozilla.org | ** Team mailing list: dev-media-request@lists.mozilla.org | ||
| | | | ||
* Engineering Manager | * webRTC | ||
* Module Owner | ** Engineering Manager | ||
* Team contacts | ** Module Owner | ||
** Team contacts | |||
* Partner team 2 | |||
** Engineering Manager | |||
** Module Owner | |||
** Team contacts | |||
|- | |- | ||
| QA | | QA | ||
| Line 58: | Line 60: | ||
| Service and Operations Team Partners | | Service and Operations Team Partners | ||
* Cross-team coordination and planning required for changes spanning groups | * Cross-team coordination and planning required for changes spanning groups | ||
* Release issues/timing Mailing list: loop-services-dev [https://mail.mozilla.org/listinfo/loop-services-dev click here to join] | * ex: Release issues/timing | ||
* IRC Channel #loop-server | **Mailing list: loop-services-dev [https://mail.mozilla.org/listinfo/loop-services-dev click here to join] | ||
** IRC Channel #loop-server | |||
| | | | ||
* | * related server side or platform team | ||
* | ** Engineering Manager | ||
* | ** Team contacts | ||
* | * Build contacts | ||
* | ** Engineering Manager | ||
* | ** Team contacts | ||
* | * Security contacts | ||
* | ** Team contacts | ||
* | |||
* | |||
* | |||
|- | |- | ||
| Marketing and Communications | | Marketing and Communications | ||
* Marketing plan | * Marketing plan | ||
* Outbound blog / engagement | * Outbound blog / engagement | ||
* Verify outbound communications/privacy matters | |||
| | | | ||
* | * Marketing contact | ||
* | * Legal/Privacy contacts | ||
|- | |- | ||