The document discusses technical debt in software projects, including examples of different types of technical debt, how much debt a project can handle before reaching "technical bankruptcy", and strategies for dealing with technical debt such as acknowledging it, tracking it, avoiding new debt, refining what constitutes "done", and empowering teams. It also introduces the presenters, Maria Matarelli and Collin Fagan, and provides contact information.

2. Agenda
 What is Technical Debt
 Real World Examples
 How much Debt can a Project Handle
 Technical Bankruptcy
 How to deal with Technical Debt

3. Maria Matarelli
@MariaMatarelli
Meet the Presenters
Collin Fagan
#Agile2013

22. Technical
Debt
Implementation
Architectural
Testing
Deployment
Information/
Knowledge

30. DONEDevelopment
Unit Testing
Appropriate
Documentation
Functional
Testing
Code Review
Deployment

37.  Acknowledge your debt
 Track it
 Deal with what you already have - Pay it now!
 Avoid it

38.  Refine definition of “DONE”
 Discuss the consequences of “Good Enough”
 Negotiate Scope, not quality
 Empower teams to succeed, not just deliver
 Understand your complexity budget
 Build „T‟ shaped skills by cross training

41. Contact Us
Maria Matarelli http://www.bevilledge.com
Maria.Matarelli@BevillEdge.com
@MariaMatarelli
www.linkedin.com/in/mariamatarelli
Collin Fagan
Collin.Fagan@nokia.com
www.linkedin.com/in/collinfagan