Here’s a big secret that people don’t want you to know. If nobody is able to give you clarity about the scope and scale of a request, sometimes that means you get to decide. It’s really cool when that happens. Don’t waste it. https://soc.jrconlin.com/@jrconlin/112374476337793296
@polotek@jrconlin You are correct, and the thing to do is try and constrain the scope to “one point”. There will be fixes that are smaller, there will be things that blow up due to unknown unknowns but on average, every chunk of value you deliver will be “one point” (in practice something like 2-3 “ideal engineering days”.) If you build a reputation for delivering on this cadence that’s how you gain trust, including forbearance when things go south.
Add comment