👋 Hi - this is Gergely and Elin from The Pragmatic Engineer.
We're researching KTLO and bug management and collecting practices that work well – and not so well! The end result will be a report, similar to the one on Organizing and running successful hackathons.
Please reach out to us with examples, strategies, frameworks, mental models and stories – good or bad! – on either of these channels:
- Direct message: send a message on LinkedIn to Elin (you can message her even if you are not a mutual contact) or on X (who is leading this research)
- Email us at ktlo-research@pragmaticengineer.com
- Form: please fill out this Google Form
We aim to share interesting practices in a summary article. We will not share anything you message us with without you reviewing it.
KTLO topics
“Keeping The Lights On” (KTLO) includes any activity that is needed for apps or services to run smoothly day-to-day.
- How does your company make sure to fix bugs as you’re building out your product?
- How do you manage tech debt and build resilient software at your scale-up?
- How does the Big Tech you’re working at organize and prioritize people and time to work on KTLO?
- How have you managed or failed at balancing what needs to be done versus what gets done in different stages of the software development lifecycle?
- How do you communicate the need for KTLO to stakeholders and leadership?
- How do you motivate your teams and people to work on it?
Bug management
- How do you find, identify, and prevent bugs?
- What tooling and workflows do you use?
- What experience do you have with “fixit weeks,” bug squashing sprints, incident teams, goalies, or other approaches to keep on top of problematic areas?