PremierAgile

In Scrum, courage as a value acts as a driving force that shapes every decision, interaction, and moment of collaboration. Courage isn't just needed in crisis; it’s woven into the fabric of the Scrum framework. It allows teams to face challenging situations, make difficult choices, and explore new ideas without fear of failure.

But what does courage look like in action? How does it show up in the daily grind of Scrum roles? Let’s dive in and discover how courage plays a vital role in making Scrum work.

Exploring How The Scrum Team Puts With “Courage” As A Scrum Value:

In Scrum, courage takes many forms. It's about standing up for the right thing even when it’s difficult, speaking up when you disagree, and admitting when you don’t have all the answers. Courage drives teams to engage in honest conversations that lead to real solutions. It’s about confidently facing the unknown and being willing to learn from mistakes.

For the Product Owner: Making Tough Calls

The Product Owner (PO) maximizes the product's value. It sounds straightforward, but it requires a lot of courage. The PO must be courageous enough to make tough decisions and navigate conflicting demands from stakeholders.

For the Developers: Standing Firm on Quality

Developers, too, must summon courage daily. They’re the ones on the ground, turning ideas into reality. They know better than anyone else what it takes to build a quality product. Developers must balance the pressure to deliver fast with the commitment to deliver well. They need the courage to say, "We need more time to get this right," or "This approach isn’t working; we need to try something else."

For the Scrum Master: Upholding the Framework

The Scrum Master is the guardian of the Scrum process, ensuring that everyone understands and embraces the framework. This isn’t always easy, especially in environments where Scrum might be new or misunderstood. Scrum Masters must have the courage to coach and mentor the team through change and uncertainty so that everyone feels safe speaking up and sharing their ideas.

Different Elements of Scrum That Foster Courage

Courage doesn’t just happen; it’s cultivated. Scrum has built-in mechanisms that help foster courage within teams. Let’s explore how:

1. Timeboxed Sprints: Creating Safe Spaces for Experimentation

The time-box nature of Sprints gives teams the freedom to experiment, learn, and fail without fear of massive repercussions. Knowing that a Sprint is a limited period allows teams to try new things, take risks, and make bold decisions. If something doesn’t work, the impact is limited, and there’s an opportunity to adapt in the next Sprint.

2. Sprint Retrospective: A Platform for Honest Reflection

Every Scrum event allows inspecting. However, Sprint Retrospective mainly brings out courage among team members. During retrospectives, the team reflects on their working together, what’s going well, and what could be improved.

• It takes courage to bring up issues about how the team collaborates.
• It takes courage to admit mistakes or suggest new approaches.

Retrospectives provide a safe space where team members can openly discuss challenges and propose changes, building a culture of continuous improvement.

3. Transparency: Building Trust Through Openness

Transparency is a cornerstone of Scrum, and it takes courage to be fully transparent about progress, setbacks, and failures.

• Teams must be open about their planned work and share completed increments with stakeholders, which fosters trust.
• The more trust the team builds, the more courage it finds to remain transparent about the ongoing challenges.

Transparency creates an environment where courage can thrive, allowing teams to confront challenges head-on and grow stronger together.

“Courage” in Everyday Scrum: Real-Life Scenarios

Courage is the fuel that powers Scrum teams forward. It enables them to take risks, face uncertainties, and continually adapt to deliver value. To bring this to life, let’s look at a few real-life scenarios where courage is critical:

• Admitting We Don't Know: During Sprint Planning, a developer acknowledges they don’t know how to implement a requested feature. Instead of pretending to know or pushing through mindlessly, they ask for help, sparking a collaborative solution-finding effort.
• Changing Direction: After reviewing the Increment in a Sprint Review, the team realizes they’ve been building something that isn’t resonating with users. It takes courage to admit this and pivot despite the effort already invested.
• Holding Each Other Accountable: When a team member isn't meeting their commitments, it affects their ability to deliver. It takes courage to have an honest conversation, provide constructive feedback, and ensure everyone is aligned with the team's goals.

So, next time you’re faced with a tough decision or an uncomfortable conversation, remember: in Scrum, courage isn’t optional—it’s essential. It helps a group of individuals achieve remarkable things. So, embrace it, nurture it, and watch your team soar!

Reference:

The Scrum Values and the Real World | Scrum.org