3 ms·
It gets interesting when a company assigns 2 story points to a task that requires 6 minimum. No time for writing tests, barely any time to perform code reviews
by cynicalsecurity 10mo ago
It gets interesting when a company assigns 2 story points to a task that requires 6 minimum. No time for writing tests, barely any time to perform code reviews and QA. Also, next year the company tells you since we have AI now, all tickets must be done 2 times quicker.
Who popped this balloon? I know I need to change my employer, but it's not so easy. And I'm not sure another employer is going to be any better.
- roryirvine 10mo agoAre you not involved in doing the estimation?
- asadotzler 10mo agoinvolved in is meaningless. if 10 people at a table all offer their inputs, it doesn't matter if mine is the rational one, or even if I hedged against their irrationality with an inflated estimate, the 9 other estimates will dominate. That's the whole problem here, a lack of autonomy and a lack of expectations for responsibility. Make the developer responsible for the estimate, and hold them accountable for the results. Letting the organization make the estimate and then blaming an LLM for the failure is a recipe for company collapse.
- theshrike79 10mo agoMe: "Boss, this takes at least 4 weeks to complete properly including QA time." Boss: sucks in air through his teeth "Best I can do is one week. Get to it." Me, with a massive mortgage and the job market is shit: "Rogerroger, bossman"
- mystifyingpoi 10mo agoClassic butchering of otherwise decent Scrum idea. If assigning 2 points means no tests, then you are already using story points wrong, and complaining about it is meaningless.