08 Apr Agile Scrum Team Agreement
The goal of setting team standards is to build a culture of the ONE team, and that`s something to send it back when it gets rocky within the team. A work agreement is a short series of policies developed by the team for the team that define the team`s expectations. A well-written agreement should help create and strengthen a clear and shared understanding of all team members about what they recognize as good behaviour and for good communication. It is generally referred to as a single “work agreement,” but in reality it consists of many individual agreements for each subject or subject. We may need to check and adapt the way we interact with each other. We may need to review and adapt the way we work with other teams or stakeholders. It is important to ask the team what will happen from their point of view. Your answers might surprise you. […] groups can help overcome rough spots, the social friction that teams experience. If you read Scrum by Example – Team Friction Inspires Working Agreements, you`ll learn to move on […] On the other hand, I saw teams hanging on a wire and barely hitting their targets, because the team members couldn`t see them attacking the whole thing and not being invested. Fortunately, there is one way to solve this problem: the teamwork agreement. Bruce Tuckman first proposed in 1965 the team development model “training, storming, standardizing, implementing.” He said that these phases are all necessary and inevitable for a team to grow, meet challenges, tackle problems, find solutions, plan the work and produce results. Scrum Guide “The Five Scrum Values” www.scrumguides.org/scrum-guide.html#values Steve begins to call for 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, the team has the first working agreements after 20 minutes: it requires an agreement between the team and the product owner on the details of the user stories that the team needs for development. This can be a measure of the quality of these user stories. It is important to have some basic user reports with defined points to make a relative comparison of the stories to be enjoyed. All team members should agree on these stories of basic users.
In the next retrospective, I decided to test the water first. I talked about how I met my wife and played our wedding dance video (which proved to be a great success for the Indian teams). Then the SM shared family photos and talked about each of his children and their interests. The PO opened its move from Seattle and the stress that had caused, especially with the packaging and removal of a huge house. One after the other, the team opened up, and when I looked around, people started to intimidate each other and spread their hearts. Some stories made teams sad, some stories made teams happy, but all shared something nearby, and they were expensive, and emotions grew. We partied with a member of the team who beamed with pride and let us know that his daughter had been admitted to a very prestigious university. We cried with another who said that a parent was suffering from an illness and how difficult it was to deal with it. The team exchanged delicious recipes and enjoyed seeing family photos and hearing the stories behind them.
For the first time, feelings were stoked when cultural and distance barriers were torn off. We have all been part of each other`s lives.