Last week we published a post about the Consortium for IT Software Quality's (CISQ) initiative to come up with a standard technical debt measure through a survey distributed to developers. The technical debt standard will be based on the effort to needed to fix good architectural and coding practices that underlie the quality characteristics of Security, Reliability, Performance Efficiency and Maintainability. The measure will therefore be conveyed as a cost based on effort to solve critical problems.
In order to understand the effort that is put in to fix the software defects part of technical debt, CISQ has published a survey which will provide the data to provide a concrete empirical foundation to measuring technical debt.We invite you to contribute to CISQ's technical debt remediation survey, and the survey will go on until January 20, 2017.
The survey is being collected in PDF form, the form is 19 pages in length and responses to the questions will be anonymous unless otherwise stated by respondents. Submission of the survey can be done by clicking the "Send by email" button at the end of the form or by emailing it to email@example.com.
There are also some perks for respondents for having taken the time to complete the survey:
- The first 50 respondents will receive a $20 Amazon gift card
- One $250 Amazon gift card is being raffled off from the pool of all respondents
- Respondents have the option to be listed as contributors to the Technical Debt specification on CISQ’s website
You can download the survey here.
Erik Oltmans, an Associate Partner from EY, Netherlands, spoke at the Software Intelligence Forum on how the consulting behemoth uses Software Intelligence in its Transaction Advisory services.
Erik describes the changing landscape of M & A. Besides the financial and commercial aspects, PE firms now equally value technical assessments, especially for targets with significant software assets. He goes on to detail how CAST Highlight makes these assessments possible with limited access to the targetâ€™s systems, customized quality metrics, and liability implications of open source components - all three that are critical for an M&A due diligence.