Detecting the Technical Debt in your software practices

Why should you care about Technical Debt?

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.

Technical Debt is an escalating problem that affects all software products to some extent. If left unmanaged it increases year on year and is a major cause of frustration not just for the Developers who have to navigate it every day, but also everyone else in the software company.

• Sales people who can’t get reliable dates to safely promise new features to customers.

• Support teams who have to deal with increased bug reports and unhappy customers.

• Senior management who have to deal with unexpected costs, delayed sales payments and ultimately reduced profits.

Who this course is designed for?

This course is designed for you if you work in a software organization in a management role, or if you are involved with managing the software practices of your development teams.

Are you the kind of software development leader who wants to create a more productive environment for your team, where people come to work enthusiastic and excited to work on your products? Then please check the course contents out.

Do you want to head up one of the elite minority of software development teams who are aware and actively managing this problem? If you are, I’d love to see you in class.

What we’ll cover

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.

We’ll look at common types of technical debt, and real world case studies to bring them to life.

• After completing this course you will know what the term “Technical Debt” means.

• You will be able to recognize 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.

What you will get when you purchase this course

• 10 bite sized videos focused on delivering the information you need quickly, illustrated with real world examples.

• The course includes full video transcripts that you can download and keep for future reference,

• Exercises so that you can apply what you learn to your own particular situation.

You will also get a certificate of completion to download and keep at the end of the course.

30 Day Money Back Guarantee

Finally, I have built this course to share the insights I gained from my industry experience over the past 30 years because I want to help more software teams become amazing places to work.  However I don’t want to take your money unless you are satisfied with your course and get value from it.

You can watch the course promo video, and also I have unlocked a couple of the course videos, so that you can try for free before you buy.

In addition, Udemy offers a 30 day money back guarantee if you are not happy with a course, so you can take this course completely risk free. Please check out the Udemy refund policy for the full details.