Abstract: Do you have that piece of code that grows bugs every time you try to change it? Yet, do you find it difficult to fund a repair? Fixing it will take a project, and that one just never makes it to the top of the queue. Or do you spend a lot of time finding others' bugs? Or do others around you always take the safe path, even when there's a better option? Do you get interrupted every sprint by a couple bugs, and so miss the sprint goal?
Safeguarding addresses all of these and more.
Safeguarding is a simple, 22-minute practice that allows you to find, fund, and then execute real changes to your process and product. Fix technical debt this sprint. And next sprint. And the one after. Without slipping features. Fix process debt. Fix psychological safety issues.
In this workshop, you will safeguard a real problem that you are experiencing right now. You'll learn how to facilitate yourself and your team through safeguarding. And you'll learn how to sell this practice to your product owners and managers.
My goal is simple: I want you to go home after the conference and start actually fixing technical debt, start actually preventing bugs. By this time next year, I want you to have less than 5% of your current number of bugs.
Learning Outcomes: - Can define good remediations, on the basis of a bug, to prevent future bugs.
- Understand hazards and know how to look for them.
- Understand when to safeguard to get the best results.
- Ready to start safeguarding when they get home.
