Description
Our in-house training “Managing Technical Debt” provides you with the necessary knowledge and practical skills to identify and assess technical debt in your company, sell improvements to your stakeholders and develop a clear plan for the future. We will alternate between a theory block followed by a practical application of the theory to your specific problems in order to create a good launch pad for technical debt management within your organization at the end of the training.
The training starts by analyzing the negative impact that problematic code, inappropriate architecture or outdated technology has on your stakeholders.
We will then evaluate these different types of technical debt based on various factors such as product or business strategy, costs, risks, architecture goals and opportunity costs.
We will then develop concrete improvement proposals and measures to deal with existing technical debt. We will use Architecture Decision Records (ADR) and pattern catalogs for refactoring and dealing with legacy code to identify effective solutions for technical debt and to document and communicate these solutions together with the assessment using technical debt items.
Finally, we will focus on decision making and planning where it is essential which technical debt should be repaid, rescheduled or not repaid. You will be able to create a detailed plan for the implementation of technical debt items to improve the long-term software quality and productivity of the team.
Translated with DeepL.com (free version)
Agenda
Understanding the problem
- Basic knowledge of technical debt
- Collection of problems triggered by technical debt
- Stakeholder analysis
Evaluation
- Evaluate technical debt according to strategy, costs, risks, architectural goals and opportunity costs
- Create technical debt items
Suggestions for improvement
- Architecture Decision Records (ADR)
- Pattern catalogs
Decide and plan
- Pay or not to pay?
- Planning Technical Debt Items
Your Benefits
This training is only conducted in-house so that we can work on the real problems caused by the participants’ technical debt.
Audience
Product owners, software developers and architects
Training Objectives
Participants can collect and prioritize the different types of technical debt (code, architecture, obsolete technologies) of their system
Participants can evaluate, plan and implement the selected improvements together with their product owner and other stakeholders
Your Trainers
Sven Johann
INNOQ
DevOps, program chair of GOTO Amsterdam
- CPSA Foundation Level
- Cloud-Native Teams
- Evolution and Improvement of software architectures
- Managing Technical Debt
Sven Johann is Senior Consultant at INNOQ and has been involved in the modernization of medium and large Java applications for many years. He is an active participant in various workshops of the Software Engineering Institute (Managing Technical Debt) and the Leibnitz Zentrum für Informatik (Dagstuhl Seminar »Managing Technical Debt«). He is also Program Chair of GOTO Amsterdam and Show Host of Software Engineering Radio.
Our Customers Say
The workshop was a lot of fun for the participants and we were able to take away some topics, especially from the second half. It was also nice to see that we are already doing and living some things right. Personally, I'm particularly pleased about this because the correct handling of technical debt is an important topic for me as a CIO, especially when it comes to long-lasting systems.
Relevant Other Training Courses
Evolution and Improvement of software architectures
Improve software systems systematically
Technology 10Methodology 20Communication —from 2,025 €
iSAQB® Module IMPROVE
If you want to learn more about working with legacy systems, you've come to the right place.