All sprints should update the labour agreement, often through a retrospective review and a question such as: “Are these still our work agreements? What do we want to update? What are the areas that require new agreements? There is no formal or correct way to create work agreements, so Steve uses the approach I share in my workshops. As usual with a ScrumMaster, good preparation pays off. Consider informing the team in advance of the agree categories/areas. Scrum of Scrums requirements can change in the event of development efforts, errors and other implementation problems, so it is important that the team is adaptable. In addition, the team should ensure that it follows the basic rules prescribed in the standardization phase. The basic rules will be essential when the Scrum of Scrums team has personal conflicts. If this is the case, the team should review the rules and enforce all agreements. Charles Bradley wrote a blog post on resuscitation of the much despised Scrums, in which he described how the scrum of Scrum teams working together on the same product can help plan and coordinate development work: a Scrum of Scrums is a technique to adapt Scrum to large groups of more than 12 people, where groups are divided into agile teams of 5 to 10. Each daily scrum includes a member designated as an “ambassador” to participate in a daily meeting with ambassadors from other teams, Scrum of Scrums. A scrum-of-scrums stand is a meeting to coordinate dependency between scrum teams.
The work agreements should be reviewed at the end of each final sprint during the retrospective session. As soon as team members feel that they are doing well with each agreement and that there is something else that needs to be addressed/discussed and added as a working agreement, they can replace it with another consensus agreement. In projects involving few people, Scrum is the guide and mentor who guides the team in the right direction. However, as several teams work together on the same project, there must be a manager capable of effectively working together on the teams. In such a scenario, each team has its own Scrum Master, which in turn coordinates with the Scrum Masters of other teams under the direction and supervision of a general program manager, known as the Agile Program Manager. Source: scrum-master.info It seemed that the teams were not able to solve problems between meetings. Morgan suggested that scrum masters started writing problems and starting to work on them instead of complaining about them in the Scrum-Of-Scrum. He also organized an opportunity for scrum-Meister to meet in person and get to know each other better: break groups of more than five people in subgroups.
In my experience, it is easier to reach an agreement on small groups first and then put them back together. Chris Spanner is a Agile@Scale consultant with a passion for transformations that set new ways of working. Currently, Chris combines the organization`s business strategy with technical execution for different clients and, as Jira Align Solution Architect, helps advance transformation paths. Outside the office, you`ll probably find it in summer motorcycle and skiing in winter. Ideally, a Scrum-of-Scrums should have a separate Scrum master who does not wear the Scrum Master hat for another team. This person should be the referee who blows the whistle when the match starts to slide off the agile track.