Prioritizing reliability and debt
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
choose between features, reliability, and debt using evidence.
Planned topics
- Use the error budget: budget left allows feature work; budget spent shifts effort to reliability.
- Evidence for debt: incident count, time lost, change failure rate, onboarding pain.
- Express debt as cost and risk: "this costs two days per release" beats "the code is ugly".
- Rank by impact over effort; pick the top few and schedule them, with capacity reserved.
- A debt list that is never prioritized is only a complaint list.
Draft outline details
Demonstration
a table: item, evidence, cost per month, effort, decision.
Check your understanding
What does a spent error budget suggest?
Show answer
Prioritize reliability work over new features.
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.