The document discusses various stories about successfully and unsuccessfully managing technical debt. It describes situations where technical debt was incurred such as a junior developer learning poor practices, rushed development leading to shortcuts, and refactoring without communication. It also provides positive examples where technical debt was identified and reduced through teamwork, prioritization, and linking it to business goals. The document warns about potential "evil" team members and product owners who try to avoid technical debt and provides suggestions for managing it properly through open communication, code reviews, and continual improvement.
2. “Technical debt is a concept in software development that reflects the
implied cost of additional rework caused by choosing an easy solution
now instead of using a better approach that would take longer.” - Wikipedia
Antonio Cobo @Mind_of_AC
3. “Technical debt is a concept in software development that reflects the
implied cost of additional rework caused by choosing an easy solution
now instead of using a better approach that would take longer.” - Wikipedia
Antonio Cobo @Mind_of_AC
9. Antonio Cobo @Mind_of_AC
What’s the accent?
By Box Repsol | Flickr - https://www.flickr.com/photos/box_repsol/26877535660/,
CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=53803565
By si.robi - Nadal US16 (43), CC BY-SA 2.0, https://commons.wikimedia.org/w/index.php?curid=52043937
26. Antonio Cobo @Mind_of_AC
Situation:
• Junior Developer
• Big company
• “Senior” Developer with no real experience
• Fixed Price contract
• Save as much money as you can mentality
33. Antonio Cobo @Mind_of_AC
Bad team work
Not teaching good practices
Not making the junior developer to think
If the original class used as a model is poorly written
34. Antonio Cobo @Mind_of_AC
Bad team work
Not teaching good practices
Not making the junior developer to think
If the original class used as a model is poorly written
35. Antonio Cobo @Mind_of_AC
Bad team work
Not teaching good practices
Not making the junior developer to think
If the original class used as a model is poorly written
37. Antonio Cobo @Mind_of_AC
Situation:
• Extremely optimistic deadline
• Development manager asked to be “hands on”
• We MUST deliver something tomorrow
• After helping the team, it’s late and DM is alone
48. Antonio Cobo @Mind_of_AC
Situation:
• Developer finding Tech Debt
• Willing to correct it
• Refactoring a small part…
• becoming bigger and bigger and bigger…
• Without telling anyone
58. Antonio Cobo @Mind_of_AC
Situation:
• Seven senior developers + PO
• Long term product development
• Some intermediate tight deadlines
• Second retrospective and Tech Debt is here!
89. Antonio Cobo @Mind_of_AC
“Improve how we handle DB concurrent connections”
As a Head of Product
I want to enable special sales events in our website (ie. Black Friday)
so that we can increase our revenue
90. Antonio Cobo @Mind_of_AC
“Improve how we handle DB concurrent connections”
As a Head of Product
I want to enable special sales events in our website (ie. Black Friday)
so that we can increase our revenue