SINGLE POST

Working Agreement Example

These five agreements must be posted in the common space of the team. Let`s start with the definition: work arrangements are standards or guidelines created by a team to improve their interactions in order to achieve better performance and create a common language. Concretely, these agreements define the expectations of the group, establish paths of cooperation and create the kind of atmosphere necessary for empathetic and psychologically safe work. As with any setting, it`s important to tailor it to your own needs and culture. When introducing work arrangements into your team, consider the most appropriate approach. There is no official or correct way to create work arrangements, so Steve uses the approach I share in my workshops. As usual with a Scrum Master, good preparation pays off. Consider informing the team in advance of the categories/areas of agreement. Ask all team members to come together to define your custom list. Remember that your role is that of a moderator.

So make sure you have your agenda ready and clearly communicate the purpose of the meeting. If this is the first time the team has established work arrangements, start by clearly defining what they are so that people know what is expected. You`re welcome! That`s far from all there is to do for work arrangements, so go ahead and learn more about it! And if you wish, share some knowledge in the comments ☺ To keep the discussion on track, use moderation techniques like Fist of Five to reach consensus on all working arrangements. The Scrum Master then suggests that the team reflect on the crucial points for their improvement and asks them to share the points that they believe should become working arrangements. Work arrangements, also known as team standards, are guidelines developed by teams on how they should work together to create a positive and productive process. First, set the context for working arrangements with your team. As a group, you can use whiteboards (physical or numeric), sticky notes, spreadsheets, or flip charts. Set a chart that`s visible to everyone, and a good start is to brainstorm and write everything down. You can start the conversation with examples so the team gets a feel for what the list will look like once it`s ready. Some examples (finally!) that you can use are: “Attend all team meetings on time”, “Increase obstacles early to avoid delays”, “No phones allowed in daily stand-ups”. You get the idea.

Review your notes and lessons from past retrospectives, it should remind you of the recurring issues the team has faced and serve as a starting point. Steve starts asking for proposed deals in his first area of interest: the daily Scrum start time. After all possible working arrangements, it uses the Decision-Maker Protocol[2] to quickly seek consensus. .