Agile Development: No Sprint Is An Island!

agile development no sprint is an islandOne of the key agile principles is about fixing timescales and varying scope.

In DSDM (Dynamic Systems Development Methodology) these iterations are called Timeboxes; in Scrum agile management practice they are called Sprints.

For Business-As-Usual (BAU) changes to existing products, one Sprint may equal a release of the product. However for projects it’s more than likely multiple Sprints will be required before the features have enough value to the user to be worth releasing.

In the case of projects, it’s clear there must be some kind of release planning sitting over the individual Sprints. This is important to estimate how many Sprints are likely to be required before the product will be ready to be released.

Having done this release planning and worked out how many Sprints should be needed, probably doing some fairly high level estimating at the outset in order to secure project funding, individual Sprints cannot be run in isolation.

The danger if they are, is that any overhang – or personally I prefer to call it hangover 🙂 accumulates and creates a bow-wave effect towards the end of the project, and on some projects it’s more like a tsunami!

Whilst the scope may be varied, and in agile development the scope should be varied, there does of course come a point when you simply can’t vary scope any further without seriously undermining the basis of the original business case. And unfortunately it’s at that point you’re back to the good old-fashioned slippage, that is all-too-common and all-too-painful in so many software development projects using whatever methodology.

So how about BAU? Surely you can run individual Sprints in BAU, each leading to a release of the product? Yes, technically you can. But I say you shouldn’t.

Just to clarify – yes, of course you can run individual Sprints each leading to a release of the product. But ideally you shouldn’t run a sequence of Sprints in complete isolation, even in the BAU scenario.

The product owner, together with the product team and those responsible for the commercial results of the product, should ideally form an outline plan of sorts; a high level roadmap if you will. This is important as the basis for business planning, budgets, revenue forecasts, etc. And even if the planning is fairly unscientific at this level, there must be a clear business vision of the key drivers for the product over time, and this vision needs to inform the priorities of the Sprints.


See also:
10 Key Principles of Agile Development
Time waits for no man!
How can I be sure my project will deliver on time?

Share on facebook
Share on twitter
Share on linkedin

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Posts

Six Actionable Nuggets of Advice for Becoming a First-time Technology NED

If the pandemic has taught companies anything it’s that tech is not something that you put off and think about ‘later’. The last year has seen organisations go through huge digital transformations, whether planned or otherwise. And for those that aren’t technology-based companies, getting the right board-level advice can not only be hard to find, but the difference between success

Read More »

Culture, Skills, and Capabilities // How to become a more data-driven organisation

In our whitepaper “How to become a more data-driven organisation”, we wrote about the five steps that an organisation would need to take, which are: Outcomes: Defining goals and metrics to ensure clear and measurable outcomes Analytics: Implementing and sharing the analytics to improve data-driven decision making Innovation: Testing assumptions through hypothesis testing and learning Data Platform: Gaining new insights

Read More »

Data Platform // How to become a more data-driven organisation

This is the fourth article in our series on “How to become a more data-driven organisation”, and we are going to be focusing on Data Platforms. It is at this point that most people start to dive deep into the technical aspects of Data Lakes vs Data Warehouses, but we want to bring us back up a level and ask

Read More »

Search the Blog

Agile Management Made Easy!

All About Agile

By Kelly Waters

“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. is one of the most popular blogs about agile on the web. ”

Kelly Waters

Agile 101 is available to purchase. GAME ON!

Agile 101

Emma Hopkinson-Spark

“Whilst there are lots of ways you can vary the game depending on the teams you have and the learning outcomes you want, the basic flow of the game play is common to all.”
Emma Hopkinson-Spark

Why did we make the game?

How to play the game?


101 Ways Limited
145 City Rd
United Kingdom


101 Ways BV
Weesperstraat 61-105
1018 VN Amsterdam

Contact Us

If you would like to get in touch with one of the team at 101 Ways, then please fill out the form below or email us at