Which of the following is the most common cause of technical debt in software projects?
Think about why teams might choose quick solutions over perfect ones.
Technical debt often arises when teams take deliberate shortcuts to meet deadlines, trading long-term quality for short-term speed.
Which type of technical debt is caused by outdated documentation and lack of knowledge sharing?
Think about what happens when information about the system is missing or old.
Documentation debt refers to problems caused by outdated or missing documentation, making it harder to understand and maintain the system.
A team notices their software takes longer to add new features and has more bugs. What is the most likely impact of accumulated technical debt?
Consider how messy or quick fixes affect future work.
Technical debt makes the codebase harder to change, slowing development and increasing the chance of bugs.
Given limited time, which technical debt should a team prioritize to fix first?
Options:
- Debt causing frequent system crashes
- Debt in rarely used features
- Debt in documentation only
- Debt related to cosmetic UI issues
Focus on what affects users and system stability the most.
Fixing debt that causes system crashes is critical because it directly impacts users and system reliability.
A product manager wants to add many new features quickly, but the engineering team warns about increasing technical debt. What is the best approach to balance these needs?
Think about sustainable development practices.
Balancing feature delivery and technical debt requires planning time to fix debt regularly while continuing development.