Agile team agreements, or team covenants, are crucial to the smooth functioning of an Agile workflow in any organization. These agreements are conventions decided by the team members which outline the team’s common understanding of how they will work together to achieve their objective.
Agile team agreements can be categorized in numerous ways, but for purposes of this article we will focus on three types: Definition of Done (DoD), Team Norms, and Working Agreements. Each of these agreements facilitates a specific aspect of team collaboration and is essential for maintaining an efficient Agile environment.
1. Definition of Done (DoD)
The Definition of Done is an agreement that is crucial to Agile teams as it brings clarity to when a product increment is considered “done”. This agreement ensures that everyone on the team has a singular and comprehensive understanding of what is needed for a product to be considered complete. For instance, a DoD could specify that a piece of software is not done until it has been coded, tested, and documented.
2. Team Norms
Team norms are rules or standards that guide team member interactions. They exhibit the behavior that is expected and the actions that will lead to team success. These can include norms around communication, decision-making, or handling conflicts. For example, a team norm could be that all team members are expected to participate actively in daily stand-ups and to honestly update their fellow team members on their progress and any blockers they’re facing.
3. Working Agreements
Working agreements detail the standards for tasks and work-related aspects such as working hours, tool usage, meeting schedules, and others. This type is highly contingent on the team’s unique circumstances, needs, and preferences. For example, a working agreement in a distributed team could specify core working hours where all team members are required to be online and available.
In order to uphold these agreements effectively, it is essential to have a clear and actionable plan. Here’s a sample action plan for sustaining agile working agreements:
- Regular Reflection: Reflection on the working agreements should be conducted during retrospectives to ensure they’re still serving the team as intended. Revisit the agreements every so often to determine if they remain effective and relevant.
- Easy Accessibility: The agreements should be stored in an easily accessible location for all team members to refer to when necessary. This could be a shared digital space, such as a team wiki or similar.
- Foster Open Communication: Encourage team members to voice any concerns or suggestions regarding the agreements. Having a safe space for open dialogue allows team members to discuss and propagate changes.
A strictly-adhered-to set of working agreements can help Agile teams in avoiding unnecessary misunderstandings, reduce conflicts, and achieve their objectives more smoothly. The result is an environment where collaboration is smooth, progress is easily tracked, and team members feel clarity in their roles and responsibilities. These agreements allow for true Agile maturity, providing enhanced performance and productivity. Just like our codes, let’s strive for self-documenting teams!
Practice Test
True or False: The Scrum values are not part of the agile working agreements.
- a) True
- b) False
Answer: b) False
Explanation: Scrum values (commitment, courage, focus, openness, respect) are core of agile working agreements. They are fundamental to support teams’ interaction and collaboration.
Which of the following is NOT a kind of agile working agreement?
- a) Definition of Done Agreement
- b) Social Contract Agreement
- c) Technical Framework Agreement
- d) Leaving Early Agreement
Answer: d) Leaving Early Agreement
Explanation: Leaving Early Agreement is not an agile working agreement. The three main types of agile working agreements are Definition of Done Agreement, Technical Framework Agreement and Social Contract Agreement.
True or False: Agile working agreement includes the agreement of sprint duration.
- a) True
- b) False
Answer: a) True
Explanation: Agile working agreement includes the agreement of work process, which includes sprint durations.
Which of the following is a component of the Technical Framework Agreement?
- a) How disagreements will be handled
- b) The common code styling
- c) The team’s working hours
- d) The definition of done
Answer: b) The common code styling
Explanation: The Technical Framework Agreement includes things like the code repository or the common testing and coding practices.
Which of the following is NOT a necessary action to uphold an agile working agreement?
- a) Annually reassessing the agreement
- b) Regularly reviewing and adapting the agreement during retrospectives
- c) Holding team members accountable for the agreement
- d) Ignoring the agreement when convenient for the team
Answer: d) Ignoring the agreement when convenient for the team
Explanation: Ignoring the agreement would undermine the effectiveness of having an agile working agreement.
What is the purpose of a Social Contract Agreement in an Agile team?
- a) Determining the technical processes team members must abide by
- b) Setting the definition of “done”
- c) Defining the team’s working hours and protocols
- d) Establishes how team members agree to interact and behave with each other
Answer: d) Establishes how team members agree to interact and behave with each other
Explanation: A Social Contract Agreement is about defining and respecting each other’s working styles and personal boundaries.
True or False: In Agile Methodology, working agreements need to be rigid and should not change over time.
- a) True
- b) False
Answer: b) False
Explanation: In Agile, practices and agreements are dynamically designed to change and evolve according to changing context and needs.
In Scrum, Definition of Done (DoD) Agreement is primarily:
- a) A functionality list in the product backlog
- b) An agreement that sets shared understanding of what it means for work to be complete
- c) Contract between the Scrum Team and stakeholders
- d) A agreed list of technical standards to be followed
Answer: b) An agreement that sets shared understanding of what it means for work to be complete
Explanation: DoD is a shared understanding of what it means for work to be complete, and is represented by a list of tasks and conditions that must be met.
Agile working agreements are typically created:
- a) At the beginning of the first sprint
- b) At the end of the project
- c) In between sprints
- d) At the end of each sprint
Answer: a) At the beginning of the first sprint
Explanation: Agile working agreements are typically created during the forming or storming phase of team development, which occurs at the beginning of the first sprint.
Which is an action to uphold Agile working agreements?
- a) Including them in performance evaluations
- b) Regularly revisiting and updating them
- c) Integrating them into the physical environment
- d) All of the above
Answer: d) All of the above
Explanation: All the choices are valid strategies for upholding Agile working agreements, supporting ongoing commitment and adaptation.
Interview Questions
What are three types of Agile working agreements that can be proposed between teams?
The three types of Agile working agreements that can be proposed are Definition of Done Agreement, Working Hours Agreement, and Code Review Agreement.
Can you explain what a Definition of Done Agreement is in the Agile methodology?
A Definition of Done Agreement is an agreement that outlines what must happen for a task or user story to be considered complete. It includes aspects like code reviews, testing, and documentation that are required before marking the task as done.
What is a Working Hours Agreement in Agile teams?
A Working Hours Agreement specifies the hours during which team members are expected to be available and working. This is crucial in distributed teams across different time zones to ensure collaboration and timely communication.
What role does a Code Review Agreement play in Agile teams?
A Code Review Agreement in Agile teams outlines the process for reviewing and approving code contributions. This helps maintain code quality, share knowledge among team members, and prevent potential issues from making it into production.
What is one action plan to uphold the Code Review Agreement in Agile teams?
One action plan is to incorporate code reviews into the daily routine. All team members can be required to allocate a certain amount of time each day to conduct and respond to code reviews.
What is an action plan to uphold the Definition of Done Agreement?
An action plan to uphold the Definition of Done Agreement is to have it visually present and referred to at relevant stages of work, such as during daily stand-ups or before starting a new task. Everyone in the team should be clear about what ‘done’ means and adhere to it.
How can an Agile team uphold the Working Hours Agreement?
An Agile team can uphold the Working Hours Agreement by respecting each other’s time, planning meetings within the agreed hours, and avoiding sending non-emergency communication outside those hours.
What is a Team Norms Agreement in Agile teams?
A Team Norms Agreement is an agreement on shared standards and behaviors within the team. It can guide how the team communicates, how conflict is handled, or how decisions are made.
How can Agile teams uphold a Team Norms Agreement?
Agile teams can uphold a Team Norms Agreement by regularly revisiting and discussing them and ensuring that all team members understand and commit to these norms. Feedback and adjustments can be made when necessary to keep the norms relevant and effective.
What role does Respect Agreement play in Agile teams?
A Respect Agreement outlines how team members should treat each other. It often includes guidelines for addressing conflict, giving critiques, and promoting a safe and inclusive environment.
How can Agile teams uphold a Respect Agreement?
Agile teams can uphold a Respect Agreement by modeling respectful behavior, addressing disrespectful behavior immediately, and creating a culture of open communication where issues or concerns can be addressed honestly and promptly.
Why are agile working agreements important to successful project delivery?
Agile working agreements are important to successful project delivery as they align expectations, improve communications, and prevent potential misunderstandings that could impact the project.
What is an action plan to maintain the effectiveness of Agile working agreements?
An action plan could include regular reviews and updates of the agreements, creating a culture of open and respectful feedback, and ensuring all team members uphold the agreements.
How can Agile working agreements impact team performance?
Agile working agreements can enhance team performance by fostering better communication and collaboration, clearing up expectations, and minimizing potential conflicts or misunderstandings.
How does leadership support the upholding of Agile working agreements?
Leadership supports the upholding of Agile working agreements by leading by example, creating a culture of trust and respect, and facilitating open and honest communication around the agreements. They may also ensure that any hindrances to adhering to these agreements are promptly addressed.
extutorials.com