MDN/Development Process

Meetings

Product Planning

Frequency

Bi-weekly

Attendees

• Stakeholders
• Product
• Developers
• QA (optional?)

Agenda

During product planning meetings we set the immediate product goals and objectives. We introduce new features, discuss enhancements to existing features, review new and outstanding bugs, and prioritize. Product planning meetings set the backlog - we create bugs, update bugs, assign milestones to bugs, remove milestones from bugs.

Output

Accurate bugzilla bugs with milestones

Development Planning

Frequency

Weekly

Attendees

• Product
• Developers
• QA (optional?)
• IT (optional)

Agenda

Development planning meetings synchronize product & development efforts. Developers review the milestones' backlog with Product and adjust according to developer input - implementation details, resources, risk, effort, etc.

Retro

• Celebrate all code pushes & give kudos
• Look back at the last "sprint" - what worked, what didn't, and what should we improve?

Planning

• For each active milestone, review outstanding bugs and plan new bugs. Discuss implementation details with Product.

Roadmap

Briefly (5m) discuss upcoming non-immediate work so no-one is surprised by anything.

Output

Developer + Product-approved bugzilla bugs

Standup

Standup is a very short (5-10m) daily meeting to make sure everyone is on the same page.

Frequency

Daily

Attendees

• Developers
• Product

Agenda

Round-robin: What I did yesterday. What I'm doing today. Blockers, if any.

Bugs

Status Flow

Bugs should typically flow thru the team:

• Product & QA & Dev
  • (Unconfirmed) -> New
• Dev
  • Assigned -> Resolved:Fixed
• QA
  • Resolved:Fixed -> Reopened or Verified:Fixed -> Closed