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

In-Flight Course Correction

Scrum Product Development

In-Flight Course Correction

🕐 12 min read
The Big Question

How can teams use real-time feedback to adapt their plans and stay on course for success?

Imagine steering an aircraft at 400 miles per hour: every shift in wind, every unexpected event, and every data point must be analyzed and acted upon — instantly. Agile teams face a similar challenge, adapting their trajectories in fast-moving environments to achieve their goals.

A flight crew meticulously plans every mission, estimating fuel, flight time, and execution details based on known and expected parameters. On mission day, they gather updated weather reports and mission changes, preparing to respond to the unexpected.

💡 Did You Know?

Commercial flight crews receive live weather and flight data updates every few minutes, requiring constant course corrections.

Once the aircraft is airborne, crew members continuously evaluate actual speeds and headings, comparing the plane’s position with the original flight plan. At every measurement, they ask: “Are we deviating from the plan? Why?” They investigate causes such as unexpected wind directions or discrepancies between planned and actual headings and speed. Using this new information, they adjust the flight plan to stay on course — repeating this inspect-and-adapt process throughout the mission.

Schematic illustration of flight path.
Figure 7-3: Flight path — comparing the planned route and actual measured position in flight.
Inspect-and-Adapt

A continuous process of evaluating current progress, learning from new data, and adjusting plans to achieve objectives.

Empirical Process Control

An approach that relies on observation, measurement, and adaptation rather than fixed predictions, central to Scrum and agile methods.

Agile teams, like flight crews, use frequent check-ins (such as daily stand-ups and sprint reviews) to assess their direction and make course corrections based on the latest data.

Scrum’s sprint cycles are designed for regular inspection and adaptation, making them ideal times to welcome new information and improve plans.

What parallels can you draw between the way flight crews correct their course and how agile teams adapt their plans?

Want to go deeper? The science behind adaptation in agile teams

Empirical process control is rooted in the idea that complex, rapidly changing environments cannot be managed by rigid plans alone. By consistently collecting and analyzing data, teams can identify trends, detect deviations, and respond effectively. This cycle — inspect, adapt, repeat — is what enables both flight crews and agile teams to achieve their mission objectives, even when faced with uncertainty.

In Scrum, sprints provide structured opportunities to reevaluate and improve plans. New information is not feared but welcomed and applied in a transparent organization committed to product success.

The flight crew repeats this inspect-and-adapt process over and over to ensure a mission’s success.

  • Flight crews and agile teams both rely on real-time information to correct course.
  • Inspect-and-adapt is essential for achieving objectives in dynamic environments.

How does the idea of “welcoming new information” challenge traditional approaches to planning and control?

❌ Common Misconception

Producing detailed status reports is necessary for maintaining control over a project.

✅ The Reality

Agile organizations minimize redundant reporting, focusing instead on transparent communication and direct adaptation using real-time data.

Warning
WARNING

Avoiding the costly overhead of redundant or bureaucratic parallel processes is important. We’ve worked with well-intentioned organizations that expend more effort in measuring status and producing status slides than they expend building products, hoping to maintain control or avoid uncertainty. Creating status reports is an unnecessary parallel activity. An organization that has transformed to being agile and has fully adopted scrum lets go of these artifacts and embraces the new way.

⏱ 5 minutes
Activity: Simulated Course Correction

Apply the inspect-and-adapt mindset in a simulated scenario.

  1. Imagine your team has just completed a sprint, but customer feedback reveals unexpected needs.
  2. List three data points you would collect to understand the deviation from your plan.
  3. Describe how you would adjust your next sprint plan to address these findings.

Have you ever seen a project lose momentum due to excessive reporting? What could have been done differently?

Describe a time when you or your team adapted plans based on new information. What was the outcome, and what did you learn from the process?

0 words Take your time — depth matters more than length
+50 XP

What is the primary reason agile organizations avoid redundant status reporting?

Review the “Avoiding Reporting Overhead” section above to find the answer.
Key Takeaway

Constant inspection and adaptation, based on real-time data, is essential for agile teams to achieve their objectives and maintain momentum.

Key Takeaway

Agile organizations thrive by welcoming new information, minimizing unnecessary processes, and focusing on transparent, direct communication.

SHIFT

The Shift

  • Adapting plans based on empirical data ensures teams stay aligned with objectives and respond effectively to change.
  • Minimizing redundant reporting frees resources for productive work and real-time adaptation.
  • Sprints in Scrum provide regular opportunities to inspect progress, welcome new information, and improve plans.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

External Forces
Prev
Testing in the Feedback Loop
Next

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

Modal title

Main Content