10 ms·
> It's enormously frustrating to be on the other side of the table, and to have a recalcitrant development team missing estimate after estimate, sometimes by or
by fooqux 2y ago
> It's enormously frustrating to be on the other side of the table, and to have a recalcitrant development team missing estimate after estimate, sometimes by orders of magnitude.
I know this is just my anecdotal experience versus yours, but every time this has been the case for me in my life, it's due to dates being told to the developers instead of the other way around. Sometimes it's blatant "we need to hit this date because of the market / end of quarter" and sometimes it's passive aggressive such as "management didn't feel your date matched expectations, try again" and it gets sent back for another estimate which will now be biased.
I've also been on both sides of the table, and I'm glad I was a developer first and had those experiences. I already knew that humans can't estimate large things accurately, and that was one of the great takeaways from scrum: do smaller batches and estimate those to get more accurate numbers.
- Tomte 2y ago> Sometimes it's blatant "we need to hit this date because of the market / end of quarter" You know what‘s blatant? "Deadline is MM-DD, and it’s non-negotiable, because that‘s the birthday of the boss‘s deceased husband". Been there, suffered that. All important projects had that deadline, year after year, when they were so unlucky to have their projected end dates somewhere around that part of the year.
- ivan_gammel 2y agoI worked on a project once, where the date was written in the law (financial compliance). Sometimes we have to accept and deal with the deadlines and the problem becomes the problem of quality and scope. In such situations you just throw away some of the best practices and just ships whatever works. Business is often totally fine with imperfections.