“We have Greek technical debt”
“We don’t have technical debt here; we have Greek technical debt” - this was a quote from one of our customers when asked about the state of their business platform. In the recent past we’ve seen the problems caused by failing IT systems bringing some very big names into the public eye in the worst of ways.
Modern software development methods have developed practices for refactoring, reengineering and re-architecting existing IT systems in order to increase quality and reduce cost of change and on-going Total Cost of Ownership (TCO). We’re interested in what you think about the trade-off of costs and benefits of reengineering your core business systems in order to mitigate or avoid future risk and costs.
IT systems at the core of business Over the past 2 years we’ve noticed a trend developing, more and more of our conversations with customers and prospects revolve around failing legacy system projects, often sent offshore, where although the system is vital to the business it has, over time, become brittle and buggy and hard to change or extend.
Over the past year the team has worked with a client to help them remediate their failing core business platform. By re-shoring and bringing in a mix of in-house and nearby partnered development a project that had thousands of open bugs, three-month deployment cycles, a minimum of six months for time-to-market for new features, and over a hundred offshore developers was bought back under control. The bug list was reduced by 70%, releases went from 3 monthly and lengthening to 2 weekly and the number of developers on the project went from an unmanageable 150 to 25 who were as productive and better at value creating than the previous larger team.
Strategies for remediating failing IT projects We’re interested in getting feedback on whether information on remediating failing IT systems projects is of interest. We’re working with organisations like yours to collate and analyse data to publish a white paper to be delivered in Q4 this year.
[Click here] if you’d like to contribute to the white paper, you’ll get free access to the anonymised datasets as well as the analysis and we’re keen to recognise relevant co-authorship.
Feedback We’d love to hear from you if you’d like to tell us anything on what we’ve said above, or would like to talk with us about your IT project needs.
[Click here] f you’d like us to call you back at a time of your convenience, or simply to leave some feedback.