logo
logo
Sign in

Can the team avoid Technical Debt completely?

avatar
Naveen Singh
Can the team avoid Technical Debt completely?

Short Answer – “NO”

But WHY?

Product development is complex where we deal with many unknowns, and learning happens throughout the Product Lifecycle.

When one says learning, this learning can be on the business side and the technical side.

Over time, developers evolve on their technical skills and practices, which requires refactoring for the Products.

If not done or partially done, or delayed refactoring leads to Technical Debt and hence the legacy code.

During the initial stages of Product Development, the team sometimes takes the conscious choices to knock the quality for early time to market. These choices require constant refactoring once the Product takes its position in the market, but these usually get ignored due to the constant features additions to the Product. As a result of this, the Product becomes unstable or unreliable. Once the Product starts to mature, the code it carries becomes legacy code. The technology evolves, and this also leads to technical debt, because Products do carry the burden of old technology.

The evolving Definition of DONE of the Product also leads to technical debt. The Product evolves by learning from the market, and the DoD evolves to purvey these learnings. Consider the DoD started to evolve Sprint after Sprint, and then all the previous Sprint deliverables lead to the technical debt, which requires refactoring.

To view the full blog and this blog "Technical Debt" is originally published on Agilemania website.

collect
0
avatar
Naveen Singh
guide
Zupyak is the world’s largest content marketing community, with over 400 000 members and 3 million articles. Explore and get your content discovered.
Read more