Confirmed users
1,193
edits
MDN/Development/Process: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
=== Sprint Backlogs === | === Sprint Backlogs === | ||
At each [[MDN/Development/Process#Planning_and_Retrospective_Meeting|Sprint Planning meeting]], the development team decides what features it should complete in the upcoming Sprint | At each [[MDN/Development/Process#Planning_and_Retrospective_Meeting|Sprint Planning meeting]], the development team decides what features it should complete in the upcoming Sprint. The individual tasks that are needed to complete those features are captured in a list called the <em>Sprint Backlog</em>. A different Sprint Backlog is used for each Sprint. | ||
The team maintains its [[http://scrumbu.gs/t/mdn/ Sprint Backlogs]] on Scrumbugs. | The team maintains its [[http://scrumbu.gs/t/mdn/ Sprint Backlogs]] on Scrumbugs. | ||
==== Organization ==== | ==== Organization ==== | ||
| Line 32: | Line 30: | ||
The team finds research tasks to be especially valuable. For example, when starting the user user login feature, the team might create a task like "Research: What services can we use to power login?". The team discusses the question and shares decisions in an associated Bugzilla bug. | The team finds research tasks to be especially valuable. For example, when starting the user user login feature, the team might create a task like "Research: What services can we use to power login?". The team discusses the question and shares decisions in an associated Bugzilla bug. | ||
=== Sprint Burndown Charts === | |||
The team uses a <em>Sprint Burndown Chart</em> during each Sprint to measure progress. A Sprint Burndown Chart has amount of work on the y-axis and time on the x-axis, so that the trend line gradually moves toward the bottom right of the chart as work as completed. | |||
The team maintains [[[http://scrumbu.gs/t/mdn/ Burndown Charts]] on Scrumbugs. A Burndown Chart is shown on the same page as its associated Sprint Backlog. | |||
=== Velocity === | === Velocity === | ||
To estimate how much work can be completed in each Sprint, the team measures its development speed or <em>Velocity</em>. Velocity is measured in <em>story points</em>, unitless values of development effort. | |||
The team calculates its [https://docs.google.com/spreadsheet/ccc?key=0AtSmmChL-hpUdFNXeFVwbmZGMDFzbUhVQS1oQ0FnbFE#gid=1 Velocity] using Google Docs. | |||
=== Status reports === | === Status reports === | ||
| Line 55: | Line 63: | ||
==== Planning ==== | ==== Planning ==== | ||
In the second part of the meeting, the team decides what features it should complete in the upcoming Sprint based on the priorities reflected in the [[MDN/Development/Process#Product_Backlog|Product Backlog]]. The team aims for variety in the features it chooses so that everyone can find something interesting to work on. The team plans to complete about two-thirds of the work it normally completes as reflected in its [[MDN/Development/Process#Velocity|Velocity]]. The remaining one-third of work is left open for other features that developers choose based on their interests. These features are not added to the Sprint Backlog because doing so would complicate our Velocity and cause bumps in our Sprint Burndown chart. | In the second part of the meeting, the team decides what features it should complete in the upcoming Sprint based on the priorities reflected in the [[MDN/Development/Process#Product_Backlog|Product Backlog]]. Tasks needed to complete these features are captured in the Sprint Backlog. | ||
The team aims for variety in the features it chooses so that everyone can find something interesting to work on. The team plans to complete about two-thirds of the work it normally completes as reflected in its average [[MDN/Development/Process#Velocity|Velocity]]. The remaining one-third of work is left open for other features that developers choose based on their interests. These features are not added to the Sprint Backlog because doing so would complicate our Velocity and cause bumps in our Sprint Burndown chart. | |||
After building the Sprint Backlog, the team plays [http://en.wikipedia.org/wiki/Planning_poker Planning Poker] to discuss the tasks in more detail and estimate how long it will take to complete each. If the team realizes that it has taken on too much or too little work, it adds or removes features from the Sprint Backlog accordingly. | After building the Sprint Backlog, the team plays [http://en.wikipedia.org/wiki/Planning_poker Planning Poker] to discuss the tasks in more detail and estimate how long it will take to complete each. If the team realizes that it has taken on too much or too little work, it adds or removes features from the Sprint Backlog accordingly. | ||