PMP · Question #257
A project manager is performing the role of scrum master for a team of developers. There is a conflict among the developers, generated by differences in how a feature can be delivered. The project man
The correct answer is B. Allow the team to decide on their own which option should be implemented.. After conducting spikes to gather information, the Scrum Master should empower the self-organizing team to make the final decision on the technical approach for feature delivery.
Question
A project manager is performing the role of scrum master for a team of developers. There is a conflict among the developers, generated by differences in how a feature can be delivered. The project manager organized a few spikes to resolve this conflict. What should the project manager do next?
Options
- AOrganize a multivoting event to achieve consensus of the whole team.
- BAllow the team to decide on their own which option should be implemented.
- COrganize more spike events until consensus of the team is reached.
- DAsk the project sponsor to decide which option should be implemented.
How the community answered
(36 responses)- A14% (5)
- B75% (27)
- C8% (3)
- D3% (1)
Why each option
After conducting spikes to gather information, the Scrum Master should empower the self-organizing team to make the final decision on the technical approach for feature delivery.
While multivoting can be a tool for decision-making, it implies the Scrum Master is organizing the decision directly, rather than facilitating the team's self-organization to arrive at a decision.
In Scrum, the development team is self-organizing and responsible for deciding how to best accomplish sprint goals and deliver features. After conducting spikes to gather necessary information, the Scrum Master's role is to facilitate but ultimately allow the team to collectively decide on the best technical approach, fostering autonomy and ownership.
Organizing more spikes indefinitely without a clear path to decision-making is inefficient and can delay the project, as spikes are meant to gather just enough information to make an informed decision.
Asking the project sponsor to decide undermines the development team's autonomy and expertise in technical matters, which goes against Agile principles of self-organizing teams.
Concept tested: Agile team self-organization & Scrum Master role
Source: https://www.scrum.org/resources/scrum-guide
Topics
Community Discussion
5
Olusegun A.Apr 10, 2026B is correct. In agile the team owns the technical decision, so once the spikes have provided enough information you let the developers pick the approach rather than forcing consensus or escalating.
Ola B.Apr 18, 2026I first leaned toward A because multivoting sounds like a clean way to get consensus, but the agile principle is that the team owns the delivery decision. Once the spikes gave them the technical info they needed, the PM should step back and let the developers pick the path forward themselves.
Wesley A.Apr 20, 2026Spot on, and the word "consensus" in these stems is usually the trap, because it implies everyone has to agree when really the dev team just needs the autonomy to decide based on what the spikes uncovered.
Wesley A.Apr 27, 2026B is right, confirmed on my pass last week. I overthought this exact scenario on my first attempt and picked A, but the agile principle is clear: after spikes provide the technical info, step back and let the self-organizing team make the call.
Grace U.May 6, 2026B is correct here because after spikes provide the technical information, the self-organizing team owns the decision. It can feel unsettling to step back and let the team choose when there was conflict, but what specific agile principle makes that hands-off approach the right call?