3 ms·
Why optimize for this? Some of the worst jobs I’ve had were the ones where a PM would say “drop whatever sprint items you’re working on and immediately context
by KMnO4 2y ago
Why optimize for this? Some of the worst jobs I’ve had were the ones where a PM would say “drop whatever sprint items you’re working on and immediately context switch to this bug”. Sounds like this is their regular day? And what happens if a bug comes in Friday @ 4pm?
- celdon25 2y agoOn-call rotations are pretty common in the industry, I don't see any mention in the article of the entire team being on-call 24/7.
- Lutger 2y agoIt's implicit but clear from the article they have thought about this. There's an owner responsible for triage and communication on the incoming reports, and somebody responsible for bugfixing, presumably they have some roster where after so many days they switch duty. This limits the context switching to only one (or two) persons at a time. It also sounds they are trying to make everything work in office hours, so when a bug comes in friday afternoon it'll get fixed on monday. From the article it sounds like a completely different game than what you mention, which I also experienced at times.
- ebiester 2y agoThis is a function of priority: it is saying that existing features working perfectly are more important than new features. It also should come with a culture of treating bugs like you do a production incident: You do retrospectives and figure out what you can change to your process to reduce the likelihood of the same type of bug happening again. You likely also have a more extensive suite of tests to prevent regressions.