Loop/Contacts: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 31: Line 31:
* Monitor team and project performance, status report at conclusion of each Iteration
* Monitor team and project performance, status report at conclusion of each Iteration
* Organize and facilitate Triage and Planning meetings
* Organize and facilitate Triage and Planning meetings
* Guide team through the practices and procedures of the project
  |  
  |  
* [https://mozillians.org/u/sescalante/ Shell Escalante]
* [https://mozillians.org/u/sescalante/ Shell Escalante]
Line 73: Line 72:
  |  
  |  
* [https://mozillians.org/u/nils/ Nils Ohlmeier]
* [https://mozillians.org/u/nils/ Nils Ohlmeier]
 
|-
| 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
|
* [https://mozillians.org/u/tziade/ Tarek Ziade, Engineering Manager over Loop Server]
* [https://mozillians.org/u/ibicking/ Ian Bicking, Engineering Manager (FxA and Push)]
* [https://mozillians.org/u/mbanner/ Maris Fogels, Sr. Project Manager (FxA and Push)]
* [https://mozillians.org/u/bmicheletto/ Bob Micheletto, Operations]
* [https://mozillians.org/u/rpappalardo/ Richard Pappalardo, Sr. QA]
* [https://mozillians.org/u/wmaggs/ Bill Maggs, PM Cloud Services]
  |-  
  |-  
  | Marketing and Communications  
  | Marketing and Communications  

Revision as of 22:51, 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
  • Report impediments to the Project Manager
  • 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
  • Responsible for attending Planning meetings
  • Report impediments to the Project Manager
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