In the last post we looked at the three pillars of Scrum: transparency, inspection, and adaptation. These pillars keep the framework standing, but they need something more to truly work in practice. That something is the Scrum values.
The values give life to the framework, shape the way teams behave, and create the environment where Scrum can succeed. Once we understand the values, we can also look at the people who live them out every day: the Scrum Team.
The Five Scrum Values
Commitment
Team members personally commit to achieving the goals of the Scrum Team. Commitment is not about working late nights. It is about staying focused on the Sprint Goal and holding yourself accountable.
Courage
Scrum requires courage. Teams need the courage to take on difficult work, to speak honestly in Retrospectives, and to address problems openly. Without courage, inspection and adaptation cannot happen.
Focus
During the Sprint, everyone focuses on the work of the Sprint Goal. By limiting what is in progress and avoiding distractions, the team is more likely to deliver something of real value.
Openness
The Scrum Team and its stakeholders agree to be open about the work and the challenges. Openness fuels transparency. If a blocker comes up, it is raised right away rather than hidden.
Respect
Team members respect each other as capable, independent professionals. Respect keeps the team healthy and collaborative, even under pressure.
Together, these values guide how Scrum Teams work, how they make decisions, and how they support one another.
The Scrum Team
Scrum is built around a single team. There are no hierarchies within it, just three defined roles that share accountability for delivering value:
- Product Owner
The Product Owner is responsible for maximizing the value of the product. They manage the Product Backlog, order the work, and make sure the team is always focused on the most valuable outcomes. - Scrum Master
The Scrum Master ensures that Scrum is understood and enacted. They coach, teach, and remove obstacles. As we saw in the first post, they are the guide who keeps the team aligned with Scrum principles. - Developers
Developers are the people in the Scrum Team who do the work of creating a usable Increment each Sprint. “Developers” does not just mean coders. It includes anyone with the skills needed to turn backlog items into value, whether that is design, testing, writing, or coding.
The Scrum Team is small, self-managing, and cross-functional. Everyone collaborates, everyone contributes, and everyone shares responsibility for success.
The values create the culture, and the roles define the structure. Without the values, the roles become mechanical. Without the roles, the values lack focus. When both are present, Scrum Teams can deliver value consistently and sustainably.
Now that you know the values and the roles that make up a Scrum Team, the next step is to see how Scrum actually plays out in practice. In the next post, we will explore the Scrum events that drive the rhythm of the framework.
Comments
No comments yet.