Who should attend
- Software and business software professionals who design, develop or manage the construction of software-reliant systems
- Software practitioners who need to quickly gain insights into how to successfully manage technical debt
About the course
Technical debt occurs when a design or construction approach is taken that's expedient in the short term, but increases complexity and cost in the long term. In the course Managing Technical Debt of Software, the concept of technical debt is examined from multiple perspectives, including how it manifests, accumulates, and impacts the software development organization. This 1-day course presents approaches to assess the technical debt landscape and teaches mechanisms by which it can be intentionally managed. The course will examine technical debt management of software using an easy to understand analogy with investment strategy to encourage active management of technical debt, and foster dialogue between business and technical decision makers.
The course provides learners with a practical approach to recognizing, assessing, and managing technical debt. After attending this course, learners will have a better understanding of
- What is meant by the term "technical debt"
- The technical debt landscape and timeline
- How to identify technical debt as software development artifacts
- The role of qualitative and quantitative analysis as applied to technical debt
- How to identify the attributes of static analysis tools for technical debt
- The organization's perspective on managing technical debt
- How the organization manages technical debt to achieve business and quality goals
- Introduction to technical debt
- Technical debt definition framework
- Making technical debt visible
- When technical debt accumulates
- Paying back technical debt
- Living with technical debt
- Concluding thoughts
Student will receive copies of the instructional materials used in the course which includes copies of slides and exercises, including the "Hard Choices" game which simulates the software development cycle for educational purposes.
Ipek Ozkaya is a principal researcher at the Carnegie Mellon University Software Engineering Institute. Her primary work includes developing techniques for improving software development efficiency and system evolution, with an emphasis on software architecture practices, software economics, agil...
Technical innovator whose work on software architectural views has had a noted impact on the architecture discipline and industry best practices. Robert Nord is a principal researcher at the Software Engineering Institute (SEI) where he works to develop and communicate effective methods and prac...
Because of COVID-19, many providers are cancelling or postponing in-person programs or providing online participation options.
We are happy to help you find a suitable online alternative.