442
edits
(→Roles and Responsibilities: minor edit) |
(→Upcoming Priorities and Project Health: added start info) |
||
Line 77: | Line 77: | ||
*Risk 1 : ex: Roadmap goals for the release in November are too high for ____(dev, UX, PM?) resources by x amount (bugs? points? UX resources). likely will not make any features beyond x, y, z. | *Risk 1 : ex: Roadmap goals for the release in November are too high for ____(dev, UX, PM?) resources by x amount (bugs? points? UX resources). likely will not make any features beyond x, y, z. | ||
*Risk 2 : ex: Dependency on a service that is not established/planned for from another team. Need help prioritizing if we should delay the feature in this project or raise the priority in the other team based on their existing backlog | *Risk 2 : ex: Dependency on a service that is not established/planned for from another team. Need help prioritizing if we should delay the feature in this project or raise the priority in the other team based on their existing backlog | ||
'''Definitions of start and done''' | |||
Start (its possible not all these items need to be defined or agreed on by all members of the team, but the lack of these items should indicate red flags) | |||
* PRD's have been created: in progress | |||
* User stories created: in progress | |||
* Above requirements are understood (including dependencies such as: access to staging, new hardware, skill set development etc): TBD | |||
* Dev, QE and PM resources are mapped to intended goals: TBD | |||
* schedules create and agreed on: TBD | |||
Done: | |||
*TBD | |||
==Current Status== | ==Current Status== | ||
[https://wiki.mozilla.org/Mobile/Firefox_for_iOS/Status_Report/21-Apr-2015 example from Jenn's] | [https://wiki.mozilla.org/Mobile/Firefox_for_iOS/Status_Report/21-Apr-2015 example from Jenn's] |
edits