Loop/Contacts: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (→‎Roles and Responsibilities: update with webrtc)
Line 4: Line 4:
  |-
  |-
  | Project Champion ||  
  | Project Champion ||  
* [https://mozillians.org/u/johnath/ Johnathan Nightingale]
* [https://mozillians.org/u/johnath/ Johnathan Nightingale, Hello]
* [https://mozillians.org/u/blassey/ Brad Lassey]
* [https://mozillians.org/u/blassey/ Brad Lassey, webRTC & Hello]
  |-  
  |-  
| Program/Project Management
* Monitor team and project performance, status report at conclusion of each Iteration
* Organize and facilitate Triage and Planning meetings
* Guide team through the practices and procedures of the project
|
* [https://mozillians.org/u/sescalante/ Shell Escalante]
|- 
| Product Manager  
| Product Manager  
* Define and document product features
* Define and document product features
Line 34: Line 27:
* [https://mozillians.org/u/mmaslaney/ Michael Maslaney]
* [https://mozillians.org/u/mmaslaney/ Michael Maslaney]
* [https://mozillians.org/u/phlsa/ Philipp Sackl]
* [https://mozillians.org/u/phlsa/ Philipp Sackl]
 
|- 
| Program/Project Management
* Monitor team and project performance, status report at conclusion of each Iteration
* Organize and facilitate Triage and Planning meetings
* Guide team through the practices and procedures of the project
|
* [https://mozillians.org/u/sescalante/ Shell Escalante]
  |-  
  |-  
  | Dedicated Hello Engineering  
  | Dedicated Hello Engineering  
Line 41: Line 40:
* Report impediments to during team stand-ups
* Report impediments to during team stand-ups
  |  
  |  
* [https://mozillians.org/u/gavin/ Gavin Sharp]
* [https://mozillians.org/u/gavin/ Gavin Sharp, Engineering Manager]
* [https://mozillians.org/u/mreavy/ Maire Reavy]
* [https://mozillians.org/u/mreavy/ Maire Reavy, Engineering Manager]
* [https://mozillians.org/u/mbanner/ Mark Banner]
* [https://mozillians.org/u/mbanner/ Mark Banner]
* [https://mozillians.org/u/abr/ Adam Roach, Lead Architect]
* [https://mozillians.org/u/abr/ Adam Roach, Lead Architect]
Line 55: Line 54:
* Report impediments to during stand-up or to Engineering Manager
* Report impediments to during stand-up or to Engineering Manager
  |  
  |  
* [https://mozillians.org/u/mreavy/ Maire Reavy]
* [https://mozillians.org/u/mreavy/ Maire Reavy, Engineering Manager]
* [https://mozillians.org/u/rjesup/ Randell Jesup, Module Owner]
* [https://mozillians.org/u/rjesup/ Randell Jesup, Module Owner]
* [https://mozillians.org/u/abr/ Adam Roach, Lead Architect]
* [https://mozillians.org/u/abr/ Adam Roach, Lead Architect]

Revision as of 22:40, 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
  • Guide team through the practices and procedures of the project
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
Marketing and Communications
  • Marketing plan
  • Outbound blog / engagement
Release Management