Back to Insights

Agile Delivery: Work in Sprints and Keep Moving

ShareLinkedInEmail

Endurance monsters, combo runners, speedsters, which kind of runner are you? Marathoners live by logging more miles every week. Most runners adjust between long and short distances, which makes them combo runners. Speedsters are a rare breed, the champions of the short game, leaving everyone behind in races of 5K or less.

It is tempting for teams to chase the big end result like a marathoner, but the better strategy is inspired by the speedsters. Focus less on the overall goal and more on shorter bursts, or iterations. That mindset, combined with a refusal to let delays stall the team, is what keeps IT projects moving and improving.

Work in short iterations

Work on a task you can complete in a short window, ideally about two weeks, one iteration at a time. Doing so produces the best result, lets the team learn from its efforts, and allows adjustments between each iteration.

This approach helps a team overcome its intimidation with the project's overall goals. Instead of worrying about how they will ever get there, the team breaks the work into shorter tasks that form a trustworthy roadmap. The shorter the task, the more accurate the estimate of effort, and the more achievable the expected result.

Shorter sprints bring other advantages too:

  • A lower cost of failure. A wrong turn costs two weeks, not two quarters.
  • More immediate data and useful feedback, which improves the next iteration.

A few habits make iterative delivery work:

  • Break projects into shorter iterations rather than chasing the full goal at once.
  • Focus on the current iteration only. Progress is built one task at a time.
  • Use regular communication to keep the team focused on immediate tasks.
  • Involve hands-on stakeholders in the testing, feedback, and planning for the next iteration.

Do not let delays stall the team

In 2005, Amazon Prime was born, offering free two-day shipping for an annual fee. Amazon's success rests partly on understanding consumer psychology, including the fact that waiting frustrates people. Waiting is a challenge for project teams too, especially when delays arise outside the team's control.

When a delay hits, it is natural to want to pause until more information is available. No one wants to make important decisions without it. Yet the team's work cannot grind to a halt.

Resist the temptation to postpone scheduled meetings until all task results are in. As logical as that seems, waiting for complete results can put the team in a difficult position with stakeholders. Timelines slip, tasks go unfinished, and the team can run out of runway if last-minute fixes are needed.

The better alternative is to keep on target despite the delay. Take action on what can be done to complete the current task, and keep the lines of communication open. In times of delay, being open and transparent with everyone about the situation is critical.

  • Remember that deadlines are mostly predictable, even when task performance is affected by factors beyond your control.
  • Meet as a team even when a task misses its objective, so everyone stays informed.
  • Use a delay as an opportunity for a retrospective to understand what happened.
  • Communicate the change and the impact the delay will have on the project.

Momentum is the point

Both habits serve the same goal: keeping the project in motion. Short iterations create momentum by turning an intimidating goal into a series of achievable tasks. Refusing to stall in the face of delay protects that momentum when circumstances work against you. Together they let a team deliver steadily, learn as it goes, and adapt without losing its footing.

To learn more, see our project management methodology.

Ready to explore a partnership?

Let's Connect

We use cookies. View our Privacy Policy