Confirmed users
821
edits
| Line 494: | Line 494: | ||
===Grades (5 is very good, 1 is very bad)=== | ===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) | (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 | ====Commited tasks vs Completed tasks==== | ||
(Oleg) t=3 (a lot of [not-part-of-the-sprint]) | * (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) 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 | |||