As a leader, at all levels, you are concerned with establishing an effective, productive team culture. Effective, productive team cultures provide boundaries for team members. These boundaries define attitudes and behaviors that work to establish trust and psychological safety within the team. Working agreements, also known as team norms, are an important foundation for teams to establish their expectations of behavior for the group so that trust can flourish.
Every team has working agreements, whether implicit or explicit. As a leader of a self-organizing Agile team, you have an important role in supporting your team in developing effective working agreements that lead to productive, respective behavioral norms, then continue to repeat these often until it becomes embedded into the teams “DNA”. What is your role as a leader in establishing those agreements? What makes working agreements effective? How many should we have? What are some ways to facilitate this discussion?
What are working agreements?
According to of Jane Haskell of the University of Maine, working agreements are guidelines that define how groups want to work together; what they want in the working environment, and what they want from each other to feel safe and free to learn, explore and discover.
Working agreements help establish team culture and norms by defining expected behavior of team members. They establish a common language, enhance performance and provide structure for team collaboration.
Why are they important?
Team working agreements provide a foundation for the team to develop a shared sense of responsibility for their work. In many ways, it is this feeling of shared responsibility that creates the environment for respect, trust and safety to grow. Good working agreements encourage positive behaviors; and allow the team to self-organize around them.
Characteristics of effective working agreements
For teams that last longer than a meeting or two, it is important that working agreements are created by the group themselves and not dictated to them. As a leader you are not there to define the conditions for them. You are there to facilitate; to provide a safe space or meeting environment for the team to define their own working agreements. To do this, you’ll need to have a facilitative process outlined for yourself that will help the group discuss and come to consensus on their working agreements.
Agreements need to be simple, direct, and actionable. They need to be easily recognized and enforceable. Complex agreements are difficult to remember and therefore will be difficult to follow in the moment. Simple agreements focus on positive behaviors that are definable. The old chestnut "don't be a dick" is funny (and true) but is difficult to define in a way that everyone immediately recognizes. That makes it effectively unenforceable. Much better is an agreement to "treat each other with respect" and a discussion of what that may mean to the team.
It is better to limit the number of working agreements. If there are too many working agreements, they are difficult to remember, which renders the entire list worthless. Science has found that our short term memory is limited to between 4 - 7 items. Start with fewer items, the ones the team feels are really important; and then add agreements when needed as the team evolves their process together. Keep it short and simple. Something that you can introduce a new team member to in a minute or so.
Keep working agreements posted in a visible place - a poster on a wall, or on a digital white board where the team is working for example. Be prepared to re-post often, so that they are available for team members to refer to. This repetition is critical for the working agreements to become part of the teams "DNA"; to be embedded into the teams culture so that following these agreements is simply how we work with each other every day.
Some examples of short, direct, actionable working agreements for Scrum teams are:
For remote teams, other working agreements may also be appropriate:
Hold each other accountable
Team members hold each other accountable for their behavior. This needs to be done in a non-confrontational way. By having known working agreements, that the team has developed and everyone has agreed to; a simple reminder like "hey, we agreed to come to meetings on time and focus, remember?" may be enough. If not, as leader, you may call a team meeting to address the behavior (not the person) and keep the meeting focused on the positive.
Review working agreements regularly
It is important that the team inspects and adapts their working agreements on a regular basis. Team context shifts, membership changes, or simply discovering a conflict we need to resolve and remember should trigger a discussion about evolving our working agreements. As a leader, bringing this up as a topic in a retrospective may be appropriate. Perhaps this is a regular agenda item when a new release cycle is starting; or an ad hoc meeting is called when a difficult conflict within the team is being resolved so we can track what we've agreed to.
Agreements become part of the culture
Good working agreements provide structure for a team to develop a shared norms, trust, and psychological safety leading to a positive team culture that enables a safe, collaborative, productive working environment. Your role, as a leader, is to facilitate so that the team has good working agreements, lead by example in following the agreements, and promote awareness of positive behavior.
Scrum masters, do you know what your team’s working agreements are? Does every team member know them? Is a review of the team working agreements included as part of on-boarding any new team members? As a team do you review your working agreements on a regular basis? With all the benefits that explicit working agreements provide, you and your scrum team may want to review and update yours!
Welcome to the Applied Scrum blog! Here, we'll be dropping in articles that we've mentioned in our newsletters if you're interested in understanding more about Agile trends and lessons.
The Agile Coaching Growth Wheel
Love this newest iteration of the Agile Coaching Growth Wheel that Scrum Alliance is sharing! The wheel is based on the model for Agile coaching from Lyssa Adkins and Michael Spayd, adding new depth and definition to support and aid Agile coaches as they develop and improve.
In the wheel, there are nine skill competency areas identified for an Agile coach. These are: self-mastery, agile/lean practitioner, serving, coaching, facilitating, guide learning, advising, leading and transforming.
To help coaches on their coaching journey, each skill area has 5 skill levels of beginner, advanced beginner, practitioner, guide and catalyst.
While still a work in progress, there is an assessment tool to help you asses your skill level. Currently the assessment is a work in progress that focuses on the one competency area of serving the business. There are plans to expand the assessment tool to the additional competency areas.
What a great idea to help professionalize the Agile coach role, and deepen our understanding as we look to our own self-improvement!