Program Management/Weekly-Status-Reports/2013-04-09

Agenda

• Update on hiring
• Recent organizational changes
• Mozilla Summit 2013
• GDC update - let Martin bask in the glory
• FFOS - upcoming work week, help down the stretch
• Mozilla-wide PM meet-up
• Q2 goals
• Product Requirements Management System - https://productmanagers.etherpad.mozilla.org/20?

Dietrich

Erin

• Status rejigger is complete
• Train Schedule Cheat sheets: http://people.mozilla.com/~elancaster/PMTools/
• Features, features, features: Planning, scoping, tracking
  • http://people.mozilla.com/~elancaster/FxAProjPlan/FxAndroid2013_Full/FxAndroid2013Gantt.html
  • Bugzilla Time tracking group
  • https://github.com/bslassey/bzgantt/blob/master/gantt-chart.html

Lawrence

• Wrapping up Git information collection
• Restructuring performance program coordination around smaller projects with defined technical owners, monthly program review
• Mobile Web compat
  • Making progress on hiring
  • Slow progress on site outreach
  • Need to sit down and create detailed project plans to focus effort
• Telemetry looking at project reboot based on lessons learned from developers using the tool

Martin

Michael

This week:

• 4-way meeting with TEF/LG/QC/Moz to review v1.1 Plan A and Plan B schedules
• Update timelines for v1.0.1 with lauch dates
• Update timeline for v1.1
• Work on messaging for v1.1 Plan A and Plan B

Marco

Metro Highlights

• Iteration #5: April 1, 2013 - April 12, 2013

• The review of the V1 Feature List will be conducted on Tuesday April 16.
  • Product Manager's recommendations for those features that can be removed from the initial release will be presented to the project team for their feedback.
  • Those features selected for removal will be taken into account in the production release forecast of the Iteration #5 status report.
• Merged the project's 'On Hold' and 'To Be Planned' backlogs into one (Planning) to simplify the process of organizing stories (features, defects and changes) which require modification before entering the story backlog for selection in upcoming iterations.
• Created a new backlog to manage the project's defect and change stories (Defect & Change Backlog) to better prioritize them in isolation.
• A cap on the number of defect and change story points allocated to each upcoming iteration will be implemented.
  • This initiative will assist in managing the contingency fund allocated to defect and change stories so the project does not deplete them too soon.
  • Defects will be prioritized over changes.
  • Implementation will occur following the revision of the V1 Feature List.
• Received an update from Shea regarding the recruitment of a new Metro Front-End Engineer.
  • The number of applicants has been low and an external agency has been sourced to actively recruit for the position.

Metro Performance Summary

• Total Work: 122 total story points - 35 bugs.
  • 5 existing feature changes.
  • 18 existing feature defects.
  • 12 new features.

• Completed Work: 49 story points closed - 21 bugs - 40% complete.
  • 3 existing feature change.
  • 12 existing feature defects.
  • 6 new features

• Remaining Work: 73 story points remaining - 14 bugs - 60% complete
  • 2 existing feature changes.
  • 6 existing feature defects.
  • 6 new features.

Metro Work Details

Sheila

• Firefox Health Report
  • Uplifted to Fx21 beta
  • Tracking final pieces
  • QA and metrics verification
• FFOS
  • Attending Madrid work week
  • Helping Dietrich and Michael track 1.0.1 and 1.1 activities
  • Working with Taipei PMs on creating a closer working relationship
• Stability
  • Kairo organization stability work week
  • Helping team with some coordination and planning
• JS team looking for PM help - meeting with Naveed to discuss details