Facilitating constructive conversations between a team and its stakeholders when priorities and expectations conflict requires a skilled agile coach to act as a mediator, facilitator, and translator. The coach's role is to create a safe and structured environment where all parties can express their perspectives, understand each other's needs, and collaboratively find solutions that balance competing priorities.
1. Preparation and Goal Setting: Before the conversation, the agile coach should meet with both the team and the stakeholders separately to understand their individual perspectives, priorities, and concerns. This helps the coach anticipate potential conflicts and plan the conversation accordingly. Clearly define the goal of the conversation upfront. For example, instead of a vague objective like "resolve conflicts," set a goal such as "reach a consensus on the top three priorities for the next quarter" or "agree on a process for managing changing requirements." This provides focus and direction for the discussion.
2. Establishing Ground Rules: Start the conversation by establishing clear ground rules to ensure that the discussion remains respectful, productive, and focused. These ground rules might include:
Active listening: Everyone should listen attentively to each other without interrupting or judging.
Respectful communication: Everyone should communicate in a respectful and constructive manner, avoiding accusatory or inflammatory language.
Focus on the problem, not the person: Discussions should focus on the issues at hand, rather than on blaming individuals.
Time boxing: Allocate specific time limits for each topic to ensure that the conversation stays on track.
One speaker at a time: Ensure that only one person speaks at a time to allow everyone to be heard.
The agile coach should facilitate a discussion to agree on these ground rules and ensure that everyone understands and commits to them.
3. Active Listening and Empathy: Encourage active listening and empathy by asking open-ended questions and prompting participants to share their perspectives and understand each other's needs. For example, the coach might ask the team, "What are your biggest concerns about the stakeholders' proposed priorities?" or ask the stakeholders, "What are the business drivers behind your requests?". Paraphrase and summarize what each party says to ensure understanding and demonstrate that their voices are being heard. For instance, "So, if I understand correctly, the stakeholders are concerned about the increasing churn rate and believe that this new feature will help to address it?"
4. Identifying and Visualizing Priorities: Help the team and the stakeholders identify and visualize their respective priorities. This can be done using techniques such as:
Priority Matrix: Create a matrix with axes representing value and effort, and plot the different features or initiatives on the matrix to visualize their relative priorities.
MoSCoW Prioritization: Categorize features or initiatives into "Must have," "Should have," "Could have," and "Won't have" categories to clarify their relative importance.
Story Mapping: Visualize the user journey and prioritize features based on their impact on the overall user experience.
The agile coach can facilitate this process by guiding the team and the stakeholders through the different techniques and helping them to reach a shared understanding of the relative priorities.
5. Finding Common Ground: Look for areas of common ground and build upon them to find mutually agreeable solutions. This involves identifying shared goals, values, and interests, and then exploring how the conflicting priorities can be aligned to achieve those shared objectives. For example, both the team and the stakeholders might agree that improving customer satisfaction is a top priority. The coach can then help them explore how the different features or initiatives can contribute to that shared goal.
6. Negotiation and Trade-offs: Facilitate a negotiation process where the team and the stakeholders can make trade-offs and compromises to balance competing priorities. This might involve deferring some features to a later release, reducing the scope ....
Log in to view the answer
