Timeline for Who decides the length of a sprint?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 1, 2020 at 15:53 | comment | added | Bogdan | @KargWare: if teams work on the same product, it's easier if they choose to have the sprints start and end at the same time. It helps with plannings, communication, coordination, releases, etc. If different teams work on different products, they should choose watever sprint length they see fit, independent of the other teams. There will of course be various things that influence what the sprint length is, as I mentioned already in the answer. | |
| Aug 31, 2020 at 10:55 | comment | added | KargWare | Should be the sprint length, start and end point sync over the whole dev department? Or team by team? I worked often in a synced environment, and so the decision was done by "management" and not by team. All teams were able to discuss it during the retros. | |
| Jul 22, 2020 at 10:34 | vote | accept | nourdine | ||
| Jul 22, 2020 at 10:22 | history | edited | Bogdan | CC BY-SA 4.0 |
added 297 characters in body
|
| Jul 22, 2020 at 10:16 | history | answered | Bogdan | CC BY-SA 4.0 |