On this page
11. Risks and Technical Debt
Content
A list of identified technical risks or technical debts, ordered by priority
Motivation
“Risk management is project management for grown-ups” (Tim Lister, Atlantic Systems Guild.)
This should be your motto for systematic detection and evaluation of risks and technical debts in the architecture, which will be needed by management stakeholders (e.g. project managers, product owners) as part of the overall risk analysis and measurement planning.
Form
List of risks and/or technical debts, probably including suggested measures to minimize, mitigate or avoid risks or reduce technical debts.
Examples
<insert list or table of known problems, risks or technical debt >
Practical Tips
- Tip 11-1: Search for problems and risks with different stakeholders!
- Tip 11-2: Analyze (external) interfaces for problems and risks!
- Tip 11-3: Identify problems or risks by qualitative evaluation!
- Tip 11-4: Analyze _processes_ for problems and risks!
- Tip 11-5: Analyze data or data structures for problems and risks!
- Tip 11-6: Analyze source-code for problems and risks!
Related Questions
See here for questions related to risks, problems and technical debt.