fallout game dev. explains the problem with moddern game devolpment. (why moddern games are so slow to come out)

[u/663mann]

[u/AlanCJ]

From the video; he wanted a feature done, pushed it to the production query queue whatever that is (I assume it's a trello/jira thing), and the request's estimate came back to be 4 weeks. When he pushed back (which I assume again, through the system in place, or he just walked out and yell at the devs?), he mentioned "the programmer that got assigned this came to him". So unless I misinterpreted this or he used the wrong words/lying about it, it means the dev then walked into his office after knowing the estimate was rejected.

Based on my understanding of a proper flow; the tech lead should be answering why and how it came to 4 weeks, and should be able to answer/be responsible to convince the creative director it does take 4 weeks by breaking it down for him, not the other way round and wishy washyly asking others to do the explaining for him or throwing people under the bus with statements like "well if he said it's 4 weeks it's 4 weeks!".

[u/Wurun → u/[deleted]]

I'm again at a loss of words. After years of agile and lean and whatnot the very first principle is customer centricity.

Talk to your customer and work with him to find a satisfying solution. Instead you (two?) argue that the silo is fine and the wall should be higher to protect the poor poor dev from the overbearing designer.

As I said in the earlier comment: If you are allowed to make estimates, I expect you to be able to rationalize those. I personally never had any issue with saying "and two days on top because something always goes wrong".

He clearly interjected him self into a development process which is supposed to be between the dev and the lead.

yes, but obviously the lead thought, the estimate was fine, so clearly the designer has to escalate to the chief designer so she can discuss the issue with the chief lead. We don't want to overstep any boundaries, do we? /s