Timeline for Dynamic length of sprints in Scrum
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 2, 2013 at 7:36 | comment | added | unairoldan | one of the principles of Scrum is to have a potentially shippable product at the end of every Sprint. For me, it is the base of the dynamic length; maybe you can not create a shippable product at the end of every Sprint with the fix lenght (you do not have enought time...) | |
| May 1, 2013 at 22:18 | comment | added | Todd A. Jacobs♦ | @Ztere0 The Product Backlog may contain a mix of stories, epics, and themes, but it is the job of the Product Owner to work with the team during Backlog Grooming to decompose items so that they can fit within a fixed-length sprint. Your problems seem to be that you are confusing release schedules with iterations, and allowing your customer to drive your internal development process. Trying to precisely align releases (as opposed to releasable increments) with iterations is not usually constructive. YMMV. | |
| May 1, 2013 at 15:06 | comment | added | unairoldan | so...If the modules or user history are made in Product Backlog => not Scrum? | |
| May 1, 2013 at 13:14 | comment | added | Todd A. Jacobs♦ | @Ztere0 The fact that you're fitting sprints to "modules" defined outside the team means the Scrum Team isn't doing the estimation, planning, or grouping of stories on the Product Backlog. This is not Scrum. Q.E.D. | |
| May 1, 2013 at 8:51 | comment | added | unairoldan | The decision of use fixed length is derived from the necessity of finish "full functionalities" in every Sprint, to deliverable the package to the client (is his petition, only full modules). At this point, we have to decide between N fixed length sprints or "more sense" Sprint length that fit with our modules. Right now the "best reason" to use fixed length is the importance of agile cadence, but I do not see anymore | |
| Apr 30, 2013 at 22:50 | history | answered | Todd A. Jacobs♦ | CC BY-SA 3.0 |