Timeline for How long should an Agile Sprint be?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 12, 2016 at 8:51 | comment | added | bobo2000 | @BartoszRakowski too short sprints is NOT a bad thing if done right, since the Scrum team are able to adapt to changes in the project scope quicker. It just means you deliver smaller product increments. Very often if you are building a software product, the PO gets more of an idea what they want next during each sprint cycle, you can then plan your next sprint cycle accordingly. By doing a 3 week sprint, the PO will have to wait 3 weeks until the work is completed at which point some of the work may become redundant or lesser in priority to other pieces of work in the backlog. | |
| Dec 17, 2013 at 19:21 | comment | added | Mark Levison | Bartosz - you made a factual error. The timeboxes for the Scrum ceremonies scale linearly with the length of the Sprint so they should be a now issue. | |
| May 8, 2011 at 23:02 | vote | accept | amelvin | ||
| May 4, 2011 at 6:03 | comment | added | Bartosz Rakowski | Usually a team gets momentum rather by doing more of the technical tasks and removing impediments than by setting sprint length. I would also recomend watching the outcome of the retrospectives - are the impediments/improvements found and are the proper actions taken? | |
| May 3, 2011 at 22:23 | comment | added | amelvin | +1 Not my first sprint - but the longest project I've faced in an agile fashion. I'm concerned that in the early stages when the project shape is still settling down whether longer early sprints may make sense on the work/cost ratio. | |
| May 2, 2011 at 7:05 | history | edited | Bartosz Rakowski | CC BY-SA 3.0 |
grammar
|
| May 2, 2011 at 5:32 | comment | added | Bartosz Rakowski | Not sure if it is not a better idea to start such sprint anyway. Well, I don't have enough information to judge. | |
| May 1, 2011 at 22:30 | comment | added | ashes999 | +1 but disagree about no delays between sprints. Given the size of the project and company, it may be impossible to have the backlog fully prioritized and rearing to go at the start of each sprint. | |
| May 1, 2011 at 11:24 | history | answered | Bartosz Rakowski | CC BY-SA 3.0 |