# Sprint Driven Development

DevFeed: [Sprint Driven Development](<https://devfeed.tech/articles/sprint-driven-development-33417.md>)

Original publisher: [Read original article](<https://timkellogg.me/blog/2022/11/22/sprints>)

Published: 2022-11-22T00:00:00Z

Content type: opinion

Language: en

Sources: [Tim Kellogg](<https://devfeed.tech/sources/tim-kellogg.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [code-reviews](<https://devfeed.tech/tags/code-reviews.md>), [development](<https://devfeed.tech/tags/development.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [team](<https://devfeed.tech/tags/team.md>)

## AI overview

The article argues that Agile sprints should resemble focused, high-intensity efforts directed toward a clear destination rather than arbitrary two-week work divisions. It proposes distinguishing between planning mode, where a team is still determining its direction, and sprint mode, where the team knows what to do and needs time to execute. The author recommends preserving sprint mode while it remains productive, while acknowledging the risks of moving quickly in the wrong direction.

## Source excerpt

Agile talks about doing work in sprints, but it never felt like a "sprint" to me. It just feels like we're chopping work up arbitrarily into 2-week chunks. When I run, sprinting is a top-speed run focused on getting to a clear destination as soon as possible. I need a long rest before I can sprint again. The agile version of this doesn't seem like it has much in common.