2 ms·
IMHO, the problem is that we as an industry don't seem to accept that tasks estimates are wrong most of the time. Because it's hard to estimate, and because man
by palata 3y ago
IMHO, the problem is that we as an industry don't seem to accept that tasks estimates are wrong most of the time. Because it's hard to estimate, and because managers don't believe developers. Also managers have an incentive to give unreasonable deadlines to developers (developers under pressure are admittedly faster, but not necessarily making a good job), and developers have an incentive to write quick hacks to make their managers happy.
There are methods that work and that don't require institutionalized estimation-bullshit. For instance:
- You write a mobile app for a customer. Discuss the requirement with them, say what is "easy" and what is "much harder than they imagine" (they probably don't want that, it's orders of magnitudes more expensive than they expect). Then work hard on limiting the scope of the project with the customer and start working. Meet every 2 weeks with the customer, show the progress and get paid. Decide the next step with the customer and go for another 2 weeks. This is the closest I can imagine to the typical Agile cults, except that it doesn't involve estimation dances ("Fibonacci points or T-shirt sizes?") and all the "velocity" crap.
- You need to write bigger software than a small app. In that case, just build it slowly, and start selling it when it is ready instead of selling promises based on estimates (again: estimates are wrong). Estimates here lead to over-promising, then there is no need to design the software properly, everyone makes hacks and rushes and makes a bad job.