| ▲ | DetroitThrow 3 days ago | ||||||||||||||||||||||||||||||||||
>I love this. I’m going to add your 'Shield & Deliver' path as an alternative (and perhaps superior) winning state. This is exactly the nuance I wanted to surface. I would be wary of this being the superior winning state, but definitely an alternative. I've done exactly this in my career as a tech lead only for it to burn me, and probably 2/3rds of the time the best thing for everyone is to simply "Save the Sprint" and not become mired in discussions that often are for personal empire building that strategic leadership would hate. Maybe people have different experiences than me on this, feel free to speak up! | |||||||||||||||||||||||||||||||||||
| ▲ | pingananth 3 days ago | parent [-] | ||||||||||||||||||||||||||||||||||
This is exactly why management is hard to unit test! You are absolutely right. If you 'Shield & Deliver' every time, you risk becoming the 'Yes Man' who absorbs infinite scope creep for someone's vanity project (Empire Building). The 'Correct' answer actually depends entirely on the Nature of the Request: Legitimate Business Crisis? -> Shield & Deliver Noise/Politics? -> Save the Sprint Distinguishing between the two before you act is the master skill. I think keeping both paths as valid strategies with different 'Trade-off' warnings or having 2 different contexts is the right move to reflect that ambiguity | |||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||