—Working agreements should be unambiguous principles.In "Working Agreements for Agile Teams", I discuss how I prefer a working agreement to be unambiguous and not use descriptive language. One example, I provide:
We agree to use topic branches for development and merge our patches to the main line after completing unit testing and code reviews.I pointed out that the use of "topic branch" as too descriptive but didn't provide any reason why I thought this.
Work agreements are the set of rules/disciplines/processes the team agrees to follow without fail to make themselves more efficient and successful.So is a working agreement a principle that reasonable people can disagree with or is it something to follow without fail?
Scrum teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. To become self-organized, a team has to go through various stages of team development.This article then goes on to list agreements for every Scrum Event. How much prescription is too much?