Gaia/SMS/Scrum
(Note: all these rules are subject to be discussed among the SMS subteam members before applying them)
Current Velocity: 12
Current Sprint: #0
Sprints
Sprint #1: 20141205 -> 20141223
http://mzl.la/1fUDBz9: SMS issues handled by the SMS subteam (blocks the sprint bug)
| ID | Assigned to | Summary | Blocking b2g |
|---|---|---|---|
| 871432 | Steve Chung [:steveck] | [sms][mms] display the received time inside the sms/mms box | --- |
| 881469 | Julien Wajsberg [:julienw] | [MMS] Implement Navigation object | --- |
| 963013 | Oleg Zasypkin [:azasypkin] | [Messages][Refresh] Update bubbles style and layout of the thread. | --- |
| 980461 | Oleg Zasypkin [:azasypkin] | [MMS] Visual adjustments to attachment download indicator | --- |
| 1003384 | Oleg Zasypkin [:azasypkin] | [B2G][1.4][SMS] - The phone type "Other" is not translated in any of the languages when suggested contacts are shown in SMS | 1.4+ |
| 1008823 | Oleg Zasypkin [:azasypkin] | [Messages] Don't use activity to send message via "Send Message" action from unknown number context menu | --- |
| 1010301 | Oleg Zasypkin [:azasypkin] | [B2G]][Messaging App] Spinning icon when sending an sms and mms is not displayed | --- |
7 Total; 7 Open (100%); 0 Resolved (0%); 0 Verified (0%);
http://mzl.la/1ggINs4: All SMS issues tracked for this sprint (target milestone)
15 Total; 15 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Minutes
Retrospectives
Sprint Plannings
Sprint #1 - Monday 12th May 2014
Daily Meetings
27th April 2014
Rules
Sprint Planning
Input: we have a list of bugs to use, with a rough priority. Here is a list of queries:
1.3+: http://mzl.la/1mIa1jx
1.3t?: http://mzl.la/1nvSyrz
1.3t+: http://mzl.la/Rv2eaI
1.4?: http://mzl.la/1oxwb50
1.4+: http://mzl.la/1nvSIiE
2.0?: http://mzl.la/1fUcgNt
2.0+: http://mzl.la/1norXyX
Visual Refresh: http://mzl.la/1mIcKth
Priority order
Currently, rough priority order is: 1.3+, 1.3t+, 1.4+, Visual Refresh, 2.0+. We can have a look to the nominations (1.4?, etc) too.
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). (QUESTION: I think we should also take some technical debt bugs, what do you think?)
When we reached the available velocity, we stop.
All the taken bugs are blocking a meta bug representing the current sprint.
Estimation
(NOTE: as a rough estimation, we can say 1 bug = 1 point, and skip this; up to you. But IMO doing the real planning thing helps us having a common understanding of the bugs).
- 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 at different occurrences, but it needs to be known in advance. For example this could be always the same developer during one sprint (TBD).
(NOTE: this was rejected by the Comms Team management for now; still we can do this, all attend the meeting, but only the selected representative talks)
Demo
Every sprint must end by a demo of what happened during the sprint.
Retrospective
This is the place where we change rules.
Everybody must think ahead of time to what was good and bad during last sprint. Could be anything, even if it's more an invididual thought. You need also to think of any question you have.
During the meeting, everybody dumps this, and then we take some time to review them. Ideally, all bad things and questions end up to actions to improve things, and the 3 most important actions (choosen by the team) will need to be done in the next sprint.