MDN/Development Process: Difference between revisions

← Older edit

MDN/Development Process (view source)

Revision as of 21:07, 19 April 2011

517 bytes added , 19 April 2011

→‎TL;DR

Groovecoder

Confirmed users

556

edits

@@ Line 1: / Line 1: @@
+= TL;DR =
+[http://prezi.com/s5f-yay7gfv-/mdn-dev-process/ MDN Dev Process Prezi]
+[http://blog.johnath.com/2011/04/19/deliberacy/ Firefox Features Development]
 = Product Planning =
-* Bi-weekly, 15-60m
+During product planning meetings we set product milestones. We discuss milestone goals & objectives - esp. release dates & success metrics. Product planning meetings set the backlog of milestones.
-* 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 ==
+* Schedule - Bi-weekly Wednesdays @ 10am PST, 15-60m
-Product Backlog in the form of accurate bugzilla bugs and milestones
+* Attendees - All MDN Stakeholders: Engagement+, Product+, Dev+, Legal?, QA?, IT?
+* Agenda
+** Carry-over any outstanding milestones
+** Introduce new milestones
+* Output
+** basecamp milestones & tasks
+** accurate bugzilla milestones
+** update [MDN#Current_Projects]
 = Dev Planning =
-* Weekly, 15-60m
+* Schedule - Bi-weekly Thursdays following Product Planning @ 10am PST, 15-60m
-* Product
+* Attendees - Product+, Dev+, QA+, IT?
-* Developers
+* Agenda
-* QA
+** Retro - celebrate every push, give kudos; encourage what worked and fix what didn't work in last sprint
-* IT (optional)
+** Triage - prioritize new bugs (use bugzilla)
+** Planning - Developers review milestones' bugs with Product and add everything necessary for dev - implementation details, resources, risk, effort, etc.
-== Agenda ==
+** Roadmap - briefly summarize Product Planning meeting for anyone who skipped it
-* Retro
+* Output - Sprint backlog in the form of dev + product-approved bugzilla bugs for immediately active milestone(s)
-** Celebrate all code pushes & give kudos
-** Look back at the last "sprint" - what worked, what didn't, and what should we improve?
-* Triage & Planning
-** Developers review milestones' bug backlog with Product and adjust according to developer input - implementation details, resources, risk, effort, etc.
-** Triage new bugs and set milestones
-* Roadmap
-** Briefly (5m) discuss upcoming non-immediate work so no-one is surprised by anything.
-== Output ==
-Sprint backlog in the form of dev + product-approved bugzilla bugs for immediately active milestone(s)
 = Standup =
-* Daily, 5-10m
-* Developers
-* Product
-== Agenda ==
-Round-robin: What I did yesterday. What I'm doing today. Blockers, if any.
 Standup is a very short (5-10m) daily meeting to make sure everyone is on the same page.
-== Output ==
+* Schedule - Daily @ 10am PST, 5-10m
-Warm fuzzies
+* Attendees - Developers & Product
+* Agenda - Round-robin:
+** What I did yesterday.
+** What I'm doing today.
+** Blockers, if any.
+* Output - warm fuzzies
 = Bugs =
@@ Line 49: / Line 43: @@
 == Status Flow ==
 Bugs should typically flow thru the team:
-* Product & QA & Dev
+* Product, QA, or Dev
 ** (Unconfirmed) -> New
+** (Unconfirmed) -> Resolved:wontfix/invalid/worksforme/duplicate/incomplete
+* Product & Dev
+** Add milestone during [[MDN/Development_Process#Dev_Planning | dev planning]]
 * Dev
 ** New -> Assigned -> Resolved:Fixed
@@ Line 68: / Line 65: @@
 * Normal, etc. - Nice-to-have, work on between other bugs
 ** (e.g., style changes, annoyances)
+= Push =
+* Monthly on Tuesdays before Product Planning
+See [[https://intranet.mozilla.org/Webdev:MDN#Production_Push MDN Production Push]]