When we work together, we share successes and failures. This allows us to support ourselves and develop in such a way that we deserve mutual respect. It is worth remembering that only a relationship built on respect gives people the opportunity to fulfill and develop. In such an atmosphere it is possible to realize the remaining values of Scrum: courage, commitment, concentration and openness.
When we think of respect as one of the values in Scrum, our thoughts naturally focus on the respect that Team members have for each other.
This is expressed in the fact that we respect the other person’s opinion, even if it is completely different from ours. We listen to arguments and critically evaluate our assumptions, allowing ourselves to be mistaken.
We understand that people have different experiences, approaches to life, and characters. We believe, however, that they give the team their full commitment and we support them in this to the best of our ability.
We respect our time by appearing at scrum ceremonies. We try to be punctual and prepared. We understand their purpose and with our attitude we try to serve them best.
Scrum Master is responsible for building and developing such attitudes in the Team. His behavior, the way he speaks and the way he treats his role shapes the environment in which the team will develop. It is Scrum Master who is the first person who should notice negative attitudes and try to influence their change. It can be a simple delay to a standup, due to lack of involvement in work, conflicts or real arguments in the team, which have nothing to do with the atmosphere of respect.
Respect in Scrum, however, should not be limited to the relationship existing in the programming team. The team works in a close relationship with the Product Owner. This, in turn, represents Business. Extending the concept of respect in Scrum, beyond the atmosphere in the Development Team, allows you to see an additional field to develop this value.
The Product Owner expresses his respect for the Team by giving them ownership of the Backlog Sprint. Trusting that the Team knows best how much work can be done in a given Iteration and how to do it.
On the other hand, the team is fully committed to the tasks entrusted to it and respects the Product Owner and the Stakeholders who know they can rely on the Team. Importantly, the Team should also communicate openly with delivered and non-delivered functionalities. Also, making realistic commitments to the Customer is an expression of respect.
Respect in relations between people is a long-lasting process. It is certainly a process that requires support at every stage of the team’s life and, more broadly, the Product. An extremely difficult test of the maturity of relations is the moment when the Customer changes his or her mind or is mistaken, and also when… the Team makes a mistake. In Scrum it is a natural situation and if it happens in an open and well-intentioned environment, it should be accepted and understood. It is worth remembering and striving for such a state.
THE CYCLE: SCRUM VALUES