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

Testing in the Feedback Loop

Scrum Product Development

Testing in the Feedback Loop

🕐 12 min read
The Big Question

Why does testing throughout a sprint lead to better products than waiting until the very end?

Imagine steering an aircraft but never checking its position until the flight is over. Would you arrive at your destination? Scrum teams avoid this risk by embedding testing into every sprint, constantly validating their course and making real-time corrections.

In scrum, you test during every sprint, doing component tests, functional tests, and tests for user feedback. Contrast that type of product development with a typical waterfall project, in which testing happens only at the end of a project. Finding errors at the last minute causes either heroic and expensive fixes or pushing out the timeline. Like an aircraft whose path goes uncorrected, a product that is not validated ends up way off course.

💡 Did You Know?

Fixing a bug early in the sprint often takes minutes, but waiting until release can turn a simple fix into a costly, time-consuming ordeal.

The daily priority is informed by the feedback received during testing and customer validation as the sprint progresses. Corrections in the product are usually made the same day, while they’re easiest and least expensive to fix and don’t hold up further progress.

Remember icon
REMEMBER

On a scrum team, everyone is responsible for everything. It isn’t up to one specialized tester to test everything for everyone else. The entire team owns the outcome, and all members care about quality.

Want to go deeper? Why testing early improves quality and speed

Early testing lets teams catch errors when changes are still fresh and localized. Research consistently shows that the sooner a software defect is found, the less effort it takes to fix. This not only keeps the product on track but also prevents small mistakes from snowballing into major setbacks.

⏱ 5 minutes
Activity: Map Your Team’s Testing Actions

Think about your most recent project or sprint. How did your team handle testing?

  1. List the testing tasks your team completed during the sprint.
  2. Identify who participated in each task—was it just testers or everyone?
  3. Reflect: Did early testing help avoid last-minute surprises?
Flashcard

What is the main difference between testing in scrum and waterfall?

Tap to reveal
Answer

Scrum incorporates testing throughout every sprint, while waterfall typically reserves testing until the end of the project.

Flashcard

Who is responsible for testing in a scrum team?

Tap to reveal
Answer

The entire scrum team shares responsibility for testing and quality, not just specialized testers.

Flashcard

Why are errors easier and less expensive to fix during a sprint?

Tap to reveal
Answer

Because changes are still fresh and isolated, making corrections quick and preventing delays in progress.

How would your project outcomes change if your team waited until the end to test?

Many tech companies now run “continuous integration” pipelines, automatically testing every code change within minutes. This practice mirrors scrum’s feedback-driven approach and prevents costly surprises late in development.

Feedback Loop

The ongoing process of testing, gathering feedback, and making corrections during every sprint.

Customer Validation

Engaging users during the sprint to ensure the product meets their needs before release.

Think about a time when an error was caught late in a project. How did it affect the timeline and cost?

❌ Common Misconception

Testing is the job of dedicated testers—developers shouldn’t have to worry about it.

✅ The Reality

In scrum, everyone on the team is responsible for testing and quality. Shared ownership ensures higher standards and fewer surprises.

Experienced scrum teams often pair developers and testers for rapid feedback, catching usability and functional issues before they grow.

  • Scrum testing happens throughout every sprint, not just at the end.
  • Errors caught early are quicker and cheaper to fix.

If everyone on a scrum team owns testing, how does that change the team’s sense of accountability?

Describe how your team handles testing and feedback today. What would change if everyone shared responsibility for quality?

0 words Take your time — depth matters more than length
Key Takeaway

Testing early and often in scrum ensures products stay on track, errors are caught when easiest to fix, and quality is everyone’s job.

Key Takeaway

Shared responsibility for testing creates a culture of quality and accountability within the entire scrum team.

Like an aircraft whose path goes uncorrected, a product that is not validated ends up way off course.

+50 XP

When are product corrections usually made in scrum teams?

Review the section on daily feedback and corrections above to find the answer.
SHIFT

The Shift

  • Testing in scrum happens continuously, enabling real-time corrections and higher product quality.
  • Shared responsibility for testing empowers every team member to own the outcome and improve accountability.
  • Early feedback and validation prevent costly fixes and help teams stay aligned with customer needs.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

In-Flight Course Correction
Prev
Culture of Innovation
Next

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

Modal title

Main Content