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

Getting Started with Scrum

Curriculum

  • 2 Sections
  • 10 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • The Basics of Scrum
    4
    • 1.1
      The Bird’s-Eye Basics
      10 mins
    • 1.2
      The Feedback Feast
      10 mins
    • 1.3
      Agile Roots
      10 mins
    • 1.4
      The Five Scrum Values
      10 mins
  • The First Steps
    6
    • 2.1
      Getting Your Scrum On
      10 mins
    • 2.2
      The Power in the Product Owner
      10 mins
    • 2.3
      Why Product Owners Love Scrum
      10 mins
    • 2.4
      The Company Goal and Strategy: Part 1
      10 mins
    • 2.5
      The Scrum Master
      10 mins
    • 2.6
      Common Roles Outside Scrum
      10 mins

The Feedback Feast

Getting Started with Scrum

The Feedback Feast

🕐 12 min read
The Big Question

How does regular feedback in Scrum help teams deliver what customers actually want, faster and more reliably?

Imagine working on a project for months, only to find out at the end that you built the wrong thing. Scrum flips this risk on its head by making feedback a feast—served early, often, and from everyone who matters.

💡 Did You Know?

The term “feedback loop” originally comes from engineering and biology, describing systems that adjust their behavior based on results. In Scrum, it’s your secret ingredient for continuous improvement.

One clear advantage of scrum over other frameworks is the feedback loop, which tells you early and continuously what’s working, what’s not working, what’s missing, and what’s extraordinary.

Feedback is generated regularly from scrum team members, stakeholders, and customers. The process goes something like this:

  1. Developers receive daily feedback as they build their product or service.
  2. Direct daily interaction occurs between the product owner and the developers for on-the-spot answers and feedback.
  3. The product owner provides direct feedback as they accept or reject every completed backlog item.
  4. At the end of each sprint, internal stakeholders provide feedback.
  5. At the end of every release, feedback is provided by the external marketplace.
Feedback Loop

A continuous process where teams receive and respond to input from users, stakeholders, and each other to improve the product incrementally.

Product Owner

The Scrum role responsible for maximizing the value of the product and managing the product backlog, including providing timely feedback to developers.

Think of a time when you received feedback late in a project. How might early feedback have changed the outcome?

You get more from the scrum model than traditional project management models because scrum emphasizes results rather than artifact development, delivering tangible, validated products rather than tomes of reports on what’s possible. You receive regular feedback along the way, enabling you to incrementally get your product or service to market as fast as possible.

Practicing Scrum in the real world often means adapting to constant change—and having the courage to pivot based on what you learn every step of the way.

Want to go deeper? The science behind feedback loops

Feedback loops are rooted in control theory and systems thinking. By continuously inspecting outcomes and adapting behavior, teams can avoid costly mistakes and seize opportunities quickly. In Scrum, this means every sprint and review session is a built-in experiment where learning is immediate and actionable.

How might your team benefit from hearing directly from customers before a project is finished?

❌ Common Misconception

Feedback only happens at the end of a project, when the product is finished and ready for review.

✅ The Reality

In Scrum, feedback is continuous—occurring daily, at the end of every sprint, and from multiple sources, so teams can adapt their work early and often.

⏱ 5 minutes
Activity: Map the Feedback Flow

Visualize how feedback moves through a Scrum team during a sprint.

  1. Draw a diagram showing who gives feedback to whom (developers, product owner, stakeholders, customers) and when.
  2. Label the types of feedback (daily, sprint-end, release) and note the purpose of each.

Tech startups often use Scrum to release “minimum viable products” quickly, get real user feedback, and pivot their offerings in response—sometimes radically changing direction based on what they learn.

What risks can continuous feedback help you avoid on your next project?

In the end, you’re not left wondering whether you produced what your customers want; you’ve been communicating with and receiving feedback from them all along the way.

  • Feedback in Scrum comes from multiple sources and happens continuously.
  • The feedback loop allows teams to adapt quickly and focus on delivering value, not just documentation.
Flashcard

Who is responsible for accepting or rejecting completed backlog items in Scrum?

Tap to reveal
Answer

The Product Owner is responsible for providing direct feedback and deciding whether completed backlog items meet the acceptance criteria.

Flashcard

What is the main advantage of Scrum’s feedback loop?

Tap to reveal
Answer

It enables early and continuous learning about what is working and what isn’t, so teams can adapt quickly and deliver what customers actually want.

Flashcard

When does feedback from the external marketplace typically occur in Scrum?

Tap to reveal
Answer

At the end of every release, the external marketplace provides feedback that helps refine the product further.

Reflect on a project you’ve worked on (or heard about) where continuous feedback could have changed the result. How might Scrum’s approach have made a difference?

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

Scrum’s continuous feedback loop empowers teams to adapt early and often, ensuring products are shaped by real user and stakeholder input—delivering true value, not just documentation.

Key Takeaway

Regular feedback at every stage—from daily work to market releases—reduces risk and dramatically increases the odds of delivering what customers actually need.

In your own words, explain why focusing on results rather than artifacts makes Scrum more adaptable to change.

0 words
SHIFT

The Shift

  • Scrum’s feedback loop enables rapid adaptation and continuous improvement at every stage of development.
  • Regular, multi-source feedback dramatically reduces the risk of building the wrong product.
  • Focusing on tangible results over documentation helps teams deliver true value to customers faster.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

The Bird’s-Eye Basics
Prev
Agile Roots
Next

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

Modal title

Main Content