Detecting the Technical Debt in your software practices
- 1 hour on-demand video
- 12 downloadable resources
- Full lifetime access
- Access on mobile and TV
- Certificate of Completion
Get your team access to 4,000+ top Udemy courses anytime, anywhere.
Try Udemy for Business- After taking this course you will know why software development projects on legacy systems always seem to take longer than expected.
- You will know why it is almost impossible to get accurate estimates for new feature development on a large legacy system.
- You will be able to calculate where your software development operation is on the technical debt acceleration curve.
- This course is designed for Managers and Project Managers working in the Software Development industry or anyone involved in managing software development teams..
- Some experience working in a company that produces commercial software products would be useful, You ideally need an understanding of the different roles and management priorities within a software company..
- Programming experience is absolutely not required, this course is taught in plain English, and all technical concepts will be explained.
Technical Debt costs the industry trillions every year and yet it frequently goes unnoticed, neither measured or managed.
In 2018 the cost of poor quality software in the US was estimated by the Consortium for IT Software Quality at $2.84 Trillion. Within the same report they identified that most IT leaders lack a basis for estimating the answers to how their software practices related to quality affect the overall cost of ownership of software.
In this course, we look under the hood at the software practices which lead to technical debt, and take the first step in addressing this ubiquitous software development problem
We’re going to take a look at some of the common symptoms and categories of technical debt that affect real world software products.
This course is meant for you if you work in a software organisation in a management or project management role, or if you are involved with managing the software practices of your development teams.
After completing this course you will know what the term “Technical Debt” means.
You will be able to recognise key symptoms of technical debt that often hide in plain sight, so that you will be aware when Technical Debt has become a problem that is affecting your own organization's ability to meet your customers needs, or hampering your growth in your market.
You will also know where to begin to look for technical debt in your company, and some of the software practices you may need to adjust.
Knowing that there is a problem with technical debt in your software practices is the first step to solving it, and knowing where to look for the problem is the second step.
- Software Development Managers, Product Managers and Project Managers.
Introduction
This lecture introduces the course with the question 'What Is Technical Debt?'.
On completing this lecture you will know some of the common problems that are caused by technical debt in real world software companies, and which types of companies are affected.
Pre Course Assessment
You will be invited to complete the pre-course assessment which you will find in the resources section.
Please do this now, before moving on to the next lecture.
What Does Technical Debt Mean
After completing this lecture you will be able to explain what the term technical debt means in the software industry.
You will have a useful and practical definition of technical debt that covers all the types of technical debt you need to be aware of as a manager in a software company.
You will know where the term Technical Debt came from, what it means, and how it applies to the software industry today.
Case Study - An e-Commerce Company
Sometimes the easiest way to illustrate an idea is by example. In this lecture you will see a real world example of an e-commerce company struggling with technical debt, and find out how much an early design flaw in the software ended up costing them 10 years later.
After completing this lesson you will feel more confident discussing the impact of technical debt with your development team.
Symptoms of technical debt
In this module we look at the visible symptoms in your company that indicate the presence of technical debt in your software.
After completing this lecture you will be able to recognise the symptoms of technical debt in your own organisation and identify whether Technical Debt has become a problem that is affecting your ability to meet your customers needs or hampering your growth in the market.
Case Study at a Global Software as a Service Company
In this case study we look at a real world example of a large software as a service company who are struggling with a lot of symptoms of technical debt.
You will start to be able to differentiate between a desire to use new technologies for their own sake, and updating parts of the software that are really costing you more than they should be
In this lecture we are going to look at the different places technical debt can be hiding in an organisation and where to start looking for it in your software company.
After completing this lesson you will know where to begin to look for technical debt in a software company.
This is the final module of the course, where we pull together everything that we've been talking about.
After completing this course You will feel confident discussing the impact of technical debt with your development team, and your colleagues and you will be capable of differentiating between a desire to use new technologies for their own sake, and updating parts of the software that are really costing you more than they should be.