Trust in the Team

Table of Contents

The Importance of Trust in Agile Methodologies

One of the main values of agile methodologies is trust. However, it is not always clear what this means.

Here are some key insights from my notes on this topic:

  • It is easy to manage inexperienced people (command-and-control works here) because we can persuade them about our view of the world.
  • Experienced employees have their own experiences and are not easily convinced by what we say.
  • To collaborate effectively with people, regardless of their experience, trust is needed. Trust paves the way for asking open questions and ultimately seeking better ways to operate than the current ones.

What is Trust? (Examples of basic principles):

  • Assume 100% positive intent: We assume positive intent behind people’s behaviors.
  • Questions serve as a means to find solutions: We believe that all questions asked are meant to find solutions (not to assign blame). Questions are an expression of care. We trust in the interlocutor’s intention, even if the person asks tough questions.
  • Always answer questions honestly: Even when the answer might seem difficult, we assume that we always answer questions honestly.

What Hinders Open and Trustful Conversations?

The main obstacle to open and trusting conversation is the assumption that you “know” how the discussed topic should be done (what framework, pattern, class, method set, how it should look). Instead of listening and discussing, you strive to prove the sole correctness of your solution. You might win this battle, but you will lose the entire war. Trust will be strained or destroyed.

If there’s a hierarchy or dependency between you, the matter worsens. If you are a manager, listen to what your subordinate has to say. Then, by asking questions, verify whether their concept is correct. It might be better than yours. Or it might not. Good questions will verify this well.

Why Do We Need Trust?

Can’t we do without it? Without trust, it becomes natural to protect your interests (covering your back, job security, or playing various project games). These activities lead to undesirable side effects (loss of time and credibility).

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Related Posts

JUG Łódź

JUG Łódź

Things moved very quickly. The first announcement was made on jdn.pl, followed by a discussion list on http://groups.google.com/group/lodz-jug?hl=pl. The incredible response from Java fans in Łódź, as well as at Javarsovia, led to the first meeting of people interested in developing the JUG in Łódź, which took place on Saturday, June 7, 2008, at 4:00 PM. I commend everyone for this effort. I am hopeful and confident that this initiative will grow into a dynamic and cooperative group of individuals.

Read More

The Big Lie About Clean Code and Unit Testing

Introduction

Many people are convinced that waking up early, say at 5:00 AM, is an unrealistic fantasy for them. They believe that their nature and their body are constructed in such a way that it’s impossible. I used to belong to this group of people.

Read More

Technical Leader Worries: My Organization Is a Mess, and Nobody Cares

Technical Leader Worries: My Organization Is a Mess, and Nobody Cares

Some time ago, I coined a funny equation like this:

Read More