UNITED WAY STL ACADEMY
  • Courses
  • Log In
  • Join Free
  • Home
  • Courses
  • Scrum Essentials

Scrum Product Development

Curriculum

  • 5 Sections
  • 25 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Planning Your Work
    4
    • 1.1
      The Product Roadmap
      10 mins
    • 1.2
      Breaking Down Requirements
      10 mins
    • 1.3
      Your Product Backlog
      10 mins
    • 1.4
      Product Backlog Common Practices
      10 mins
  • The Talent and the Timing
    4
    • 2.1
      The Developers
      10 mins
    • 2.2
      Getting the Edge on Backlog Estimation
      10 mins
    • 2.3
      Your Definition of Done
      10 mins
    • 2.4
      Common Practices for Estimating
      10 mins
  • Release and Sprint Planning
    5
    • 3.1
      Lean Startup
      10 mins
    • 3.2
      Release Plan Basics
      10 mins
    • 3.3
      Sprinting to Your Goals
      10 mins
    • 3.4
      Planning Your Sprints
      10 mins
    • 3.5
      Your Sprint Backlog
      10 mins
  • Getting the Most Out of Sprints
    4
    • 4.1
      The Daily Scrum
      10 mins
    • 4.2
      Team Task Board
      10 mins
    • 4.3
      The Sprint Review
      10 mins
    • 4.4
      The Sprint Retrospective
      10 mins
  • Inspect and Adapt: How to Correct Your Course
    8
    • 5.1
      Need for Certainty
      10 mins
    • 5.2
      The Feedback Loop
      10 mins
    • 5.3
      Transparency
      10 mins
    • 5.4
      Antipatterns
      10 mins
    • 5.5
      External Forces
      10 mins
    • 5.6
      In-Flight Course Correction
      10 mins
    • 5.7
      Testing in the Feedback Loop
      10 mins
    • 5.8
      Culture of Innovation
      10 mins

Sprinting to Your Goals

Scrum Product Development

Sprinting to Your Goals

🕐 12 min read
The Big Question

How can structuring work into consistent, iterative sprints lead to more effective, adaptable teams—and what hidden pitfalls arise when sprint timing or goals are disrupted?

Finally, the heart of scrum! Sprints and their built-in inspect and adapt model are integral scrum features. Through scrum’s iterative cycle, you can achieve the three pillars of empiricism — transparency, inspection, and adaptation.

Empiricism

A process of making decisions based on observed evidence, emphasizing transparency, inspection, and adaptation.

By breaking your work into tangible pieces and then using the empirical scrum model to assess your progress, you can pivot constantly while moving forward. This allows you the nimbleness and ease of adaptation sorely missing in waterfall. Each scrum team member has the same purpose in the sprints: maximizing effectiveness in delivering desired outcomes.

💡 Did You Know?

The regular rhythm of sprints helps teams forecast future delivery using data like velocity—making continuous improvement a data-driven habit, not a hope.

Defining Sprints

Sprints are the essence of scrum. They’re a consistent timebox for product development by the developers. Each sprint includes the following:

  • Sprint planning
  • Daily scrums
  • Development time, including regular review by the product owner
  • Sprint review
  • Sprint retrospective

The consistent timebox of sprints allows the developers to establish a development rhythm. It also enables scrum teams to extrapolate into the future based on empirical data such as velocity. As soon as one sprint is finished, another begins. A consistent iterative feedback loop flow is created, resulting in an ideal production environment and continuous improvement.

Tip icon
TIP

Imagine that you’re a runner. You’re consistently training for the 100-yard dash and have become incredibly proficient at it, but suddenly your coach asks you to run a marathon. If you attempt the marathon at your 100-yard-dash pace, you won’t finish the marathon. You need to modify your training to adjust for a marathon pace, which will require coaching, schedule, and diet changes over time. All your muscle memory and the type of endurance your body has developed will need to be relearned to run a different race length.

How does the sprint structure create a rhythm for your team, and why might this rhythm be so crucial for continuous improvement?

Planning Sprint Length

Because sprint goals don’t change during a sprint, the answer to the question “How long should a sprint be?” depends on your product and how long your organization can go without making changes. That is the outer edge. You have no reason to discuss going beyond that in duration. For example, if your organization struggles to go a week without needing changes, don’t even entertain the idea of a two-week sprint. You won’t be able to maintain the integrity of the stability of the sprint, and stability is a huge driver of performance in scrum. Instead, discuss how much shorter you can make the sprint.

Remember icon
REMEMBER

According to The Scrum Guide (2020 version), sprints are “fixed length events of one month or less to create consistency.”

What factors should your team consider when deciding the length of a sprint?

Also, sprint lengths don’t change after they begin and ideally don’t change throughout development unless they’re being made shorter. If a scrum team changes sprint length, it comes at a significant cost: Their earlier velocity is no longer relevant. Performance is not a straight mathematical line that can be sliced, diced, and reassembled. Just because a scrum team splits their sprint from one to two weeks doesn’t mean they will automatically accomplish half their historical two-week velocity.

Shorter sprints decrease the amount of time between feedback received from stakeholders, enabling scrum teams to inspect and adapt earlier and more often:

  • With one-month sprints, you have 12 opportunities to inspect and adapt per year.
  • With two-week sprints, you have 26 opportunities per year.
  • With one-week sprints, you have 52 opportunities per year.

Longer sprints have a diminishing return because less of a sense of urgency exists due to the multiple days still available to the team. Weekends and longer sprint meetings can also have a negative effect on efficiency.

The capacity of developers during a one-week sprint may be higher or lower than half the historical two-week velocity. You don’t have any idea until you run a few sprints, and you don’t know for sure until you run a lot of sprints.

