"Are you willing to own the risk? If so, what will it look like? Can you budget additional time for addressing these bugs, and draft contingency plans?"

[–] Diplomjodler3@lemmy.world 8 points 12 hours ago* (last edited 12 hours ago)

*Sticks fingers in ears* Can't hear you!

[–] Bazoogle@lemmy.world 5 points 7 hours ago

"You're overthinking it" - real response from my management

[–] IcyToes@sh.itjust.works 5 points 12 hours ago (1 children)

"I only know 1 (credible) way to build it. I'll take x days. I'll go right ahead with that."

[–] Diplomjodler3@lemmy.world 4 points 12 hours ago (1 children)

We need it yesterday! Just get it done!

[–] IcyToes@sh.itjust.works 3 points 10 hours ago* (last edited 10 hours ago)

"Why are we only learning about this now? How long has this requirement been known? I think we need to look into the process that work comes into the team otherwise, if we don't learn, we are going to take the website down and cost the company thousands/millions. It's worth working with the business to get a batter understanding of upcoming requirements so we know what's going to be needed in a months time". There is a reason retros exist. Oh, and you have to be good at teasing out real deadlines vs arbitrary deadlines made up with no justifiable reason.

"You ask me how long it'll take, and it's 3 days. You probably need to manage expectations on this. Maybe let them know the risks of x, y and z and why it will take this long".