Start the New Year Guilt Free
Technical debt is a concept in software development that reflect ‘s the implied cost of additional rework caused by choosing and easy solution now instead of using a better approach that would take longer. (Wikipedia)
Here’s the summary of the attached presentation with Video.
❖ Definition – Examples
❖ Inventory technique — Trello example
❖ Next: When to work on technical debt
❖ Using Flow to help — What does automation have to do with debt clearing?
❖ Governance Documentation
❖ How big are we? — A dashboard to shows your org “size” over time
❖ System Tools to help assess debt
You can download the presentation below