Gaia/SMS/Scrum: Difference between revisions

From MozillaWiki
< Gaia‎ | SMS
Jump to navigation Jump to search
Line 3: Line 3:
'''Current Sprint''': [[Gaia/SMS/Scrum/3|#3]]
'''Current Sprint''': [[Gaia/SMS/Scrum/3|#3]]


== Current Sprint ==
== Current Sprint: [[Gaia/SMS/Scrum/3|Sprint #3]] ==
=== SMS issues handled by the SMS subteam (blocks the sprint {{bug|1022706}}) ===
=== SMS issues handled by the SMS subteam (blocks the sprint {{bug|1022706}}) ===
[https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&o1=substring&query_format=advanced&v1=1022706 Bugzilla link]
[https://bugzilla.mozilla.org/buglist.cgi?f1=blocked&o1=substring&query_format=advanced&v1=1022706 Bugzilla link]

Revision as of 10:09, 10 June 2014

Current Velocity: 8

Current Sprint: #3

Current Sprint: Sprint #3

SMS issues handled by the SMS subteam (blocks the sprint bug 1022706)

Bugzilla link

Full Query
ID Assigned to Summary Blocking b2g Feature-b2g Whiteboard Resolution
925404 Oleg Zasypkin [:azasypkin] [B2G] [SMS] Always include the phone number in the SMS Thread UI, even if the carrier is known --- No cf_feature-b2g burirun2, burirun3, [lang=js][lang=css][p=2][not-part-of-initial-sprint] FIXED
994553 Steve Chung [:steveck] [Sora][Message][Contacts]Contacts's head portrait do not display in Message 1.4+ No cf_feature-b2g [p=2] FIXED
1008127 Pavel Ivanov [:ivanovpavel][:pivanov] UX [Messages][Refresh] Subject handling in the Composer --- No cf_feature-b2g [sprint2 p=3][sprint3 p=2][not-part-of-initial-sprint] FIXED
1012663 Oleg Zasypkin [:azasypkin] [SMS] Remove inline style for CSP compliance --- No cf_feature-b2g [sms-most-wanted][p=1] FIXED
1013296 Arnau March [:arnau] ( not working in Firefox OS anymore :( ) Compose. Change send button to an paper plane icon --- No cf_feature-b2g [p=1][not-part-of-initial-sprint] FIXED
1015867 Julien Wajsberg [:julienw] [Messages] The editable composer should take more space 2.0+ No cf_feature-b2g [sprint2 p=2][sprint3 p=1] FIXED
1016897 Steve Chung [:steveck] [Flame][v1.4][Message]Tap new message icon, it will automatically return SMS which is just saved as draft. .And if then tap Back key, this contact will have 2 SMS items in main message view. 1.4+ No cf_feature-b2g bamboo[p=1] FIXED
1018035 Julien Wajsberg [:julienw] [Flame][v1.4][SMS]No cursor display when tap the message edit box. 1.4+ No cf_feature-b2g torch, [not-part-of-initial-sprint] FIXED
1022096 Julien Wajsberg [:julienw] [Messages] sms text truncated in delete messages mode 2.0+ No cf_feature-b2g [2.0-FL-bug-bash][not-part-of-initial-sprint] FIXED
1024978 Julien Wajsberg [:julienw] [Messages] Activity Handler tests are failing with newer mocha --- No cf_feature-b2g [not-part-of-initial-sprint] FIXED
1025552 Oleg Zasypkin [:azasypkin] [Messages][Refactoring] Refactor attachment.js and specifically move rendering part to a separate module --- No cf_feature-b2g [p=1] FIXED
1026528 Oleg Zasypkin [:azasypkin] [Messages] Corrupted attachments do not display correctly 2.0+ No cf_feature-b2g [not-part-of-initial-sprint] FIXED

12 Total; 12 Open (100%); 0 Resolved (0%); 0 Verified (0%);


All SMS issues tracked for this sprint (target milestone)

Bugzilla link

Full Query
ID Assigned to Summary Blocking b2g Feature b2g Resolution
925404 Oleg Zasypkin [:azasypkin] [B2G] [SMS] Always include the phone number in the SMS Thread UI, even if the carrier is known --- --- FIXED
974867 Naoya Matsumoto [MMS]Auto suggestion for email address --- --- FIXED
994553 Steve Chung [:steveck] [Sora][Message][Contacts]Contacts's head portrait do not display in Message 1.4+ --- FIXED
1005866 Fernando Campo (:fcampo) [Messages] Confirmation button when deleting messages and threads should be in Red and say "Delete" - --- FIXED
1012663 Oleg Zasypkin [:azasypkin] [SMS] Remove inline style for CSP compliance --- --- FIXED
1015867 Julien Wajsberg [:julienw] [Messages] The editable composer should take more space 2.0+ --- FIXED
1016897 Steve Chung [:steveck] [Flame][v1.4][Message]Tap new message icon, it will automatically return SMS which is just saved as draft. .And if then tap Back key, this contact will have 2 SMS items in main message view. 1.4+ --- FIXED
1018035 Julien Wajsberg [:julienw] [Flame][v1.4][SMS]No cursor display when tap the message edit box. 1.4+ --- FIXED
1019359 Paco Rampas [:paco] [Sora][Message] The "slecet all/deselect all"still can use when it display as grey. 1.4+ --- FIXED
1021788 Steve Chung [:steveck] [Messages] Can't click on the suggestion list when there are a lot of recipients in the recipients panel 2.0+ --- FIXED
1021844 Julien Wajsberg [:julienw] [Messages] Can't load the application in Firefox --- --- FIXED
1022096 Julien Wajsberg [:julienw] [Messages] sms text truncated in delete messages mode 2.0+ --- FIXED
1022706 [meta] SMS subteam sprint 3 --- --- INCOMPLETE
1024978 Julien Wajsberg [:julienw] [Messages] Activity Handler tests are failing with newer mocha --- --- FIXED
1026528 Oleg Zasypkin [:azasypkin] [Messages] Corrupted attachments do not display correctly 2.0+ --- FIXED
1026671 Guillaume Marty [:gmarty] Header Font in Messages App Does Not Center Align --- --- WORKSFORME

16 Total; 16 Open (100%); 0 Resolved (0%); 0 Verified (0%);


Previous sprints

Rules

Sprint Planning

Input: we have a list of bugs to use, with a rough priority. Here is a list of queries:

blockers

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


nominations

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Features

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


"SMS most wanted" list

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Priority list

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Priority order

Currently, rough priority order is: 1.3+, 1.3t+, 1.4+, Features, 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). We can also take some technical debt bugs (at least 1 per sprint would be nice), identified by [sms-most-wanted] in the whiteboard

When we reach 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.
  • 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 and etherpad every weekday at 08:45 GMT. Minutes will be archived in the Sprint page.

Each attendee adds the following information to the etherpad:

  • what he did since the last daily meeting
  • what he'll do until the next daily meeting
  • is he blocked on something

Then he writes "updated the XXXX" on top of its part, to make it clear he finished updating its current status.

Other attendees can comment directly in the etherpad, by specifying the first name in front of their comment.

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 add, the meeting ends.

Comms Daily Meeting

Every developer of the team will attend this daily meeting but only one will speak. He will summarize what happened on our team (including our blockers) to report to other teams.

The developer that speaks can be different at different occurrences. For example, it can be the first one that's asked to speak.

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 on etherpad, 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.