If you opt for a team work agreement, the most important thing is to make sure that your team is fully involved in the whole process. Make sure it is addressed to all „itchy” or uncomfortable topics and that the agreement is placed in a place that is easily accessible to the team. Instead, you should talk about these issues as a way to be a proactive and self-organized team and use the agreement as an action plan to overcome them. If your team has been working together for some time, you have identified some of the key issues or concerns that your agreement needs to address. Then set a timer for about five minutes and ask the team to generate as many ideas as possible for work standards. This is a good time to remind them of the agreements that „We believe… to look at the situation. or `We appreciate…` To avoid having to clean things up later. An important part of the agile process is the maintenance and refinement of the backlog, where an activity involves assigning estimates to stories that have not yet received one. This estimate is usually made by planning poker, where sizes are assigned based on the Fibonacci sequence.
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. Don`t try too hard to come up with a perfect teamwork arrangement on screen. The work agreement screen, like everything else, evolves in the context of an agile team, if we learn more. The more we work together, the more we learn from each other and what improves (or hinders) our work dynamics as a team. Some of what we have now introduced into the labour agreement will not be pitifully irrelevant in a few weeks or months, while new things emerge (for example. B, new additions to standards and guidelines) require attention and are naturally found on the work agreement screen. It is ok. It shows that we are indeed learning, that we are evolving and that we are constantly generating. Working agreements, also known as team standards, are guidelines developed by teams on how they should work together to create a positive productive process.
The web created by Avi Schneier and the Scrum Inc. team  encourages the team to ask questions that go to the heart of the team dynamics, standards and policies they commit to putting on the table, through the skills they want to put on the table and the skills they want to learn from each other, to how they celebrate success and learn from failure. In this article, I will discuss how I adapted the original Avis screen to the needs of the teams I have coached, clarify the various elements of a working agreement and share with you a step-by-step guide to facilitate collaborative workshops for the development of working agreements.