Engineering driven timelines has become a buzz word but I rarely ever see it get practiced fully. Maybe it’s far too utopian of a concept. Every time a sprint team comes up with a LOE , it gets pushed back to be done in half the time and that leads to sub par release quality because of missed scope or just short cuts that don’t scale . Haven’t been able to change this habit in the company despite multiple conversations. What are some tricks or tips managers out there follow and have been successful in making the process more sustainable for ##engineering but meets business expectations? TC: 400k
World Conflicts
Yesterday
445
Why I Find Free Palestine Inspiring
World Conflicts
Yesterday
594
Israeli precision-guided munition likely killed group of children playing foosball in Gaza, weapons experts say
Tech Industry
Yesterday
464
Why does everyone say that Amazon is toxic?
World Conflicts
Yesterday
508
Is "From the River to the Sea" So Wrong?
Personal Finance
Yesterday
1144
Thank you AAPL and NVDA
Move the schedule back
I'm being pretty tongue in cheek with that comment but you're begging the question to a degree. I think you've already outlined how to solve the problem and what's getting in the way so the natural answer is to remove what's getting in the way. You can either add time, cut scope, or reduce quality. These are the main levers available to you (or hidden option is to work extra which unfortunately is the choice a lot of people settle on). You can do more to sell your point, work harder, or just give them the garbage deliverable that they've allocated for. It's up to you what you feel is priority