MDN/Development Process: Difference between revisions
Groovecoder (talk | contribs) No edit summary |
Groovecoder (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
= | = Meetings = | ||
== Product Planning == | == Product Planning == | ||
=== Frequency === | === Frequency === | ||
Bi-weekly | Bi-weekly | ||
| Line 13: | Line 11: | ||
=== Agenda === | === 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 === | === Output === | ||
| Line 18: | Line 17: | ||
== Development Planning == | == Development Planning == | ||
=== Frequency === | === Frequency === | ||
Weekly | Weekly | ||
| Line 30: | Line 27: | ||
=== Agenda === | === 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 ==== | ==== Retro ==== | ||
* Celebrate all code pushes & give kudos | * Celebrate all code pushes & give kudos | ||
| Line 42: | Line 41: | ||
=== Output === | === Output === | ||
Developer + Product-approved bugzilla bugs | 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. | |||
Revision as of 17:28, 3 February 2011
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.