Loop/Contacts: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 20: Line 20:
* Keep work item, Feature Story and Epic status up-to-date
* Keep work item, Feature Story and Epic status up-to-date
  |  
  |  
* [https://mozillians.org/u/madhava/ Madhava Enros]
* [https://mozillians.org/u/madhava/ Madhava Enros, Firefox Experience]
* [https://mozillians.org/u/sevaan/ Sevaan Franks]
* [https://mozillians.org/u/sevaan/ Sevaan Franks, Hello Experience]
* [https://mozillians.org/u/darrin/ Darrin Henein]
* [https://mozillians.org/u/mnovak/ Matej Novak, Copy Director]
* [https://mozillians.org/u/mmaslaney/ Michael Maslaney]
* [https://mozillians.org/u/mmaslaney/ Michael Maslaney, Visual Design]
* [https://mozillians.org/u/phlsa/ Philipp Sackl]
* [https://mozillians.org/u/phlsa/ Philipp Sackl, Design Lead]
  |-   
  |-   
  | Program/Project Management  
  | Program/Project Management  

Revision as of 22:57, 2 February 2015

Roles and Responsibilities for Hello and webRTC

Role Contacts
Project Champion
Product Manager
  • Define and document product features
  • Maintain Product Backlog, Feature Stories up-to-date and prioritized, Review Iteration Build Release
UX/Design
  • Self-organizing and self-managing; team determines how much work they can commit to from the Product Backlog during each Iteration Planning meeting
  • Deliver UX assets/work necessary to progress work in backlog
  • Responsible for attending Planning meetings & Reporting impediments
  • Keep work item, Feature Story and Epic status up-to-date
Program/Project Management
  • Monitor team and project performance, status report at conclusion of each Iteration
  • Organize and facilitate Triage and Planning meetings
Dedicated Hello Engineering
  • Self-organizing and self-managing; team determines how much work they can commit to from the Product Backlog during each Iteration Planning meeting
  • Deliver build for every sprint consisting of work from sprint backlog
  • Report impediments to during team stand-ups
Dedicated webRTC Engineering
  • Self-organizing and self-managing; team determines how much work they can commit to
  • Report impediments to during stand-up or to Engineering Manager
QA
  • Create and execute test plans, triage issues, attending Planning meetings, Report impediments
Service and Operations Team Partners
  • Organization with unique charters, that include supporting Hello and webRTC.
  • Cross-team coordination and planning required for changes spanning groups
Marketing and Communications
  • Marketing plan
  • Outbound blog / engagement
Release Management