Mobile/Fennec/Tracking Protection Status/Status Report/14-Jul-2015: Difference between revisions
< Mobile | Fennec | Tracking Protection Status
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
<!--Should explain WHY for the health/status reported above. Items covered here may be covered in more detail further down in the report. If senior management were to look at nothing but this section, they should be able to tell what is going on with the project.--> | <!--Should explain WHY for the health/status reported above. Items covered here may be covered in more detail further down in the report. If senior management were to look at nothing but this section, they should be able to tell what is going on with the project.--> | ||
* The team did not land all selected work for the first 2-week iteration, and did not hit 33% of total work for the release, '''BUT''' status is not considered Red as a large amount of work sits near completion/in review. | * The team did not land all selected work for the first 2-week iteration, and did not hit 33% of total work for the release, '''BUT''' status is not considered Red as a large amount of work sits near completion/in review. | ||
** Clearing of the Review queue would put the team at 62% complete for the release, and above the level of selected work for the iteration | ** ''Clearing of the Review queue would have put the team at 62% complete for the release, and above the level of selected work for the iteration'' | ||
== Risks & Issues == | == Risks & Issues == | ||
Latest revision as of 18:56, 14 July 2015
Status Report for Fennec - Tracking Protection - for the week of 08/07/15 - 14/07/15
Overall Project Health
| This Week | Last Week |
|---|---|
|
|
|
Exec Summary/Hot Topics
- The team did not land all selected work for the first 2-week iteration, and did not hit 33% of total work for the release, BUT status is not considered Red as a large amount of work sits near completion/in review.
- Clearing of the Review queue would have put the team at 62% complete for the release, and above the level of selected work for the iteration
Risks & Issues
| Description of Risk/Issue | State | Owner | Plan to Resolve/Mitigation | Target Date |
|---|---|---|---|---|
| Team assigned is not 100% dedicated to Tracking Protection work, which has potential to impact ability to complete work | Open | Margaret, Jenn | Monitor how the team is doing in terms of meeting commitment for Tracking Protection, and discuss adjusting other workload as neccessary | Ongoing for the release |
| Eng is blocked on 1175977 as the list of required telemetry probes has not yet been defined | Open | Product Management | Javaun is defining this for Desktop, and mobile should then align accordingly | July 27th |
Accomplished for the Last Period
- Landed 1173623
- Half of total work for the release is currently In Review
Planned for Last Period but Not Accomplished
- Did not land the full 21 committed points of work for the iteration
- 3 points/1 item blocked
- 13 points/3 items in review
Planned for the Upcoming Period
Status Details
Mobile Tracking Protection Status - July 14th
Mobile Tracking Protection - Status by Bug - July 14th
Important Links/References
- Work Tracking Spreadsheet
- Meta bug for Tracking Protection work