Mobile/Projects/Kinderfox/Status/22-Jul-2015: Difference between revisions
Jump to navigation
Jump to search
(Created page with "__NOTOC__ <big><big><big>'''Status Report for Fennec - Kinderfox - for the week/period of 16/07/2015 - 22/07/2015'''</big></big></big> == Overall Project Health == {| cellpa...") |
|||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
<big><big><big>'''Status Report for Fennec - Kinderfox - for the | <big><big><big>'''Status Report for Fennec - Kinderfox - for the period ending 24/07/2015'''</big></big></big> | ||
== Overall Project Health == | == Overall Project Health == | ||
| Line 9: | Line 9: | ||
|- | |- | ||
|<!-- For Red/Yellow/Green Status un-comment for the color you are reporting --> | |<!-- For Red/Yellow/Green Status un-comment for the color you are reporting --> | ||
[[File:RED.jpg|frameless|75px]]<br> | |||
[[File:YELLOW.jpg|frameless|75px]]<br> | <!--[[File:YELLOW.jpg|frameless|75px]]<br>--> | ||
<!--[[File:GREEN.jpg|frameless|75px]]<br>--> | <!--[[File:GREEN.jpg|frameless|75px]]<br>--> | ||
| Line 23: | Line 23: | ||
== Exec Summary/Hot Topics == | == Exec Summary/Hot Topics == | ||
<!--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.--> | ||
* | * A fixed backlog has been created for the V1 release, and sizing estimates applied. | ||
* | * Approximately 40% of the scoped work is assigned and in progress, while 57% is not yet started. | ||
* | * V1 scope was defined to produce a minimum viable product. Stance from Product Management at kick-off: If any features are determined to not be possible for the 42 release, this means the V1 as a whole is not viable for 42. Is this statement still true? If not, what can be removed. If so, do we slip to 43 delivery? To be discussed at Tuesday AM meeting with Product Management. | ||
== Risks & Issues == | == Risks & Issues == | ||
| Line 37: | Line 36: | ||
|- | |- | ||
| align="left"| | | align="left"| Project timeline is very short. Delivery of all features for Aug 10 is risky. | ||
|'''Open''' | |'''Open/Monitor''' | ||
| | |All | ||
| align="left"| | | align="left"| Final backlog was not set for the beginning of the 6-week cycle for 42 nightly. Currently 11 working days left in the cycle (as of July 24th) and 57% of work has not been started, and only 3% complete. Meeting with Product on Tuesday AM. Decision needed: Can the scope be adjusted and still meet mvp level, or does this need to slip to 43? | ||
| | | Jul 28th | ||
|- | |- | ||
| Line 67: | Line 66: | ||
== Accomplished for the Last Period == | == Accomplished for the Last Period == | ||
<!--Both deliverables; code and actions; and decisions. Remove example text below--> | <!--Both deliverables; code and actions; and decisions. Remove example text below--> | ||
* Landed | * Landed [https://bugzilla.mozilla.org/show_bug.cgi?id=1125316|Bug 1125316] | ||
* | * V1 Scope defined and backlog sizing completed | ||
== Planned for Last Period but Not Accomplished == | == Planned for Last Period but Not Accomplished == | ||
<!--Both deliverables; code and actions; and decisions. Remove example text below--> | <!--Both deliverables; code and actions; and decisions. Remove example text below--> | ||
<!--Items that DID NOT meet their target date, which fell in the last reporting period--> | <!--Items that DID NOT meet their target date, which fell in the last reporting period--> | ||
* | |||
* | |||
== Planned for the Upcoming Period == | == Planned for the Upcoming Period == | ||
<!--Both deliverables; code and actions; and decisions. Remove example text below--> | <!--Both deliverables; code and actions; and decisions. Remove example text below--> | ||
<!--All items due over the next reporting period. Including those items missed last period if the new target date falls in the next period. i.e., you will have some repeated items from the previous section--> | <!--All items due over the next reporting period. Including those items missed last period if the new target date falls in the next period. i.e., you will have some repeated items from the previous section--> | ||
* | * Clear bugs in review queue: [https://bugzilla.mozilla.org/show_bug.cgi?id=1125289|Bug 1125289] & [https://bugzilla.mozilla.org/show_bug.cgi?id=1180653|Bug 1180653] | ||
* Land assigned bugs: [https://bugzilla.mozilla.org/show_bug.cgi?id=1125315|Bug 1125315], [https://bugzilla.mozilla.org/show_bug.cgi?id=1125977|Bug 1125977], [https://bugzilla.mozilla.org/show_bug.cgi?id=1125979|Bug 1125979], [https://bugzilla.mozilla.org/show_bug.cgi?id=1125980|Bug 1125980], [https://bugzilla.mozilla.org/show_bug.cgi?id=1182514|Bug 1182514] | |||
* Land | |||
== Status Details <!--Optional Section If Needed--> == | == Status Details <!--Optional Section If Needed--> == | ||
<!--Space for various quantitative data. Charts, burn downs, stats, bug counts etc...--> | <!--Space for various quantitative data. Charts, burn downs, stats, bug counts etc...--> | ||
<!--Thumbnail Gallery. Graphics expand on click. Replace Example Text with your own files and names--> | <!--Thumbnail Gallery. Graphics expand on click. Replace Example Text with your own files and names--> | ||
Summary of Engineering Work | |||
* Done - 3% | |||
* In Review - 12% | |||
* Assigned - 28% | |||
* Available - 57% | |||
<!-- | |||
<gallery> | <gallery> | ||
File:Example1.jpg|Example Chart 1 - Add Name Here | File:Example1.jpg|Example Chart 1 - Add Name Here | ||
File:Example2.jpg|Example Chart 2 - Add Name Here | File:Example2.jpg|Example Chart 2 - Add Name Here | ||
</gallery> | </gallery> | ||
--> | |||
== Important Links/References <!--Optional--> == | == Important Links/References <!--Optional--> == | ||
<!--Remove Example Text Below and replace with your links and titles--> | <!--Remove Example Text Below and replace with your links and titles--> | ||
<!--Useful for keeping track of links to Aha! Roadmaps, Trello Boards, Key Bugzilla queries, other related wiki pages with further background information, status reports for related projects etc... --> | <!--Useful for keeping track of links to Aha! Roadmaps, Trello Boards, Key Bugzilla queries, other related wiki pages with further background information, status reports for related projects etc... --> | ||
* [https:// | * [https://docs.google.com/a/mozilla.com/spreadsheets/d/126rvOGF-exZ0C0VpTlPU3Q8IgLstRaFAw0j3vyDCGGs/edit?usp=sharing Kinderfox V1 Backlog Tracking Sheet] | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1125984 Kinderfox V1 Meta bug in Bugzilla] | |||
* [https:// | * [https://wiki.mozilla.org/Mobile/Projects/Kinderfox Main project wiki page] | ||
* [https:// | |||
[[Category:Wikipage templates]] | [[Category:Wikipage templates]] | ||
Latest revision as of 18:55, 24 July 2015
Status Report for Fennec - Kinderfox - for the period ending 24/07/2015
Overall Project Health
| This Week | Last Week |
|---|---|
|
|
N/A |
Exec Summary/Hot Topics
- A fixed backlog has been created for the V1 release, and sizing estimates applied.
- Approximately 40% of the scoped work is assigned and in progress, while 57% is not yet started.
- V1 scope was defined to produce a minimum viable product. Stance from Product Management at kick-off: If any features are determined to not be possible for the 42 release, this means the V1 as a whole is not viable for 42. Is this statement still true? If not, what can be removed. If so, do we slip to 43 delivery? To be discussed at Tuesday AM meeting with Product Management.
Risks & Issues
| Description of Risk/Issue | State | Owner | Plan to Resolve/Mitigation | Target Date |
|---|---|---|---|---|
| Project timeline is very short. Delivery of all features for Aug 10 is risky. | Open/Monitor | All | Final backlog was not set for the beginning of the 6-week cycle for 42 nightly. Currently 11 working days left in the cycle (as of July 24th) and 57% of work has not been started, and only 3% complete. Meeting with Product on Tuesday AM. Decision needed: Can the scope be adjusted and still meet mvp level, or does this need to slip to 43? | Jul 28th |
Accomplished for the Last Period
- Landed 1125316
- V1 Scope defined and backlog sizing completed
Planned for Last Period but Not Accomplished
Planned for the Upcoming Period
- Clear bugs in review queue: 1125289 & 1180653
- Land assigned bugs: 1125315, 1125977, 1125979, 1125980, 1182514
Status Details
Summary of Engineering Work
- Done - 3%
- In Review - 12%
- Assigned - 28%
- Available - 57%