Confirmed users
820
edits
Gaia/SMS/Scrum/1: Difference between revisions
→Retrospective
| (2 intermediate revisions by the same user not shown) | |||
| Line 62: | Line 62: | ||
== Sprint planning == | == Sprint planning == | ||
The minutes are stored [[Gaia/SMS/Scrum/Planning | The minutes are stored [[Gaia/SMS/Scrum/1/Planning|in a separate page]]. | ||
== Daily meetings == | == Daily meetings == | ||
| Line 554: | Line 554: | ||
== Retrospective == | == Retrospective == | ||
=== What was good in the last sprint === | |||
* we finished the sprint ! | |||
* I finished the navigation patch (at last !) yay :) | |||
* I like that we discuss every day about SMS only things +1 | |||
* it was good to have the visual design team in the daily meetings | |||
=== What was bad in the last sprint === | |||
* Still tones of blocker... (v1.3t/v1,4) Not sure when it will be ended | |||
*:-> what can we do about this? at least try to know when it will finish? | |||
*:-> Maybe that will help whether we should keep more resource on blockers | |||
* It's still difficult for me to quickly find source of truth for VR (a lot of mocks, some of them outdated and etc.) +1 | |||
*:-> we already discussed about this with Victoria but nothing changed; let's discuss this again later today.+1 | |||
=== Any questions === | |||
* Could we have more easy way to update our status? You mean, every day?Yep, for example, maybe we could have a google doc for bug id/status and we can update if before meeting(or update to wiki directly, we don't need to copy/paste everyday) and just update if something really blocked in the scrum. | |||
*:The goal of the daily meeting is not really the status, it's more to discuss together. So I'm happy to change it to make it more useful. Oleg what are your thoughts? | |||
*:Mmm, having some centralized doc\wiki (with bug<->status) will be good for Mon\Wed\Fri Comms meeting, not sure whether anyone else read our minutes. Regarding to daily meetings in IRC - I like it :) | |||
*:Would it make sense to do the daily meeting partly in an etherpad too ? (like we do here now) We'd have etherpad for the bugs (and this way we can just add a line every day, for example) and IRC for other discussions | |||
* is the sprint the right size? is 2 weeks fine? I think 2 is the right one, 1 is too small, 3 is too big. | |||
=== Actions === | |||
* we need to know when the blocker phases end (especially when will 1.3t+ end?). +1 | |||
* have a centralized place for all uptodate visual design material | |||
* daily meeting: use etherpad as a more synthetic way to update the bug status, and keep IRC as discussion backchannel(+1) | |||