Firefox/Metro
Firefox Metro Development Project
Goal
The goal of this project is to produce a Minimum Viable Product (MVP) version of Firefox for release on the Windows 8 Metro Operating System.
Summary
- Total value of story points is: TBD.
- To date, the total value of story points completed: TBD.
- Projected amount of story points remaining to complete the project: TBD.
- Remaining sprints to completion: TBD.
- Project launch: TBD.
Scope
The project's Minimum Viable Product has just those features that allow Windows 8 Metro version of Firefox to be deployed, and no more. It is a strategy which allows Mozilla to collect the maximum amount of validated learning about customers with the least effort.
The Feature Stories required to develop the Minimum Viable Product are collected and prioritized in the Product Backlog. The goals of the Product Backlog are to:
- Enable stories to be prioritized so that the team is always working on the most important features.
- Support continual planning as the product emerges so the plan matches reality.
- Improve forecasts so that the stakeholders make the best decisions about the project goals.
The Backlog can be changed after an Iteration – features that weren’t anticipated are added, features no longer necessary are removed and priorities changed as necessary. The Product Manager is responsible for maintaining the backlog.
- Firefox Metro Browser: Product Backlog
Release
Pessimistic Release Scenario
- If we average the worst TBD velocity figures, the team can complete TBD story points per Iteration. This means that at an estimated TBD Iterations remaining, the team could complete a total of TBD story points which (falls short of/meets/exceeds) the target of the TBD remaining story points for the project. If this scenario holds true then the project would finish TBD.
Optimistic Release Scenario
- If we average the best TBD velocity figures, the team can complete TBD story points per Iteration. This means that at an estimated TBD Iterations remaining, the team could complete a total of TBD story points which (falls short of/meets/exceeds) the target of the TBD remaining story points for the project. If this scenario holds true then the project would finish TBD.
Expected Release Scenario
- If we average all the velocity figures, the team can complete TBD story points per Iteration. This means that at an estimated TBD Iterations remaining, the team could complete a total of TBD story points which (falls short of/meets/exceeds) the target of the TBD remaining story points for the project. If this scenario holds true then the project would finish TBD.
| Pessimistic Scenario | Optimistic Scenario | Expected Scenario | |
|---|---|---|---|
| Average Velocity | all | all | all |
| Sprints To Completion | all | all | all |
Iterations
The project is structured on completed Feature Stories during 12-day Iteration cycles. An Iteration is divided into two parts: 10-days reserved for Feature Story development and 2-days for Operations (Iteration Reviews and Planning).
- The forecasted total number of sprints to complete the project: TBD
- View Current Iteration Backlog: [1]
- View Previous Iteration Status Reports:
- Firefox Metro Sprint #1: January 21, 2013 - February 05, 2013 (Report Upcoming)
| Pessimistic Scenario | Optimistic Scenario | Expected Scenario | |
|---|---|---|---|
| Average Velocity | all | all | all |
| Sprints To Completion | all | all | all |
- Firefox Metro Browser: Product Backlog
Risks
- Rendering and graphics, specificly OMTC
- This area was a significant issue for Fennec so it will be monitored.
- We have no data on how long this work is likely to take and it's hard to estimate.
- First wave of refactoring done by 30th of December 2012 (bug 804893)
- Mitigation: Monitor next milestone and report on progress
- Sharing data between the desktop and the metro experience will happen via sync
- Main Tracking Bug: bug 768638
- Bugs relating to the metro team: bug 769424, bug 826396
- Sync team dependencies bug 826357, bug 798841
- UX will need to design a start page that shows the fields needed to setup sync
- High Resolution Support may be an issue and should be investigate.
- See a list of touch screen devices with HiDPI specified here.
- Themed/hoverable anonymous scrollbars for content
- bug 636564
- This work is an important component of mixed use (mouse/touch) scrolling working / scrollbar control display. Originally started for new OSX support but never completed.
- Metro related bugs : bug 775718, bug 777610
Communication
| Communication Type | Mechanism | Audience |
|---|---|---|
| Announcements | dev-planning and metro lists. metro@mozilla.org is the email address for the second list. | all |
| General discussion | metro list | devs |
| IRC | #windev | all |
| User Experience Meeting | Monday at 1pm PT (4pm ET)
|
devs |
| Engineering Triage Meeting | Wednesday at 1pm PT (4pm ET)
|
devs |
| Engineering Team Meeting | Thursday at 1pm PT (4pm ET)
|
devs |
Progress Reports
| 2012 | |
|---|---|
People
| Project Champion |
|
| Program Management |
|
| Product |
|
| UX |
|
| Engineering Oversight |
|
| Dedicated Engineering |
|
| Graphics Team Support |
|
| Accessibility |
|
| Localization |
|
| Services Engineering |
|
| Servieces |
|
| Incoming Bug Triage |
|
| QA |
|
| Security |
|
| Privacy |
|
| Releng |
|
| Marketing |
|
| Legal |
|
The letters following each name stand for:
- R = Responsible for deliverable
- A = Accountable for the final decision making on some aspect of the project
- C = Needs to be consulted on key topics
- I = Needs to be kept informed
See reference section for RACI roles system for more information.
Iterations
Firefox Metro will be broken down into 3 week cycles called "Iterations". Each iteration will kick off with a planning meeting and full report on progress sent out to stakeholders. The goal of this process is to provide a structure that allows for review of status, dependencies, new requirements, and facilitate task coordination between development groups.
Any bug that is expected to be worked on during a particular milestone will be marked with a whiteboard tag formatted like the following example:
"[metro-it1]"
The number will increment each time a new iteration starts and we will attempt to have the majority of engineering tasks schedule for the next 2 iterations. With that said, there are many demands on the engineering teams and changes to the plan could occur at any time so expectations should be tempered accordingly. To request a bug, feature, or user story to be planned in an upcoming milestone, add "[metro-it?]" to the whiteboard and it will be reviewed in the next iteration kick off meeting.
Here are the dates we will use for the next few iterations:
- [metro-it1] - November 19th, 2012 - December 7th, 2012
- [metro-it2] - December 10th, 2012 - January 11th, 2013
- This is longer due to holiday and the impact it's having on the regular train model
- [metro-it3] - January 14th, 2013 - February 1st, 2013
- [metro-it4] - February 4th, 2013 - February 22nd, 2013
- [metro-it?] - request to be scheduled.
References
- Developer documentation and notes: Firefox/Windows 8 Integration
- Product User Stories First Draft: User Stories Etherpad
- User Experience Firefox Metro Page: Firefox Metro UI wiki page
- User page with good information: Anaaktgeboren Firefox Metro
- Legacy feature page for the port: Feature Page
- First Pass MVP Feature Spreadsheet
- MVP Initial Feature List Meeting Notes
- UX Review of User Stories
- Raci Roles and Responsibilities Process
- Work Week: Reference Materials