MozillaWiki

Firefox/IterativeDevelopment

< Firefox
Revision as of 16:09, 10 February 2014 by GavinSharp (talk | contribs) (→‎General)

Firefox Desktop Iterative Development

Objectives

The Iterative Development Model implemented for Firefox Desktop aims to accomplish six key objectives:

  • Transparent - Who is working on what, when, and why.
  • Predictable and Repeatable - Know what to expect from the process.
  • Inclusive - Include all key participants (Eng, UX, QA, Product) and stakeholders in the process.
  • Clear Direction and Decision Making - Know what we should do and who makes the call.
  • Clear and Stable Priorities - Be clear on what is most important for each iterative cycle.
  • Innovative - Provide flexibility to engage in experimental and original projects.

Production Summary

Note: Next update on Tuesday March 04 following the conclusion of Iteration IT-30C-29A-28B.2

At the conclusion of Iteration ##:

  • Points Completed: ##
  • Bugs Resolved: ##
  • Team Velocity: ##
  • Velocity Range: ##

Development Update

Note: Next update on Tuesday March 04 following the conclusion of Iteration IT-30C-29A-28B.2

Product Backlog

All work related to the ongoing development and maintenance of the Firefox Desktop Product are collected and prioritized in the Product Backlog. The goals of the Product Backlog are to:

  • Enable work 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 direction of the product.

The Product Backlog is maintained by the Senior Management team (Chad, Gavin, Madhava) at the Product Backlog Refinement Meeting to ensure new priorities are available for each Sprint Planning meeting.

Product Backlog: View Bugzilla

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Release Plan

The Release Plan is a guideline that reflects expectations about which features from the Product Backlog will be implemented and when they are completed across multiple iterations for specific target releases. It also serves as a base to monitor progress with the ongoing development of the product. The Release Plan is not static and will be revisited and updated at the conclusion of each iteration.

Iterations

The Iteration Backlog is a collection of Work that the team has committed to implement, test and deliver in a two-week iteration.

Current Iteration: IT-30C-29A-28B.2 - Tue 02/18/14 - Mon 03/03/14

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Definition of Done

The Definition of Done ensures a potentially shippable product increment is released at the conclusion of a release cycle.

Potentially Shippable Guidelines:

  • Means Tested and Verified
  • Does Not Mean Cohesive

Tested and Verified

  • QA will be flagged to test work marked as 'Resolved' within the iteration.
  • Any defects found will 'Reopen' the work subject to testing.
  • If QA does not discover any defects the work will be marked as 'Verified'.
  • Only 'Verified' work will merge into a build at the conclusion of the release cycle.

Product Increment

  • A potentially shippable product increment means compliance with the work's individual acceptance criteria and not the full story under development.

Bugzilla

The following format is used to maintain consistency in how bugs are filed:

  • p= (point value assigned to the bug)
  • s= (the iteration the bug is being developed in)
  • r= (the target release of the bug under development)
  • [story] (collection of related bugs required for the completion of a feature)

Roles and Responsibilities

Role Contacts
Project Champion
Program/Project Management
  • Monitor team and project performance
  • Submit status report at conclusion of each Iteration
  • Organize and facilitate Triage and Planning meetings
  • Guide team through the practices and procedures of the project
  • Ensure team and project impediments are addressed
Product Manager
  • Define and document product features
  • Maintain Product Backlog, Feature Stories up-to-date and prioritized
  • Review Iteration Build Release
UX/Design
  • Self-organizing and self-managing; team determines how much work they can commit to from the Product Backlog during each Iteration Planning meeting
  • Deliver UX assets/work necessary to progress work in backlog
  • Responsible for attending Planning meetings
  • Report impediments to the Project Manager
  • Keep work item, Feature Story and Epic status up-to-date
Dedicated Engineering
  • Self-organizing and self-managing; team determines how much work they can commit to from the Product Backlog during each Iteration Planning meeting
  • Deliver build for every sprint consisting of work from sprint backlog
  • Responsible for attending Planning meetings
  • Report impediments to the Project Manager
  • Keep work item, Feature Story and Epic status up-to-date
Localization
QA
  • Create and execute test plans
  • Verify acceptance criteria
  • Responsible for attending Planning meetings
  • Report impediments to the Project Manager
Privacy
Release Management
Marketing
Legal
Feedback

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

Communication

General

Backlog Refinement Meeting

  • Time: Fridays - 12:00 - 2:00 (PST), 3:00 - 5:00 (EST)
  • Duration: 2 hour(s)
  • Vidyo Room: "Firefox"
  • Etherpad: View Team Page

Sprint Planning/Review and Status Meeting

  • Time: Tuesdays - WHAT TIME Pacific, WHAT TIME Eastern
    • First Tuesday focussed on Sprint Planning/Review.
    • Second Tuesday focussed on Team Update.
  • Duration: 2 hour(s)
  • Vidyo Room: "Firefox"
  • Etherpad: View Team Page

Feature Pitch

  • Time: WHAT DATE - WHAT TIME Pacific, WHAT TIME Eastern
  • Duration: ## hour(s)
  • Vidyo Room: "VIDYO ROOM NAME"
  • Etherpad: TBD

Iteration Performance Reports

  • Iteration IT-30C-29A-28B.2: Tue 02/18/14 - Mon 03/03/14 - [View Performance Report]
  • Previous Reports - [View Archive]

Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox/IterativeDevelopment&oldid=922755"