Skip to main content
Thursday, June 25, 2015 - 10:15am - 11:15am
Test Management

Managing Technical Debt Prior Year Content

Technical debt is slowing your software development projects. Any developer who has gone beyond version 1 has encountered it. Technical debt takes different forms, has many different origins, and does not always equate to bad code quality. Much of it is incurred due to the passage of time and a rapidly evolving business environment. Some is in the form of hundreds of little cuts; some is massive and overwhelming, the result of a single poor design choice. Philippe Kruchten explains how to distinguish different types of technical debt, identify their root causes, objectively assess their impact, and develop strategies suitable in your context to limit or selectively reduce the technical debt you incur. Discover what debt you can happily live with. See when to declare bankruptcy. And learn that not all technical debt is bad. Just like in the real world, some technical debt can be a valuable investment for the future.

Philippe Kruchten
Philippe Kruchten, Kruchten Engineering Services, Ltd.

Philippe Kruchten is professor of software engineering at the University of British Columbia, in Vancouver, Canada, where he holds an NSERC chair in design engineering. He joined UBC in 2004 after a thirty-year career in industry, where he worked mostly with large software-intensive systems design in the domains of telecommunication, defense, aerospace, and transportation. Philippe’s current research interests are in software architecture (in particular, architectural decisions and the decision-making process), the evolution of large software and technical debt, and agile software development practices. He is the founder of Agile Vancouver.

read more