PremierAgile

Respect in an organization is crucial in growing a high-performance team and solving complex problems. It ensures collaboration and understanding of each team members' strengths and shortcomings. This is the third article in the series of 5 articles on Scrum Values about respect.

Besides the practices, the Scrum Framework is built on five core values. These values play a critical role in the success of Scrum Teams and organizations, especially transforming the mindset from doing Agile to being Agile. The values guide different roles how to think, make decisions, and evolve.

The Scrum Guide mentions five values:

1. Focus

2. Openness

3. Respect

4. Courage

5. Commitment

In this article, we'll discuss the value 'Respect,' and what it means to different Scrum Roles. 

What is Respect in Scrum?

According to the Merriam-Webster dictionary, respect refers to the act of giving particular attention or high or special regard.

In the context of Scrum, it means that Scrum Team members and stakeholders should demonstrate respect to each other    “to everyone“ to the Product Owner, Scrum Master, Developers and stakeholders.

Scrum Teams need to be aware that their strength lies in collaborating with each other. They need everyone's distinct contribution to complete the work of the Sprint. Thus, Scrum Teams need to respect each other's ideas, even team members have a bad day once in a while, and still recognize everyone's accomplishments.

Respect“ what it means to the Product Owner?

The Product Owner is as good as one of the key stakeholders of the product but work together as part of the Scrum Team. They create a product vision, product strategy, product roadmap, Product Backlog, along with presenting a "Done" Increment to the stakeholders.

As the Product Owner is evolving and adapting the Product Backlog, it is the responsibility of the Developers to create the product in "Done" increments. It is possible that the Scrum Master and the Developers might have ideas about the product while they are working on the technical aspects. In such a case, the Product Owner should respect and acknowledge the ideas of the Scrum Master and the Developers as an opportunity for overall product improvement.

The Product Owner also interacts with the stakeholders on a regular basis. And stakeholders may have useful feedback for the Increment. The Product Owner should respect the feedback of the stakeholders and use it to make the product better   “ inspect and adapt during the Sprint Reviews.

In addition, Product Owners should also respect Scrum Master's ideas as they bring innovation, new ideas and practices to improve the overall Scrum.

The Product Owner also respects the users' preferences, market dynamics, healthy competition.

The Product Owner also respects Scrum by living the five Scrum values, following the timebox, sticking to the Sprint Goal and following the other Scrum practices as agreed by the Scrum Team.

Respect“ what it means to the Developers?

The Developers is self-organizing and cross-functional, which means it works as a whole to deliver a "Done" increment. The team should, therefore respect everyone's skills, culture, diverse backgrounds, experience, and ideas.

The Product Owner creates Product Backlog and sets expectations from the Developers in terms of priorities set in the Product Backlog.  The Developers should respect the Product Owner by delivering as per the priorities set.

The Scrum Master is a servant leader and doesn't have any authority. They enable and empower the Developers to make the decisions especially for estimations, solutioning, technical-how etc. The Developers should respect the empowerment and leverage to the best possible extent to provide transparent progress, bring problems to the fore-front, be productive and deliver a high-quality product.

In addition, Developers should also respect Scrum Master's ideas as they bring innovation, new ideas and practices to improve the overall Scrum.

The Developers also respects Scrum by living the five Scrum values, following the timebox, sticking to the Sprint Goal and following the other Scrum practices as agreed by the Scrum Team.

Respect“ what it means to the Scrum Master ?

Great Scrum Master s focus on developing respect within their teams. The Scrum Master should focus on the health of the Scrum Team and ensure the effective use of Scrum.

The Developers creates and owns the Sprint Backlog, and they decide how to do the work and how much they can do in a Sprint. The Scrum Master should respect the Developer's decision about how to convert the Sprint Goal into a "Done" Increment; by trusting their knowledge and skills and helping them to work at a sustainable pace.

The Scrum Master is also responsible for ensuring the efficiency of the Product Owner. However, the Product Owner might not always be able to fulfill what is asked of their role. For instance, they may not know how to prioritize a Product Backlog or break large Product Backlog Items into smaller Product Backlog Items. The Scrum Master should respect the Product Owner by acknowledging what they know and helping with their shortcomings.

The Scrum Master also respects Scrum by following and coaching others to follow the five Scrum values, by following the timebox, respecting the Sprint Goal and following the other Scrum practices as agreed by the Scrum Team.

Respect“ what it means to Scrum Events and Artifacts?

Let's take a look at what respect means to Scrum Events and Artifacts.

1. The entire Scrum Team should attend the Sprint Planning, Sprint Review, and Sprint Retrospective, and follow the timeboxing.

2. While the Daily Scrum is conducted, the Product Owner should not disrupt it thereby respecting the discussions, ideas of the Developers.

3. The Scrum Team crafts a Sprint Goal and adheres to it, except for extreme market dynamics or the Sprint Goal becomes obsolete.

4. The Developers creates the Sprint Backlog which is a forecast for the Sprint, and respects to complete the Sprint Backlog within the Sprint's timebox.

5. Only "Done" Increment should be reviewed in each Sprint Review. This also implies that everyone's time and involvement are respected.

6. The Product Owner should set realistic expectations for the Developers and collaborate with them that sets up for the overall success.

7. Developers works as per the priorities set by the Product Owner in the Product Backlog.

Benefits of Respect in Scrum

Effective feedback

In a respectful environment, team members tend to accept criticism and see it as an opportunity for improvement.

Team navigation

An atmosphere of respect prevents tensions and conflicts between members. This facilitates shifting decisions when working as a team.

Saving resources

When an organization has a culture of respect, the team is more motivated and driven to deliver performance, which yields better time and cost management.

Stakeholders' trust

Creating an environment of respect builds stakeholders' trust and confidence. This will help the Scrum Team achieve much more, thus creating value for the overall organization.

Top performance

When everyone in the team feels appreciated and respected, they are likely to give their best. Top performance is a result of a safe environment where everyone is respected for their cultures, ideas, contributions, skills and treated well. When there's respect, people work with autonomy and trust their skills. This promotes smooth workflow and better-finished products.

Develop great products

Respect in product development leads to great ideas, early feedback within and outside the organizations including early adopters of products and hence great products that creates values for the organizations.

Conclusion

Respect is one of the essential elements of a high-achieving team and a great performing organization. Scrum promotes respect by including all team members in the planning and decision-making process; and by ensuring everyone is heard and valued.