Warning icon
WARNING

While the cost of changing sprint lengths throughout development is significant, the cost of changing a sprint goal during a sprint is worse. If a sprint goal becomes irrelevant (for example, changes in company direction or changes in the market) before the end of a sprint, a product owner may decide to cancel the sprint and plan a new sprint to reflect the right priority. But be aware that canceling wastes valuable time and is quite traumatic for the scrum team and the organization. Also, the shorter the feedback loop (that is, the length of the sprint), the less likely a product owner would be to cancel a sprint.

❌ Common Misconception

Changing sprint length or goals during a sprint is a simple way to adapt quickly to new requirements or organizational shifts.

✅ The Reality

Changing sprint length or goals disrupts team stability and undermines metrics like velocity, making adaptation less effective and more costly in the long run.

Sprint Goal

A clear objective for what the sprint will achieve, which remains stable throughout the sprint.

  • Sprints provide a stable rhythm for inspection and adaptation.
  • Changing sprint length or goals mid-sprint disrupts team effectiveness and reliable measurement.

Companies that shorten their sprint cycles often find they can detect issues and pivot faster—sometimes doubling their opportunities for feedback in a year without increasing the stress on teams.

Technical Stuff icon
TECHNICAL STUFF

One thing we know from science is that you can’t turn off your mind. It’s always working. If you can give your developers a small number of problems to solve and tell them that they’ll face those problems tomorrow, they’ll think about them consciously at work. Whether they want to or not, they’ll also think about them unconsciously when they’re away from work. This is the reason why the stability of sprints is so important. After a sprint starts, the developers must have confidence that the scope is stable so that their minds can be fully focused on what needs to be done for this sprint, whether they’re at work or away from it. Have you ever had an epiphany while brushing your teeth? That’s the dynamic we’re talking about here. But you need two elements: a limited number of problems and confidence that you’ll face those problems tomorrow. If a developer works on Product A, Product C, and Product Who-Knows-What every day, this won’t happen.

Want to go deeper? The science behind stable sprints and cognitive focus

Neurological studies show that when people are able to focus on a limited set of well-defined problems, their subconscious continues working on solutions even while they’re away from their desks. This effect, called “incubation,” is why maintaining consistent sprints—and not shifting priorities mid-sprint—yields better problem-solving and innovation over time.

⏱ 5 minutes
Activity: Mapping the Sprint Rhythm

Visualize how your current team rhythm aligns with scrum sprint cycles.

  1. List the current meetings and feedback loops your team uses in a typical development cycle.
  2. Map them onto a sample sprint timeline (e.g., 2 weeks).
  3. Identify one area where adding or shortening a feedback loop could help your team adapt faster.

Reflect on a time when a change in priorities or timing disrupted your momentum—what could have been done differently using scrum’s sprint structure?

0 words Take your time — depth matters more than length

How can you help your team avoid the pitfalls of changing sprint goals or lengths mid-development?

CUMULATIVE FLOW DIAGRAMS

Cumulative flow diagrams (CFDs) provide scrum teams visibility into the patterns of their output and help them identify possible bottlenecks in their processes.

A burnup chart, shown on the left side of the figure, is a type of CFD that shows the number of requirements the team completed within a set duration of time. CFDs, shown on the right side of the figure, give a snapshot of how much work is in any given stage of the process, exposing indicators such as lead, cycle, work, and wait times and identifying points of inefficiency.

Schematic illustration of a sprint backlog is a key scrum artifact.
Cumulative flow diagrams help visualize progress and bottlenecks in the scrum process.

Changing sprint lengths during development makes performance indicators inconsistent over time. In addition to the loss of relevancy of the historical velocity with changing sprint lengths, CFD indicators such as lead, cycle, work, and wait times also become irrelevant.

Key Takeaway

Stable, fixed-length sprints create predictability and focus, enabling teams to inspect, adapt, and continuously improve based on reliable data.

“As soon as one sprint is finished, another begins. A consistent iterative feedback loop flow is created, resulting in an ideal production environment and continuous improvement.”

+50 XP

According to scrum best practices, what is the recommended maximum length for a sprint?

Review the “Planning sprint length” section above to find the answer.
Flashcard

What is the main reason to avoid changing sprint lengths during development?

Tap to reveal
Answer

Changing sprint lengths makes historical velocity and performance metrics irrelevant, disrupting predictability and team rhythm.

Flashcard

What is a Cumulative Flow Diagram (CFD) used for in scrum?

Tap to reveal
Answer

CFDs provide visibility into workflow patterns, showing how much work is in each stage and identifying bottlenecks and inefficiencies.

Flashcard

Why does stability in sprint scope matter for developer focus?

Tap to reveal
Answer

Stability ensures developers can focus on a limited number of problems, both consciously and unconsciously, without distractions from shifting priorities.

Describe how you would explain the importance of a stable, fixed-length sprint to someone new to scrum.

0 words
Key Takeaway

Shorter sprints enable more frequent feedback and adaptation, while stable sprint goals and lengths safeguard team focus and performance metrics.

Practitioners recommend experimenting with shorter sprints in fast-changing environments, but only after running several cycles to establish a baseline for team velocity and performance.

SHIFT

The Shift

  • Consistent, fixed-length sprints drive transparency, inspection, and adaptation, enabling continuous improvement.
  • Changing sprint length or goals mid-sprint undermines team stability and reliable performance measurement.
  • Short feedback loops and stable priorities give teams the focus—and the freedom—to innovate effectively.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

Release Plan Basics
Prev
Planning Your Sprints
Next

© 2026 United Way STL Academy | Powered by Sejal Learning Systems.

Modal title

Main Content