Ultimately, the goal of this session is to give you the tools to better deal with technical debt. Rather than blaming individual developers, you will be able to show the systemic sources of technical debt, and assess the relative value of addressing each of them. Rather than depending on technical measures to convey the costs of technical debt, we will help you to put the costs of technical debt in stark business terms.
I help organizations build valuable software. Period.
He has sixteen years' experience as a software developer, team lead, consultant, and coach on many organizations. Since founding derailleur consulting, his focus has been on how to make good teams and organizations great, and great ones better, through the application of lean, agile, and systems thinking.
Through this, he has worked with organizations from the very small to the very large, across an array of industries and occupations, helping their people uncover ways to understand their organization's systems and how to improve them.
Chris is actively involved in the local and extended agile community, and has spoken at conferences across Canada where he likes to engage participants with live, hands-on demonstrations to help explain the theories of W.E. Deming, Eli Goldratt, and others, and how they can use them in their work.You can find Chris on @DerailleurAgile or local agile events around GTA.