AD0-E121 · Question #47
Due to a major conflict In the 'add to cart" functional requirement in the e-commerce project, the development team cannot proceed with the planning and implementation. After a detailed discussion…
The correct answer is D. - Scrum Waste*. Note: Option D appears to contain a typo - "Scrum Waste" almost certainly reads as Scrum Master in the original material. The explanation below assumes that correction. --- When a requirement conflict blocks the team and cannot be resolved through direct discussion between the…
Question
Due to a major conflict In the 'add to cart" functional requirement in the e-commerce project, the development team cannot proceed with the planning and implementation. After a detailed discussion with the product Owner and development team, the requirement conflict is still not resolved. Who should the business Practitioner meet with to resolve this issue?
Options
- A
- Content Owner
- B
- Content Manager
- C
- Business Owner
- D
- Scrum Waste*
How the community answered
(14 responses)- A7% (1)
- D93% (13)
Explanation
Note: Option D appears to contain a typo - "Scrum Waste" almost certainly reads as Scrum Master in the original material. The explanation below assumes that correction.
When a requirement conflict blocks the team and cannot be resolved through direct discussion between the Product Owner and development team, the Scrum Master is the appropriate escalation point. The Scrum Master's core responsibility is to remove impediments - including unresolved conflicts - that prevent the team from moving forward, acting as a facilitator and servant-leader within the Scrum framework.
Why the distractors are wrong:
- A (Content Owner) and B (Content Manager) are not standard Scrum roles and have no authority over requirement prioritization or conflict resolution.
- C (Business Owner) does hold organizational authority, but escalating directly to them bypasses the Scrum process; the Scrum Master should be the first point of contact for process-level impediments.
Memory tip: Think of the Scrum Master as the team's "impediment remover." If something is blocking the team from working - including a conflict that can't self-resolve - the Scrum Master owns that problem. If the PO + dev team can't fix it themselves, it's now an impediment, and impediments belong to the Scrum Master.
Topics
Community Discussion
No community discussion yet for this question.