Consensus-Driven
Scrum focuses on a consensus-driven approach where decisions are made with mutual consent. It emphasizes that the team as a whole comes to an agreement and decides the best possible solution. This process ensures that every member is heard, valued, and contributes to the decision. Though this may be time-consuming, it leads to a more democratic and fair system that helps in building strong bonds and a sense of unity among team members, thereby substantially increasing the team's overall performance.
Guide: Consensus-Driven in Cross-Functional Teams, Scrum
Consensus-Driven refers to a decision-making process in which all team members develop and agree to support a decision. This approach ensures that everyone's opinions are heard, considered, and incorporated, and that all team members support the decisions.
It works by soliciting input from all team members and reaching a decision that everyone can support. This support may not mean it’s each team member's first choice, but they can live with it and will back it.
Here are some tips to answer questions regarding Consensus-Driven in an exam:
- Ensure you understand the concept well.
- Remember, it's about collective agreement, not necessarily unanimous agreement.
- Share examples of a Consensus-Driven approach in practice.
- Discuss the benefits, such as increased team collaboration and ownership.
Remember, to answer correctly about Consensus-Driven, visualize it as a critical team interaction tool that boosts cooperation, ownership, and effective decisions.
PSM I - Consensus-Driven Example Questions
Test your knowledge of Consensus-Driven
Question 1
The team is having trouble reaching consensus on the effort estimation for a complex user story. As the Scrum Master, what will be your approach?
Question 2
Your team reached an impasse on a key decision during a sprint. The debate becomes heated and counterproductive. As the Scrum Master, what should you do first?
Question 3
The business stakeholder is imposing a critical decision instead of forming a consensus with the team. As a Scrum Master, what is your best approach?