Conflicts and trade-off conversations
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
surface conflicting requirements and get a decision from an owner.
Planned topics
- Typical conflicts: availability vs cost, latency vs consistency, speed of delivery vs resilience.
- Do not resolve a conflict silently in code; list it with both owners.
- Present options with consequences in each stakeholder's language (money, risk, time).
- Record the decision, owner, and review date.
Draft outline details
Demonstration
a conflict table: "99.95% availability" (operations) vs "no extra infrastructure budget" (finance): option A second region, option B multi-AZ plus faster recovery, with cost and risk per option.
Check your understanding
Who should resolve a requirements conflict?
Show answer
The accountable stakeholders, informed by the engineer's options; not the engineer alone.
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.