Your symptoms assessment is on its way to your inbox right now
so you have what you need to find your technical debt levels
Congratulations on taking the first step to managing your technical debt strategy and making your software engineering workplace a happier, more productive place!
You now have everything you need to assess your technical debt levels using seven key indicators that will tell you how much your company is suffering from this hidden disease, so that you can make a recovery plan and get your development team back on track.
Before you head over there, I’d like to share something else with you.
The next thing my clients usually want to know, is how to find the root cause of these symptoms.
If you’re the kind of software development leader who wants to create a more productive environment for their team, and who wants to head up one of the elite few software teams that is actively managing this problem, then please read on.
If that is you, you may be interested in going deeper into the subject with our online video course, Detecting the Technical Debt in your software practices, which is now live on Udemy.
Great, you’re still here? Please check out the details below.
New Online Video Training Coming Soon
Become A Technical Debt Detective is a video course for software engineering leaders like yourself who want to get to grips with the issues that are cluttering up their legacy software and causing their teams to spend so much time on frustrating firefighting instead of creating awesome valuable features that your customers really love and want to use.
Discover where to find the hidden maintenance costs in your legacy software product so you can remove the blockers and stop wasting your software development resource, stop wasting money and invest in value creation instead to make your software company more profitable.
I believe there’s a new kind of Software Engineering Leader in the world today. Is it you?
This new kind of leader is…
- A coach who knows that software developers, like everyone else, are more productive when they are happy, and happier when they are more productive.
- A leader who will do what it takes to inspire their team to create valuable products that customers love to use and are happy to pay for.
- An expert who is able to to hack the software creation process and even the entire organisation to remove the hidden blockers and road-bumps that get in the way of your teams productivity, causing them to waste time on firefighting instead of creating!
Real tech leaders know that their software engineering team is the powerhouse of their software company, and they make an impact by creating an environment that supports the creativity and strengths of their team, puts them front and centre in the company, and removes all the little distractions and time wasters that get in their teams way. They give their team space to develop mastery of their skills while creating high value products that your customers love.
But the question that may be on your mind right now is what are all these blockers that are getting in the way of my teams performance and where do I find them, so I can get them out of my teams way.
This online video course has some answers based on 30 years industry experience.
How To Detect Technical Debt In Your Software Practices
So you can stop wasting time and money and empower your development team
This 10 part video course is designed for you if you manage a software development team,
and you want to know what is slowing down your team’s performance, wasting money and making everyone’s job harder, so that you can take steps to address the issues that will make the most difference to the effectiveness of your team.
You do not need to be a software developer to get the value from this course!
Special Discount
Use this coupon code to get a HUGE Special Discount only available until August 10th.
£199.99 £37.00 special discount price.
Discount Valid until September 2nd 2020
Become A Technical Debt Detective
Remove the hidden blockers and watch your development team fly!
- Are features taking longer to develop in your software than they used to?
- Are your customers reporting increasing numbers of bugs?
- Are you spending more and more hours on testing your product?
Did you know that the Consortium for IT Software Quality estimated that Technical Debt cost the software industry £2.84 Trillion in 2018?
Recognising the root cause of a problem is the first step to solving it.
This course will arm you with the information you need to recognise technical debt in your software development organisation, and know where to start looking for it.
Find out what technical debt means and why you need to care
You get a course of 10 video lessons on Udemy that takes you from zero to Technical Debt Detective, containing 55 minutes of videos, with downloadable transcripts, real world case studies and activities to enable you to make a difference in your own company.
Find out the hidden reasons your development projects are taking longer and longer
- Know what technical debt means
- be able to explain to non technical people in your company what the term technical debt means in the software industry and how it impacts on the entire software company
- Be able to recognise the symptoms of technical debt in your own workplace
- Know whether Technical Debt has become a problem that is affecting your ability to meet your customers needs or hampering your growth in the market
- Know the four most common places to look for technical debt
- know where to look for technical debt in your software company, and some of the reasons it arises.
- Feel confident discussing the impact of technical debt with your development team, and 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
- Real world case studies bring the problems alive and help you relate them to your own situation. Learning from others’ mistakes is the least painful way to learn.
Identify the common symptoms of technical debt
Course Contents
Section 1 - What is Technical Debt and how do I know it when I see it?
Introduction
This lesson 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.
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 - 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
Section 2 - Where to look for technical debt?
Introduction
In this lesson 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.
Technical debt in code
In this lesson we take a closer look at technical debt within software code and some of the reasons it arises.
Technical debt in software architecture
In this lesson we take a closer look at how the overall software architecture can result in technical debt.
Technical debt in the underlying technology
In this lesson we take a closer look at how the overall software architecture can result in technical debt.
Social technical debt
In this lesson we will take a look at some non-technical causes of technical debt!
Course Summary
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.
Helen Abell
What you will get from this course
Armed with this knowledge you will be able to assess where your company is on the timeline, and make informed decisions on when and how much of development resource you need to allocate to paying down your technical debt to avoid more serious problems down the line.
Once you start to see the invisible mountain of technical debt your team are climbing, you will be better able to negotiate for the resources you need to scale the mountain and start paying off your technical debt instead of racking up more and more interest without knowing where it is coming from.