"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".

[–] jjjalljs@ttrpg.network 2 points 8 hours ago

I feel like every retro I've attended has been a farce.

"What went bad? We said doing it this way would be harder and more risk prone. Management insisted we do it that way, and it took longer than and caused a site outage."

"What should we do differently?'

"Listen to the team next time"

"That won't happen"

load more comments (1 replies)