You can use it to clarify the air in cases such as changes in team structure or delivery or collaboration issues. You should repeat this assessment after a few sprints to see if the team has noticed any improvement. These software developers discuss their working arrangements on Zoom and use Trello to capture the inputs. This exercise allows all participants to easily create, discuss and manage team agreements. This can work well for colocation or remote teams. This commitment is supported by writing what all team members see as important protocols that the team must adhere to in order to maximize their ability to deliver faster and with better quality. For more information on this exercise, please contact Bob Fischer or other members of our Agile Consulting team at agileinfo@eliassen.com. You can also learn more about our approach to agile teams through our agile consulting services. First of all, I ask the room to take a look at the sticky notes on the wall and make sure that those who want to consider them for training the whole team have a point on it. If not, I will add other points. Regularly review your team`s working arrangements, especially if the team or work changes or if an agreement can no longer be respected.

When people are too deeply buried in negative thoughts and can`t change their mindset, I break the session and ask participants to do energizing exercises to improve mood. My feeling is that the team will not later execute any plan made during such a state of depression. The goal of team standard setting is to establish a ONE team culture, and that`s something to identify with when things get tough within the team. Draw the same chart on a flipchart and have each team member write down their assessment: “If you were to join a new team, what could you count on your team members?” If you`ve seen our previous articles, you know we`re looking for new team members. With that in mind, I asked myself, “How are we going to share our culture with newcomers?” (Usually, Agile coaches use the jargon “How are we evolving?”) Write down all the ideas and ask the team to sort them in order of importance. You can use silent sorting or point adjustment. Record up to three of the most important ideas and ask the team if this is their choice for experimentation for the next sprint. Create a plan to implement them. Finally, I would like to talk about logistics. I prefer to save this for the end, because towards the end of the meeting with less time, it forces the team to make logistics decisions quickly. Some teams can be too detailed with logistics, so I like to spend less time there. As a rule, decisions made in the field of logistics can be easily changed.

How does the team want to communicate when there are changes in projects? Only via Slack? Here is a high-level timeline. The more people and remote participants there are, the more time you need. Since this is such a valuable and critical exercise, I would take ninety minutes if you can get it. You can always stop if you finish early. Present your working conditions or your team`s values to the team and ask each team member to select the individual statement that is particularly important to them. Ask people to comment on their decisions. Tell participants that the group will do an exercise on team agreements and explain what they are (if the team doesn`t know them). Explain that it`s important to have team agreements for a new team that`s starting today or already running so they can focus on improving performance. You can adapt according to the goal you want the group to have. Previously, we assessed where we are and selected the desired state. (Review the states that the team found to be real and desirable in Exercise 2.) Let`s add our current status to this chart. Once the volunteer has read their sentence aloud, ask the team: Karat helps companies hire software engineers by running and designing technical interview programs that improve the hiring signal, reduce bias, and reduce the time spent on engineering teams for interviews.

Before the working arrangements session, collect the issues the team is currently facing, either from an obstacle committee (see example), a retrospective, or just familiar challenges. Bring them and share them during the session to support work arrangements. At a count of three, each team member raises their fist and shows a number from 0 (bad) to 5 (large). Ask anyone who shows a 0 to 3 what can be improved to bring it to a 4 or 5. Use this feedback for future meetings/retrospectives or discussions on working arrangements. This article is exactly what I needed! We already use Azure retrospectives, which is easy to match the exercise. The second question I`m going to ask is, “How are we going to create an environment as a psychologically safe team for all team members? If at least one person answered yes, add this message to the whiteboard in a column labeled “Candidates for team-wide agreements.” There are many different articles online on the “right” way to create an agile teamwork agreement, but I think it`s best to develop a creative process that works well for your team and culture. .