Safe Working Agreement

This story of self-discovery traced the journey of a team of geographically dispersed and culturally different people. It shed light on the process of how they discovered hidden obstacles to create a better working environment for their team. They reached a moment of revelation that helped two distant groups ally and work together as a team. Their agreement was formally part of the team`s culture, with a series of working agreements binding them. The following table summarizes what I learned as a coach. Both sprints should be updated to the work agreement, often by retrospectively reviewing it and asking a question like, “Is it still our work agreements? What do we want to update? In what areas are new agreements needed?┬áMy name is Alex and I was a project manager. I made the transition to the agile world in 2009 and have never looked back. I appreciated the speed and adaptability of working to Agile depending on the complexity and inertia of the waterfall. I also quickly discovered that it was as simple as Agile, that it was really about changing people`s mindsets to adopt a different professional lifestyle. The change in mentality meant that you had to “show the light” to people, so I became the Agile Coach. Steve begins to question the agreements proposed in his first priority area: Daily Scrum Start Time. After any possible working agreement, it uses the Protocol of Decider[2] to quickly seek consensus.

If there is no immediate consensus, the person who said “no” to an idea proposes what they consider to be a better thing. If several people have a problem, everyone is expected to come up with 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: work agreements are a simple and powerful way to establish explicit guidelines on the type of work culture you want for your team. They are a memory for all of how they can commit to respectful behavior and communication. In this article, we help you understand why these agreements are useful and how you can help your team establish their own agreements. A work agreement is a short set of guidelines developed by the team for the team and set out the team`s expectations. A well-written agreement should help establish a clear and common understanding among all team members of what they recognize as good behavior and communication. It is usually referred to as a single “working agreement”, but in reality it consists of many individual agreements for each topic or problem. These agreements are created by teams and the Scrum Master facilitates the meeting, and they are preferably created/verified during the Sprint 0 of each release.

The theory is that work agreements (VAs) are a set of rules that are generated by the entire team in terms of mentality and behavior within the team. It reduces unwanted friction between team members. I had never been a big fan of work agreements. Of course, I knew what they were, I knew what to do, I had even integrated one or two versions into some of the Agile classes I had taught, but I never understood how powerful the development process can be! As I wanted SM to facilitate the process, I coached them to establish a list of questions for each value, to generate a discussion and help the teams decide on any “rules” we should establish to ensure that everyone respects that value…

Comments are closed.