Loop/Contacts: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 36: Line 36:
* Deliver build for every sprint consisting of work from sprint backlog
* Deliver build for every sprint consisting of work from sprint backlog
* Report impediments to during team stand-ups
* Report impediments to during team stand-ups
* IRC Channel #Loop
  |  
  |  
* [https://mozillians.org/u/gavin/ Gavin Sharp, Engineering Manager]
* [https://mozillians.org/u/gavin/ Gavin Sharp, Engineering Manager]
Line 50: Line 51:
* Self-organizing and self-managing; team determines how much work they can commit to
* Self-organizing and self-managing; team determines how much work they can commit to
* Report impediments to during stand-up or to Engineering Manager
* Report impediments to during stand-up or to Engineering Manager
* IRC Channel #media
  |  
  |  
* [https://mozillians.org/u/mreavy/ Maire Reavy, Engineering Manager]
* [https://mozillians.org/u/mreavy/ Maire Reavy, Engineering Manager]
Line 61: Line 63:
* [https://mozillians.org/u/mthomson/ Martin Thomson, Architect]
* [https://mozillians.org/u/mthomson/ Martin Thomson, Architect]
* [https://mozillians.org/u/ehugg/ Ethan Hugg, Cisco]
* [https://mozillians.org/u/ehugg/ Ethan Hugg, Cisco]
* [Multimedia team covers much in FxOS for H264, gUM, FxOS compatibility]
* [Kevin Simons, Engineering Team manager Telenor]
* [Kevin Simons, Engineering Team manager Telenor]
* [Andreas Pehrson, Telenor]
* [Andreas Pehrson, Telenor]
Line 72: Line 75:
* Organization with unique charters, that include supporting Hello and webRTC.   
* Organization with unique charters, that include supporting Hello and webRTC.   
* Cross-team coordination and planning required for changes spanning groups
* Cross-team coordination and planning required for changes spanning groups
* Team Mailing list: loop-services-dev [https://mail.mozilla.org/listinfo/loop-services-dev click here to join]
  |  
  |  
* [https://mozillians.org/u/tziade/ Tarek Ziade, Engineering Manager Loop Server]
* [https://mozillians.org/u/tziade/ Tarek Ziade, Engineering Manager Loop Server]
* [https://mozillians.org/u/ametaireau/ Alexis Metaireau, Engineer]
* [https://mozillians.org/u/rhubscher/ Rémy Hubscher, Engineer]
* [https://mozillians.org/u/ibicking/ Ian Bicking, Engineering Manager (FxA & Push)]
* [https://mozillians.org/u/ibicking/ Ian Bicking, Engineering Manager (FxA & Push)]
* [https://mozillians.org/u/mbanner/ Maris Fogels, Sr. Project Manager (FxA & Push)]
* [https://mozillians.org/u/mbanner/ Maris Fogels, Sr. Project Manager (FxA & Push)]
* [https://mozillians.org/u/jgruen/ John Gruen & https://mozillians.org/u/rfeeley/ Ryan Feeley UX FxA]
* [https://mozillians.org/u/bmicheletto/ Bob Micheletto, Operations]
* [https://mozillians.org/u/bmicheletto/ Bob Micheletto, Operations]
* [https://mozillians.org/u/rpappalardo/ Richard Pappalardo, Sr. QA]
* [https://mozillians.org/u/rpappalardo/ Richard Pappalardo, Sr. QA]

Revision as of 23:11, 2 February 2015

Roles and Responsibilities for Hello, webRTC, partner teams, and external partners

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
  • IRC Channel #Loop
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
  • IRC Channel #media
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
  • Team Mailing list: loop-services-dev click here to join
Marketing and Communications
  • Marketing plan
  • Outbound blog / engagement
Release Management