A DEEPER UNDERSTANDING OF…
Technical Debt
Road to Mastery — Season 2 — Episode 4
Time to talk about the big evil monster in our Product Development universe. Is it our Cthulhu, Morgoth, Chimera, Frankenstein? Or is it the Grim Reaper that will one day come knocking on the doors of every product made. Or perhaps it’s the “Hecatoncheires” who were:
“not only known for their frightful enormity, but also for their ghastly arrangement of hundred arms and fifty heads. Even Uranus was so taken back by their ugliness that he decided to push them back into their mother’s womb. On failing to do so, they were subsequently banished to the underworld […]” — Hecatoncheires
Our creature of dread indeed. It’s time to talk about ‘the one that shall not be named’ and isn’t even mentioned in the Scrum Guide. No, I am not talking about the Project Manager. For the sake of this story we’ll refer to ‘it’ as:
“Technical Debt: the typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership. May exist unintentionally in the Increment or introduced purposefully to realize value earlier.” — Scrum.org Developer Glossary
