Confirmed users
821
edits
Gaia/SMS/Scrum/4: Difference between revisions
Jump to navigation
Jump to search
→Retrospective
| Line 443: | Line 443: | ||
== Demos == | == Demos == | ||
== Retrospective == | == Retrospective == | ||
===Previous sprint's actions=== | |||
* invite all people that work on SMS to daily meetings (this time, we were missing Pavel, Marina) => It seems we didn't make it... (still this) | |||
* better identify that bugs will target the same area (eg: composer bugs); ideally we need to span them on several sprints, so we need to identify well in advance | |||
*: (Julien) did it work better ? I was not here in the planning | |||
*: (Oleg) I'd say that we didn't do anything related to that action :) | |||
* New blocker which is taken by the developers should be reported in the scrum and estimate the point. | |||
*: (Julien) should we estimate the bugs we did after the fact? (I think we should not; it doesn't give much value to estimate them after the fact) | |||
*: (Oleg) agree, the value is "pre" estimation, when we can raise questions\concerns and even abandon\delay the bug | |||
*: (Julien) I like that we report the bug in the sprint (the current way is fine for me; maybe confusing if one bug is in several sprints like for the subject bug 1008127, since you added "not part of the initial sprint" it disappeared from previous sprints :) not a big deal ) | |||
===What was good in the last sprint=== | |||
* Sprint was completed | |||
* We've landed the rest of VR (at least the biggest parts); | |||
* I think we did bigger amount of work then in the previous sprint; +1 | |||
*: (Julien) why did we do more work, after you ? | |||
*: (Oleg) I think we initially picked up bugs that was 100% clear and not much VR bugs that depends on UX :) | |||
*: (Julien) good point. We need to take INVEST bugs only (http://en.wikipedia.org/wiki/INVEST_%28mnemonic%29). (mmm maybe it's not the right word here; let's say we need to take actionable and clear bugs :) ) | |||
*: (Oleg) Yeah, it makes next steps more predictable and you feel better :) | |||
*: Also as we planned just 7 points for the sprint, we estimated few bugs more, like next-tasks-to-do pool. But probably if we estimate better and pick up clear bugs we won't need it. | |||
* Oleg did scrum master stuff (so I did less ;) ) :) | |||
===What was bad in the last sprint=== | |||
* We did a lot of work marked as [not-part-of-the-sprint] +1 | |||
* comms standup meeting: too many of them, and in the same time, too few interactions with UX/VD in stand up. | |||
*: Yeah, I didn't feel much value from comms standup, maybe it's only me. | |||
===Any questions=== | |||
* David told me the name of our sprint is confusing and that we should use eg "2.0 S6" like everybody else. What do you think? | |||
*: (Oleg) Mmm I'm fine with the current one, but I'm not sure what other do and what 2.0 means | |||
*: (Julien) "2.0" means version 2.0, "S" means "Stabilization". "6" means "sprint 6" | |||
*: (Oleg) After all it doesn't really matter for us how it's named | |||
*: (Julien) yep, that's also what I think, we don't really mind. So next one is 2.0S6 ? | |||
*: (Oleg) yep | |||
* Oleg: do you want to keep the scrummaster role for the upcoming sprint? (I mean, managing the scrum pages) I can prepare the page from the planning though. | |||
*: (Oleg) I don't mind, anyway mainly you and Steve give updates on Comms, so I'd like to help anyhow :) | |||
*: (Julien) about updates, it would be better if it can cycle; maybe when it's Steve turn (it's always Steve turn first) he can ask you or me to speak instead. | |||
*: (Oleg) yeah, that should work. Agree, soon we won't have that many of Comms meetings :) | |||
*: (Julien) about the full scrum master role, we can discuss/define more formally in a few weeks what it should be, so that it's easier to make it cycle too (especially that I'll be away 3 weeks in august/september) | |||
* have UX/VD join our sms stand up meeting, not always, but maybe once or twice a week ? | |||
*: (Oleg) Probably on sprint planning we can see whether we'll need UX help during sprint, and plan meeting\s accordingly, it can be 0 if we don't anything to do with UX | |||
*: (Julien) stand up meetings is a good opportunity to discuss things that happen now... but maybe we didn't miss that so much after all and I'm wrong. | |||
*: (Oleg) also we'll have to ask UX what is acceptable for them :) | |||
*: (Julien) exactly; but NI works fine too for this. | |||
===Actions=== | |||
* Try harder to take only actionable and clear bugs | |||
* we'll use the same sprint names than everybody else. Next sprint is 2.0S6. | |||
* If we still have Comms standup someway, Steve can ask Oleg or Julien to speak for the team :) | |||
* define what the scrummaster role is/should be (not for this sprint though) | |||
* estimate quality metrics only once every 3 sprints. | |||
===Grades (5 is very good, 1 is very bad)=== | |||
(should we keep this? I feel like it's useless after all, I feel the same for now) | |||
*: (Oleg) I mean that from sprint to sprint not much changes, all characteristics still almost the same. I think it's useful for longer periods than one sprint. | |||
*: (Julien) it's useful if we take actions to make them better. Maybe keep only some? | |||
*: (Oleg) I think quality parameters is more long term (I believe we can't change from 3 to 4 during sprint or two), Commited vs Completed is good characteristic even for single sprint | |||
*: (Julien) maybe not estimate the quality parameters in all sprints, but only once every 3 sprints ? or every version ? | |||
*: (Oleg) Yeah, I like the parameters itself, but we need more time to change it, maybe 3 sprints can work, let's try | |||
*: (Julien) ok, let's do this. So in this sprint, we'll estimate only commited vs completed ? | |||
*: (Oleg) yep, Product Performance - is the physical performance of the app, or performance of the SMS team ? ) Sorry missed meaning of that previously, if it's about performance of SMS app (as I thought) then yes, only every 3rd sprint. | |||
*: (Julien) performance of the app :) "Product" performance | |||
*: (Oleg) Ok :) | |||
Commited tasks vs Completed tasks | |||
(Oleg) t=3 (a lot of [not-part-of-the-sprint]) | |||
(Julien) t=3 (only 3 because we did a lot of tasks out of the sprint) | |||
*: (Julien) we take into account what we think we should, as a team :) do you think it makes sense? | |||
*: (Oleg), yeah agree, we need to improve current situation | |||