Build Trust With Scrum
Build Trust With Scrum
You don't need to blindly fall into each other's arms to build trust - just be willing to cooperate and believe in your team.
Join the DZone community and get the full member experience.Join For Free
Are We Really a Team?
Looking back, a couple of years ago I had a chance to work with the great team. Yes! They are a great team, but not from the beginning...that was a broken team when I came on.
- The team used Scrum but the Transparency was lost. The Development Team hid issues from the Product Owner when he came to ask. They said: “All good!", but actually, they had a ton of bugs and impediments and couldn’t deliver working software.
- The Development Team complained that the goal was changed frequently by the Product Owner.
- Disappointment appeared between the Development Team and Product Owner every Sprint Review.
- The higher manager started to doubt the product's quality and progress. Therefore, they put more and more pressure on the team and asked for more reports. This didn’t help to improve the situation but only made it more terrible.
- Every time something went wrong, people started to complain to each other and this led to "fear mode." They started to say "I", not "We."
In a tough time, I planned to do many things to support the team, but first I asked them: "As a Team, do you trust each other?"
Why Trust Is Important
Trust is important because it is the core around which human relationships revolve. Without trust, there will be no relationship. In some relationships like a family, trust exists naturally. Otherwise, some relationships people need to build up over time.
Lack of trust: Relationships will be broken and Transparency is lost. People start to play defense, no one wants to work as a team or collaborate on a goal.
From my experience, nothing is more important for Teamwork than trust. You can't build a good team while they lack trust.
What Should We Do to Build Trust?
I used to say: "If you want someone to trust you, you need to trust them first." Or, we can say, to trust someone, you need to be courageous first!
It's hard, right? What if you give them trust but they give you disappointment? What if they do something wrong? What if we failed?
I believe we have an answer in the Scrum framework. It supports the Scrum team to be courageous:
- Managing the risks in a Sprint.
- Having Daily Scrum to support Development Team reviews and having a plan updated to achieve the Sprint goal at the end of Sprint.
With a time-box, the Scrum Team has a chance to learn, fail, and improve continuously.
"Be courageous! We can fail, but fail quickly and learn."
Therefore, be courageous to do a thing your team has never tried before. To do a thing we do not understand fully because we are in a complex situation. Being courageous supports Scrum values:
- Product Owner needs to trust the Development Team: they will do their best to create a done increment at the end of Sprint.
- The Development Team needs to trust the Product Owner for his/ her vision.
- The Development Team member trusts each other, not only on their strengths but also their weaknesses.
- The higher manager(s) needs to trust the Scrum team and give them a space to be self-organized.
To be honest, as a leader, when communicating, keeping the commitment to the team and transparency with each other is important to build the trust as well.
"As a leader, you need to trust your team first to be trusted.”
How Long Does it Take to Build Trust?
"It will never ever be a one-day job."
As a Scrum Master, one of your daily jobs is building up and maintaining trust among a team, raising up 5 values of Scrum. Your work is not a short term job but step by step. Even that is rebuilding trust or building up a level of trust.
Published at DZone with permission of Khoa Doan Tien , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.