BT

Deliver Shippable Products with Good Engineering Practices

by Ben Linders on  Aug 25, 2016

Good engineering practices are the tools that help agile teams to deliver shippable products. Although many engineering practices have proved to be effective, they are not as widely used as they should be. Agile anti-patterns like the software testing ice-cream cone, accumulating technical debt and functional silos prevent teams from delivering a potentially releasable product.

Technical Debt and Team Morale when Maintaining a Large System

by Ben Linders on  Jan 26, 2016

Thomas Bradford talked about his experience with maintaining a monolith Java based system with zero test coverage and large technical debt at the Agile Testing Days 2015. InfoQ interviewed him about the problems that they had maintaining the system and the technical debt that had been build up, why they decided to take a different approach and how they improved team morale.

Measure and Improve Code Quality

by Ben Linders on  Jan 11, 2016

InfoQ interviewed Boris Modylevsky about the importance of measuring code quality and how measurements can be used to improve quality, integrating static code analysis in continuous integration, testing coverage and test automation, and the benefits that continuous integration with integrated code analysis and test coverage can bring.

Managing Technical Debt Using Total Cost of Ownership

by Ben Linders on  Jun 03, 2015

Total Cost of Ownership (TCO) can be used for investment decisions and financial benefit analysis. When applied to software it covers the initial development costs and subsequent maintenance costs until phase out of a product. TCO can support architectural decisions and management of technical debt.

Addressing Organizational Debt

by Savita Pahuja on  May 25, 2015

Steve Blank,talks about the organizational debt which is similar to technical debt. He says that growing companies need to understand how to recognize and refactor the organizational debt.

Is Unhedged Call Options a Better Metaphor for Bad Code?

by Ben Linders on  Dec 24, 2014

In a blog post on bad code and technical debt Steve Freeman described how Chris Matts came up with the metaphor of an unhedged call option for bad code. This post is being intensively discussed on Reddit and on Hacker News recently. InfoQ interviewed Steve and Chris about using metaphors for bad code and code smells, trade-offs and costs of low quality code, and responsibilities for code quality.

Designing Systems for Testability

by Ben Linders on  Oct 22, 2014

Testability must be explicitly designed in the system said Peter Zimmerer from Siemens AG. Test architects should drive testability and collaborate with architects, designers and testers in using good design and engineering practices. At the QA&Test 2014 conference Peter gave a tutorial about design for testability for embedded software systems.

Advice on When to Repay Technical Debt

by Rafiq Gemmail on  Dec 11, 2013

An exploration of recent advice from Henrik Knibert, Ward Cunningham and Hayim Makabee on technical debt, how to make the most of it and when to pay it off.

Rocket to Mars: A Sprint Planning Game

by Ben Linders on  Dec 11, 2013 7

“Many team and their product owners believe that the team's unique job is to deliver more and more story points, but we consider this to be a complete misunderstanding of the relation between the team and the product owner” said Damien Thouvenin and Pierrick Revol. They ran a sprint planning game on investing time to produce stories, investigate issues, reduce technical debt, or do training.

Should You Create User Stories for Technical Debt?

by Ben Linders on  Mar 21, 2013 15

Agile teams sometimes struggle with the planning of pure technical tasks that have no direct value for the user of a system, but have to be done to deliver working software. Should you create user stories to handle such technical tasks and technical debt, or not?

XP Days Benelux 2012, second day sessions

by Ben Linders on  Nov 30, 2012

The 10th anniversary edition of the XP Days Benelux 2012 conference continues on the second day. An impression of the sessions about agile adoption, self organizing and managing technical debt.

Technical Debt Is Now Costing Us $3.61 Per Line Of Code

by Christopher Goldsbury on  Feb 27, 2012 10

According to a report by CAST Software, technical debt now costs a company on average $3.61 per line of code. The report's findings are summarized in this article and more discussion is presented from other thought leaders on the topic.

Is Technical Debt Still a Useful Metaphor?

by Amr Elssamadisy on  Jul 11, 2011 9

A discussion has been taking place on the LinkedIn Agile Alliance group questioning if "technical debt" is still a valid metaphor in today's global software development world. This discussion has surfaced a strong support for the effectiveness of the metaphor even after 20 years.

How To Pay Down Technical Debt

by Dan Puckett on  Dec 06, 2010 4

Technical debt can be difficult to connect directly to customer value, but delivering customer value is what Agile processes are all about. So how can we track and reduce technical debt in an Agile development environment?

Is Technical Debt a Technical Issue?

by Amr Elssamadisy on  Jan 19, 2010 5

Is technical debt a purely technical issue that can be addressed directly by refactoring and tests or is it a symptom of a bigger problem? Will the adoption of TDD fix the issue or just cover up a symptom of something bigger?

General Feedback
Bugs
Advertising
Editorial
Marketing
InfoQ.com and all content copyright © 2006-2016 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT

We notice you’re using an ad blocker

We understand why you use ad blockers. However to keep InfoQ free we need your support. InfoQ will not provide your data to third parties without individual opt-in consent. We only work with advertisers relevant to our readers. Please consider whitelisting us.