Roadmap › Team Lead, Managerial & Agile Interview › Module: Delivery and Stakeholders
Lessons in this course (13)
11. Technical decision-making, debt and quality
Advanced★ Must knowLesson 11 of 13
- Decide with criteria: requirements (functional + non-functional — performance, scalability, security, availability, cost), team skills, time to market, maintainability, vendor lock-in.
- Use spikes/proofs of concept for uncertain choices; document with Architecture Decision Records (context, decision, alternatives, consequences).
- Technical debt: make it visible (backlog items with impact), allocate capacity (e.g. 15–20% per sprint), pay down debt in areas that change often, avoid "big rewrite" unless justified.
- Quality gates: code review standards, automated tests, CI checks, static analysis, Definition of Done.
- Build vs buy: core differentiators → build; commodity → buy/open source.