About Technical Debt Masterclass
Module Content
14 Lessons
Free
Technical Debt has become more evident in the last decade as the pace and horizon of change continues to expand. This debt is a backlog of work caused by not doing regular cleanup, maintenance, and standardization during product development to make future work easier.
Lesson 2: Technical Debt Overview
Technical Debt. Technical Debt Overview. Iterative development recognizes we will probably get things wrong before we get them right. We use multiple passes to improve what we are building to converge on a good solution.
Lesson 3: Is Technical Debt Bad?
Technical Debt works in a similar way to financial debt - when you take shortcuts to roll out a product on time, you basically take on debt. The symptom is the more debt you take on, the more it slows you down, and the more you will have to take on in the upcoming stages of the project.
Lesson 4: Why care about Technical Debt?
You should care about technical debt - developers must deal directly with technical debt, so while it may make their job easier today, it will certainly make it a lot harder and in the long term, more time-consuming.
Members Only
Lesson 1: Technical Debt Iterations
If the team does not pay attention to quality, it will soon become impossible to release anything rapidly. Perform frequent incorporation of work into the whole, no matter the product, and then retest to determine that the entire product still works as intended.
Members Only Technical Debt Repercussions
The impact of Technical Debt grows in an unpredictable, nonlinear manner. Taking on technical debt is taking a loan today against the time needed to do future work.
Members Only Technical Debt Velocity
Sponsors usually want to know when the project will be done. Once the team establishes a reliable velocity (average stories or story points per iteration) or the average cycle time, the team can predict how much longer the project will take.
Members Only Compounding Technical Debt
Do you want to cut scope to reach the desired release date, or increase schedule duration to deliver on the likely release date? Accelerated velocity takes on technical debt by cutting corners, poorer design, reduce testing, etc.
Members Only Making Technical Debt Visible
No product can be debt-free since such economics may not be justified. Technical Debt should be kept low enough so it does not significantly affect product development.
Members Only Economics of Technical Debt
An important cause of technical debt is when work that should have been performed when a feature was built but ended up being deferred. The more technically encompassing the definition of done checklist is, the less likely of accruing technical debt and improving economics.
Members Only Servicing Technical Debt
The team sets a budget of time to allow for servicing happened-upon technical debt when it is discovered. Happened-upon technical debt that is NOT serviced should be classed as known debt and made visible for corrective action or not.
Members Only Technical Debt – The Big Picture
In enterprise IT, technical debt comes in the form of legacy hardware and software, inefficient maintenance processes, outdated communications or inadequately maintained products/software, lack of scalability or resiliency, and poor user experiences.
Members Only Technical Debt Predictive Methods
There are still business and project deadline pressures. Technical Debt reduces team effectivity and product quality. The accelerated effort, long hours increases technical debt by cutting corners, poorer design, reduce testing, errors, etc.
Members Only Technical Debt Discipline
evident in the last decade as the pace and horizon of change continues to expand.
Comments are closed.