Resolving conflicting requirements
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
resolve conflicts between stakeholders with explicit trade-offs and a named decision owner.
Planned topics
- Conflicts are normal: e-commerce wants fast release, security wants controls, stores want stable tills.
- First restate each need as an underlying goal (speed to market, protect card data, keep stores trading), which often reveals room.
- Lay out options with what each stakeholder gains and gives up; quantify where possible.
- Name the decision owner. The architect facilitates and recommends; the person accountable decides.
- Record the decision, the trade-off accepted, and the review date, e.g. in an ADR.
Draft outline details
Demonstration
a conflict card: requirement A (release weekly), requirement B (security review per release); options: full review each release, automated checks plus review of risky changes, quarterly review; trade-offs and chosen option with owner.
Check your understanding
Who decides a stakeholder conflict?
Show answer
The accountable decision owner, with the architect facilitating and recording the trade-off.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.