Google's Systematic Approach to Tackling Technical Debt

2025-05-08
Google's Systematic Approach to Tackling Technical Debt

Google engineers faced the challenge of technical debt slowing down development. They systematically defined ten categories of technical debt through surveys, data analysis, and cross-functional team collaboration. A maturity model was developed to assess teams' debt management capabilities. Through education, tooling, and process improvements, Google significantly reduced the impact of technical debt on engineer productivity, highlighting the importance of systematic management rather than aiming for zero debt.

Read more
Development

Why Software Estimation Is Always Wrong (and How to Improve)

2025-04-02
Why Software Estimation Is Always Wrong (and How to Improve)

In Scrum teams, story points estimate effort, but software estimations are inherently flawed. They predict an unknown future, and project complexity, unclear requirements, and technical debt contribute to inaccuracies. Cognitive biases like Hofstadter's Law, Brook's Law, and the planning fallacy exacerbate the problem. The article explores improvements: tracking progress, adding buffers, using the COCOMO model, and an alternative from "NoEstimates": dropping story points, focusing on throughput and cycle times, and using visual tools like Kanban.

Read more
Development estimation