CAST ha partecipato al 1° Evento Metrico 2015 organizzato dal GUFPI ISMA, associazione di riferimento nazionale per la misurazione del software in Italia, tenuto a Roma lo scorso 14 Maggio.
La conferenza ha visto la partecipazione di Cast sui seguenti 3 topics:
The growing problem of technical debt cannot be overlooked. InfoWorld Editor Eric Knorr recently highlighted the need for technical debt to be paid down, noting, “I wouldn’t be surprised to learn we’re now in the process of accumulating technical debt at historic rates.”
Technical debt is expected to exceed 1.5 million per business application.
As Larry Quinlan, Global CIO, Deloitte Touche Tohmatsu Limited explains, “CIOs need the courage to make the investments that reduce technical debt — and the knowledge and the team to know where and when to make those investments.”
Yet, despite the advances that give IT management proper visibility into the cost and quality of their application development, one issue still remains unresolved: accurate technical debt estimation. The issue resides in how technical debt is calculated and communicated to management.
In this post, we wanted to take a step back and break down exactly what a function point is and how an IT organization can use them to measure application development productivity, improve IT project planning and estimating, and better manage application service providers.
So, you’re ready to get started on building your own multi-language custom source code analyzer platform using open source components. Your return estimates are still looking pretty good, even after taking into account the costs in our previous post, “6 Hidden Costs of Building Your Own Multi-Language Code Analyzer Platform”.
Well, we have a quick list of maintenance costs that you may not have considered. So, before you break ground on that project, see if you thought of all these.
When one of our writers, Lev Lesokhin, started contributing to Wall Street & Technology he was shocked to find very little on the subject of technical debt. Considering how much the concept intersects the worlds of finance and technology, he thought he’d find whole forums of IT guys and financiers exploring the intricacies en mass.
When he realized that was far from the case, he set out to create a guide to bridge the gap and get the conversation started. By taking some of the more complex concepts of technical debt and translating them into financial language, he hoped to bring the technical jargon out of the CIO boardroom and decipher it for a financial audience.