This is the official site of the SQALE method


The SQALE Definition Document has been downloaded over 10,000 times!

By on oct 02nd, 2014, no comment

The SQALE method just passed an important milestone. Indeed, since the launch of the method on the site in August 2010, over 10,000 people have downloaded the definition document. This is quite impressive in regards of the technical (and tedious) nature of the document. Of the 22,000 site visitors, nearly half of them have [...]

Read the rest

The SQALE Debt Map: How to use it

By Jean-Louis Letouzey on juil 15th, 2014, no comment

I previously explained the use of the SQALE Pyramid here . I will explain here how to use the Debt Map indicator. We can produce this indicator at 2 levels: • The first level is the Project level. In this case each point of the map is a file. • The second level is the [...]

Read the rest

The SQALE Pyramid: A powerful indicator

By Jean-Louis Letouzey on déc 12th, 2013, no comment

Meaningful insights into your Technical Debt The SQALE Pyramid is certainly the most useful indicator of the SQALE method. It gives a lot of information on the nature of the technical debt and thus helps to make decisions. I will try to show how it helps to answer questions that often arise once you have [...]

Read the rest

Testability is the mother of ability

By Jean-Louis Letouzey on déc 02nd, 2012, no comment

Among the particularities of the SQALE method, there is one whose importance is not always well understood. I’ll try to explain it in this post. The SQALE Quality Model identifies quality characteristics and put them in a chronological order. It appears that the first one at the bottom is Testability. This means that even before [...]

Read the rest

Why managers like the Technical Debt concept

By Jean-Louis Letouzey on sept 21st, 2012, no comment

Since its introduction by Ward Cunningham, the concept of technical debt is quite well recognized and used more and more by project managers to monitor their project. What is quite surprising (and also beneficial) is the fact that this quite technical concept is also used and supported by middle and upper managers. I have already [...]

Read the rest

How agile is your code?

By Jean-Louis Letouzey on août 29th, 2012, no comment

It is sometimes necessary to change the maintenance mode of a legacy application and switch it to an agile mode. In this case, we must ask ourselves whether the source code of the project in question does not contain too much technical debt inherited from years of maintenance. If the inherited debt is too high, [...]

Read the rest

Obsolescence and Technical Debt

By Jean-Louis Letouzey on avr 26th, 2012, no comment

I have read many blogs and articles on Technical Debt. I also participated in exciting events on the topic. They are at least 2 major and positive messages that are always raised: The code quality is very important and all projects, all organisations should monitor it. The Technical Debt metaphor is a simple but smart [...]

Read the rest

What “Managing Technical Debt” means?

By Jean-Louis Letouzey on mar 07th, 2012, no comment

Estimating the value of the Technical Debt of a project is not enough to be able to manage it. When you have estimated the value of your debt, you’ve just made a first step. You know where you are but it does not help you decide where to go and how to get there. I [...]

Read the rest

A new version of the SQALE method is on line

By Jean-Louis Letouzey on fév 13th, 2012, no comment

The Version 1-0 of the SQALE Definition Document has just been released. As announced in a previous blog entry (here), this version of the method introduces and support the new concept of “Non-Remediation Cost”. This is for quantifying what will happen if a non-conformity is not corrected. I would like to clarify and explain what [...]

Read the rest

Technical Debt and Business perspective

By Jean-Louis Letouzey on jan 27th, 2012, no comment

A new concept: Non-Remediation Cost The current version of the SQALE Method Definition Document supports and helps to manage the Technical Debt of an application/project. The new version of the method (which will be publicly released soon) will continue to use the debt metaphor and help you to manage two concepts: •    The Technical Debt, [...]

Read the rest