Technical Debt is widely regarded as a bad thing that should be paid back as soon as possible, however it can be a strategy that helps balance short-term wins and long-term productivity. The article describes different ways that a project could pay back Technical Debt and what factors must be considered when deciding if you should repay, convert debt or just pay the interest.
Historical data is a key resource for judging the effectiveness of software process improvement methods and also for calibrating software estimation accuracy. In this article, Capers Jones compares Agile and Scrum with a sample of contemporary software development methods using several standard metrics.
In the wake of the latest product announcement from IBM, InfoQ talked to Bertrand Portier about a RedBook that presents a Model-Driven-Development approach to service construction. The concepts are general enough to be applied to product stacks other than IBM.