https://www.robg3d.com/2014/09/two-weeks-is-the-worst-sprint-length/ Blog of Rob Galanakis (@robgalanakis) Mon, 15 Sep 2014 19:36:37 +0000 hourly 1 https://wordpress.org/?v=5.4.1 https://www.robg3d.com/2014/09/two-weeks-is-the-worst-sprint-length/#comment-232918 Mon, 15 Sep 2014 19:36:37 +0000 http://www.robg3d.com/?p=1676#comment-232918 There are two notions of “agile” these days – project management approach, and programming style. Both are almost two different worlds. As management approach, agile is more an excuse than something that leads to results, really. It hardly makes sense, from programming point of view, to not start working a new item on a second thursday evening, because sprint ends in two days, or plan your success two weeks in advance on hourly basis – you’ll always overestimate to be safe. Probably a lot of developers could make a list of funny decisions project took on just because project tunnel-visioned into scrum practices.
I’m more of an advocate of “trust your developers” approach. Rely on fast iterations (by iterations I mean merging finished functionality into head and handing over to QA pipeline, not sprints, of any length), rapid deployments, TDD practices – the thing that truely makes development agile, ready to ship at any time. You don’t need sprint plannings here, or sprints. You’re still free to present customer all your new stuff every second friday, if they like such schedule. But you’re open to do it on wednesday, if you so choose.

]]>