For other readings and examples of work agreements, we recommend other work agreements: “Documentation for Critical Tasks” (the team projects them as a partial task during planning, anywhere) and “Identify dependencies” (to identify dependencies at an early stage and document them on notes, either at preliminary meetings or when planning meetings). Fun Fact, I went with friends a few nights ago and two of them used to get into heated arguments about random topics. So when we drove, I explained the definition of employment contracts and explained how their behaviour concerned everyone else, we laughed, but we agreed, “no heated debates about friendly excursions”. It worked! There was no way out as they would agree on this! 😉 There is no right answer to what your “definitive” work agreements should be. We recommend: To keep the discussion on track, use facilitation techniques like Faust of Five to reach consensus on all labor conventions. Work agreements are the rules/disciplines/processes that the team is ready to follow, without making themselves more effective and simplistic about the self-administered aspects of the Scrum. These agreements help the team develop a common understanding of what it means to work as a team. You can use the first few minutes of the meeting to draw up a short list of work agreements that only apply to that event. This approach helps all participants achieve the same way of thinking and helps you as a moderator manage the event smoothly and with clear expectations. Work agreements have quickly become an essential part of modern and successful teams. You may have heard that the term is thrown around, especially as new teams, but is it worth talking to your own team? These agreements are drawn up by teams and scrumMaster facilitates the meeting, and they are created/verified preferably during the Sprint 0 of each publication.
Your wa list should be clear, so it`s easy to follow and follow. The aspects it should contain depend on the team and the most pressing issues they face when maturity levels are low, you may need to steer the team in the right direction as a moderator, but always remember that these are their agreements. As the VA is agreed upon by all team members, everyone feels responsible for raising a hand if someone breaks the agreement, and it is reminded to the author that he has agreed to respect the standards, it is his own word that is at stake and all issues are dealt with within the circle of trust of the team. We control how people want to interact and what works best for them to achieve their goals, instead of being imposed by the “big bosses”. Steve begins to ask for proposed agreements in his first priority area: Daily Scrum Start Time. After any possible work agreement, it uses the Decider protocol to quickly examine the possibility of consensus. If there is no immediate consensus, the person who said “no” to an idea suggests what they see as a better idea. If more than one person has a problem, everyone is expected to offer a better idea. If too many people say “no,” the applicant should consider withdrawing the proposal. In the case of Steve`s team, after 20 minutes, the team has its first work agreements: group standards – how we communicate with each other, what we think is civil and appropriate, etc. – are generally implicit. We only notice them when they are not working – for example, when someone is doing something that seems unproductive or disrespectful to someone else.
Unfortunately, what appears to be a breach of protocol for you might seem quite acceptable to another. Working agreements, also known as team standards, are guidelines developed by teams on how they should work together to create a positive productive process.