Technical Debt

920 views

Published on

This presentation was prepared for a Scrum Team to inform them about the problems of technical debt - (un)done stories - and define with them in this session a Defintion of Done (DoD).

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
920
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Technical Debt

  1. 1. TECHNICAL<br />DEBT<br />
  2. 2. Undone!<br />Done!<br />
  3. 3. Pay menow<br />Pay melater<br />or<br />
  4. 4. Review<br />Review<br />Review<br />Plan<br />Plan<br />Plan<br />Plan<br />Stabilization<br />Undone<br />Undone<br />Undone<br />
  5. 5. Backlog<br />Time<br />
  6. 6. Backlog<br />Time<br />Undone<br />
  7. 7. mean?<br />DONE<br />What<br />does<br />
  8. 8. Code complete & reviewed,Unit test passed, Integration tested,Refactored, Acceptance tested,Accepted by QA, Documented, Integrated, Deployed, <br />Bugs closed, Regression tested, <br />No work around, Item after <br />Item, Accepted by PO,<br />…<br />DoD EXAMPLES<br />
  9. 9. So, you all agree<br />withourDoD?<br />NO<br />YES<br />
  10. 10.
  11. 11. www.projekt-log.de<br />

×