Timeline for How to deal with sprint planning running far too long?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 1, 2018 at 19:30 | vote | accept | kitta | ||
| Aug 26, 2018 at 19:17 | audit | First posts | |||
| Aug 26, 2018 at 19:18 | |||||
| Aug 10, 2018 at 22:26 | comment | added | Thomas Owens♦ | @GregBurghardt Perhaps. But there's a difference between the entire team being in a room for 5 hours and different combinations of people being off doing design work for 3 hours after a 2 hour planning session. | |
| Aug 10, 2018 at 21:00 | comment | added | ruakh | Re: "make sure that the team realizes that they don't need to get every detail right in Sprint Planning": And, more importantly, make sure that it's actually true that they don't need to get every detail right in sprint panning. | |
| Aug 10, 2018 at 20:38 | comment | added | Michael Borgwardt | @GregBurghardt: OP writes that they spend most of the time doing design. So the entire team works on the design of every single story. If you break that up so that only part of the team works on each respective story, you reduce the overall time spent in meetings. | |
| Aug 10, 2018 at 19:54 | comment | added | Greg Burghardt | Basically the team will still spend the same number of hours in meetings. We just call them different meetings. :) It takes what it takes to break things down enough for the team to feel comfortable estimating the work, and to be independent when it comes time to do the work. | |
| Aug 10, 2018 at 15:36 | history | answered | Thomas Owens♦ | CC BY-SA 4.0 |