So team agreements. In many interviews I do with remote teams, I hear that creating a set of basic rules helps to reduce misunderstandings. Through my workshops, I learn that very few companies have team agreements. So I wanted to talk a little bit about the process and the experience of the Happy Melly team, which is completely isolated in the hope that it somehow shows how to establish a team agreement and what the process might look like to you. Phil Montaro from all over office led me with a policy he created for team agreements, and he called it the ICC workflow. I have definitely talked about it in the past. And it represents the breakdown of your work into three categories: information, communication and cooperation. So you would actually ask the team what kind of information you need for the projects you are working on, what types of communication you use to do your job, and how they know what everyone is doing. It is important to remind the team that these actions are not even cancelled. They can (and should) change when we know more about cooperation. Retrospectives are a good time for action that changes an existing labour agreement if we recognize that it is an obstacle to better cooperation. Divide groups of more than five people into subgroups. In my experience, it is easier to reach an agreement on small groups first and then put them back together.
Now that you have the basics, here are examples of some clauses that you could include in your teamwork agreement. Some of them are specific to agile teams. Once we were all done, we took the opportunity to talk about each sticky team note. And the things we agreed on were placed in a Google Doc. At first, I remember it was a relatively painless process. There have not really been any major disagreements about anything for which we have just established the ground rules. What are the expected reaction times? And how are we going to give each other feedback? And what tools would we communicate with? So just a set of fundamental rules. And the idea was that we would evaluate them regularly. These agreements have spared me a lot of grief, so I shared below some tips on how to create one that works for your agile team. I also added three examples of clauses that I used for my teams that you could use. Finally be creative to deal with your problems and a little fun with the deal.
Finally, it is a «social» contract. There is no formal or correct way to create work agreements, so Steve uses the approach I share in my workshops. As usual with a ScrumMaster, good preparation pays off. Consider informing the team in advance of the agree categories/areas. Here are some important things you need to keep in mind when creating your own teamwork contract. Instead of restarting the ICC workflow from scratch, I decided it would be easier to go through the Google document point by point of what we had decided last time, and just take a look at everything we wrote and decide on its relevance. And I admit it was a bit difficult to get on the list. So I wonder if there`s a way to make it more fun. But even that highlighted some differences in the way we use the tools, and it gave us an opportunity to clarify some of the assumptions that were very interesting.
For example, Chad, our illustrator, it [inaudible – 05:02] Status updates, and other people are very attentive and really watch it every day.