This document discusses technical debt governance and developer demos. It contains information about degrading velocity over time spent implementing features versus time spent on debt repayment. Charts show the effects of debt on productivity. The document also lists governance roles and mentions analyzing code with SonarQube and using pull requests to prevent debt. Demo topics are listed as the idea, experience with SonarQube, and its roadmap.

2. Technical Debt
Governance/Developer Demos

3. rik.van.den.berg@centric.eu
@rik_vanden_berg

5. -50
-40
-30
-20
-10
0
10
20
30
S1 S2 S3 S4 S5 S6 S7 S8 S9 S10 S11 S12
Degrading Velocity
Productive time spent on implementing features
Interest/repayment = extra time spent on implementing features or payment of debt
Debt = effort required to cleanup or refactor code

6. Developer

7. Dev Lead

8. Development Manager

9. CTO or Offshore (Romania)

19. Open Source with Paid offering
Plugins

20. 1. Analyze your code using SonarQUbe
2. Governance for the developer, Visual Studio
3. Governance, Visual Studio and SonarQube
4. Using Pull Requests to prevent the leak

21. The Idea
The Experience
SonarQube Roadmap