Have Scrum Teams Forgotten to be Courageous?

The Sprint Review has started. The customers' feedback is harsh. The Product Owner is about to ask the question most teams avoid.

This is the moment Scrum was built for.

Not the Sprint Planning. Not Backlog Refinement. Not the Retrospective.

This moment. Right here. Asking a real customer what they actually think of the work.

This moment. Right here. Asking a real customer what they actually think of the work.

Last week, the team finished a discovery sprint packed with energy. Ideas were flowing. The prototypes felt strong. The team walked into the customer session genuinely excited about what had been built.

And the feedback was not what anyone expected.

Some ideas landed. Others missed entirely. The customer was figuring out what they needed in real time, right alongside the team. The conversations were rich, honest, and uncomfortable in the best possible way. The team walked out feeling a little beat up.

That feeling has a name.

Courage.

Scrum lists five values: commitment, focus, openness, respect, and courage. Commitment gets talked about. Focus gets tracked in sprint reviews. Openness sounds good in retrospectives. But courage is what actually determines whether a team learns anything real.

Courage is what it takes to show unfinished work to a real customer and ask honestly what they think.

Courage is what it takes to be transparent about progress when progress is slower than expected.

Courage is what it takes to sit in a feedback session and resist the urge to defend the work instead of listening to it.

Without courage, a team gets comfortable. Comfortable teams stop seeking feedback. They start assuming. They tell the customer what they want to hear. They protect the backlog from inconvenient truths.

And the product slowly drifts further from what the customer actually needs.

The team that walked out of that session feeling beat up. But the next morning, they felt grateful. Not because the feedback was easy. Because the feedback was honest. Because that honesty will make the product better and the customer relationship stronger than any amount of positive validation ever could.

That is the promise Scrum made when it instilled courage as a value.

Not courage as a concept. Courage as a weekly practice.

---

The Sprint Review exists so teams can show real work to real people and hear real reactions. The Daily Scrum exists so problems surface before they compound. The Retrospective exists so the team can be honest with each other about what is and is not working.

Every single event in Scrum requires courage.

Skipping the hard feedback is easy. Shipping without validation is easy. Staying inside internal meetings all week is easy.

Scrum was never designed to be easy.

It was designed to be honest.

Feedback only makes a product better when the team has the courage to ask for it honestly.