Confirmed users
556
edits
MDN/Development Process: Difference between revisions
→TL;DR
Groovecoder (talk | contribs) |
Groovecoder (talk | contribs) (→TL;DR) |
||
| (4 intermediate revisions by the same user not shown) | |||
| 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 = | = Product Planning = | ||
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. | 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. | ||
| Line 10: | Line 14: | ||
** basecamp milestones & tasks | ** basecamp milestones & tasks | ||
** accurate bugzilla milestones | ** accurate bugzilla milestones | ||
** update [MDN#Current_Projects] | |||
= Dev Planning = | = Dev Planning = | ||
* | * Schedule - Bi-weekly Thursdays following Product Planning @ 10am PST, 15-60m | ||
* Product | * Attendees - Product+, Dev+, QA+, IT? | ||
* Agenda | |||
** Retro - celebrate every push, give kudos; encourage what worked and fix what didn't work in last sprint | |||
* | ** 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. | |||
** 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) | ||
* Triage | |||
** Developers review milestones' | |||
* | |||
* Roadmap | |||
* | |||
Sprint backlog in the form of dev + product-approved bugzilla bugs for immediately active milestone(s) | |||
= Standup = | = Standup = | ||
| Line 48: | Line 43: | ||
== Status Flow == | == Status Flow == | ||
Bugs should typically flow thru the team: | Bugs should typically flow thru the team: | ||
* Product | * Product, QA, or Dev | ||
** (Unconfirmed) -> New | ** (Unconfirmed) -> New | ||
** (Unconfirmed) -> Resolved:wontfix/invalid/worksforme/duplicate/incomplete | |||
* Product & Dev | |||
** Add milestone during [[MDN/Development_Process#Dev_Planning | dev planning]] | |||
* Dev | * Dev | ||
** New -> Assigned -> Resolved:Fixed | ** New -> Assigned -> Resolved:Fixed | ||
| Line 67: | Line 65: | ||
* Normal, etc. - Nice-to-have, work on between other bugs | * Normal, etc. - Nice-to-have, work on between other bugs | ||
** (e.g., style changes, annoyances) | ** (e.g., style changes, annoyances) | ||
= Push = | |||
* Monthly on Tuesdays before Product Planning | |||
See [[https://intranet.mozilla.org/Webdev:MDN#Production_Push MDN Production Push]] | |||