Timeline for Should agile sprints/iterations be back-to-back?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 2, 2018 at 13:39 | answer | added | Dan Ray | timeline score: 0 | |
| Oct 25, 2018 at 15:09 | answer | added | WPrecht | timeline score: 0 | |
| Oct 23, 2018 at 23:18 | answer | added | Bryan Oakley | timeline score: 0 | |
| Oct 23, 2018 at 23:10 | answer | added | RandomUs1r | timeline score: 0 | |
| Oct 23, 2018 at 17:48 | comment | added | user1431072 | And to my previous comment -- i think this is precisely what is wrong with the common idea of a "sprint" today -- that it's just a timebox of sorts. If we think about it like that, then yeah, sure, everything including tech debt just falls into a "sprint". It just doesn't make sense. I could see you doing a few back-to-back sprints to build a product. But once the core product is done, and you're doing maintenance, paying down tech-debt, etc, its a whole different ballpark.. Just my opinion | |
| Oct 23, 2018 at 17:42 | comment | added | user1431072 | @JacobRaihle I disagree with you. Somebody came up with the term and had a purpose for it. A time box? Indeed. But maybe they coined it a sprint because that's exactly what it was, a small box of time meant for the team to sprint to the "sprint" goal, which should be some deliverable. Although I'm not the source of truth, i tend to disagree that it was termed a "sprint" just for it to mean a time box. When my teams work in a sprint, we go hard. We do everything we can to meet the sprint goal. At the end of one, we are often gassed. But we always deliver. | |
| Oct 23, 2018 at 16:31 | comment | added | Frax | I guess it's better to think about that as a "race short enough that the whole track and the finish are visible from the very start and at all times" (as opposed to a long race with possible hard-to-foresee obstacles). This "race at top speed" connotation seems actually pretty harmful here. | |
| Oct 23, 2018 at 15:27 | comment | added | Jacob is on Codidact | The word "sprint" in scrum is not intended in the sense of a "short race at top speed". It is simply the term used to refer to a timebox of work. | |
| Oct 23, 2018 at 14:34 | answer | added | jonathangersam | timeline score: 10 | |
| Oct 23, 2018 at 14:30 | answer | added | mmathis | timeline score: 4 | |
| Oct 23, 2018 at 14:12 | comment | added | Jon Raynor | Yes, sprints/iterations needs to be back to back, but your team and management should consider the length of the project and build in some less stressful times. Sometimes these are called discovery sprints. This helps the team from not getting burned out. Make sure everyone understands the entirety of the project is not a sprint but a marathon. | |
| Oct 23, 2018 at 13:54 | history | asked | user1431072 | CC BY-SA 4.0 |