Gaia/SMS/Scrum: Difference between revisions
| Line 24: | Line 24: | ||
=== Daily Meeting === | === Daily Meeting === | ||
It happens on IRC irc.mozilla.org/#gaia-messaging every weekday at | It happens on IRC irc.mozilla.org/#gaia-messaging every weekday at 08:45 GMT. Minutes will be archived below. | ||
First, the person who attended latest Comms Daily Meeting will do a quick summary about what happens in other teams. | First, the person who attended latest Comms Daily Meeting will do a quick summary about what happens in other teams. | ||
Revision as of 08:58, 28 April 2014
Current Velocity: ?
Current Sprint: #0
Rules
Sprint Planning
Input: we have a list of bugs to use, with a rough priority. Currently, the priority is 1.3+, then 1.4+, then 2.0 commited features
Between 50 and 70% (depending on the moment in the release cycle) of the velocity will be used for these bugs. The rest of the velocity is to be kept for blockers appearing during the sprint.
We take the list of bugs in the order of priority, and estimate them together (see Estimation below).
When we reached the available velocity, we stop.
All the taken bugs are blocking a meta bug representing the current sprint.
Estimation
- we estimate relatively to other bugs. As first bug to help estimate, we'll take a bug that needed around 2 days to fix (including tests, reviews, discussions), and we'll assume its complexity (or "p-value") is 1 point. Then all other estimations will be done relatively to this bug and other bugs.
- we can estimate using 1, 2, 3, 5.
- We never estimate with less than 1
- bugs that needs more than 5 needs to be made "meta" and we need to file smaller individual bugs. This will need to be done during the planning so it's better if someone can do it ahead of time.
- Only the developers that feel they can estimate do the estimation. That means it's perfectly fine to not take part to a bug's estimation if you don't feel you can.
Daily Meeting
It happens on IRC irc.mozilla.org/#gaia-messaging every weekday at 08:45 GMT. Minutes will be archived below.
First, the person who attended latest Comms Daily Meeting will do a quick summary about what happens in other teams.
Everyone will have up to 2 minutes to tell the following things:
- what he did since the last daily meeting
- what he'll do until the next daily meeting
- is he blocked on something
This is not the place where we unblock things. But this is the place where we know there are things to unblock, and so a follow-up will need to happen.
Then unless somebody has something else to say, the meeting ends.
Comms Daily Meeting
One developer of the team will attend this daily meeting. He will summarize what happened on our team (including our blockers) to report to other teams. He will also get other teams' report to report to our team the day after.
The developer that attend the meeting can be different.