in conjunction with ICSE 2013
Most successful software development organizations accumulate at least some "technical debt"--shortcuts that were expedient at the time they were taken, but that create an ongoing maintenance obligation that slows future progress. Why does this always happen, and can it be avoided? When does it make sense to take on debt, and when should debt be avoided? Is all technical debt equal, or is some worse than others? How much debt is too much? And how do you get out of debt? Steve McConnell, the award winning author of Code Complete and Software Estimation addresses these questions and more in this cutting-edge technical presentation.
Steve McConnell is CEO and Chief Software Engineer at Construx Software. Steve is the author of Software Estimation: Demystifying the Black Art (2006), Code Complete (1993, 2004), Rapid Development (1996), Software Project Survival Guide (1998), and Professional Software Development (2004). His first two books won Software Development magazine's Jolt Excellence award for best programming books of their years.
Steve has worked in the software industry since 1984 and has expertise in software estimation, project management, executive leadership, and software construction practices. In 1998, readers of Software Development magazine named Steve one of the three most influential people in the software industry along with Bill Gates and Linus Torvalds.
Steve has served on the Panel of Experts that advises the Software Engineering Body of Knowledge (SWEBOK) project and served as Chair of the IEEE Computer Society's Professional Practices Committee. Steve served as Editor in Chief of IEEE Software magazine from 1998-2002.
Welcome and workshop theme
Use of the metaphor and related techniques in practice
Tool support for managing technical debt
Technical debt landscape and perspectives of technical debt in the software development lifecycle
Dependency analysis techniques to manage debt
Practical implications, tools, and techniques
Invited Speaker: Steve McConnell
Economic modeling of technical debt
Economic implications and research directions
We plan to have a dinner the evening of the workshop to facilitate closer links among the participants.