3 ms·
If you read the manifesto it asserts that estimates are impossible to make. It's the difference between being unable to produce an estimate and refusing to pro
by bjourne 10y ago
If you read the manifesto it asserts that estimates are impossible to make. It's the difference between being unable to produce an estimate and refusing to produce one. I don't think the manifesto is very good, but it doesn't encourage subordination afaict.
- dahart 10y agoYou're right on the surface, in the literal sense, the manifesto is not directly saying engineers should disagree with managers. But, unless management wants to get rid of estimates and deadlines, it is advocating an antagonistic belief system. It is insubordinate and will cause people to act insubordinately merely to believe that estimates should be avoided at all cost, and that contact between engineers and managers should be minimized and not done on a regularly scheduled basis. Managers can't do their jobs if engineers believe those things. Programmers can't either, some of them just don't know it yet. You can't succeed as an engineer if you can't produce work on a deadline, and estimate and budget your time to meet the company schedule. Accepting that, and understanding why estimates and deadlines and scheduled communication are important to your manager and to the company, and learning how to better facilitate and participate in those activities will make you a better, more valuable engineer.
- discordianfish 10y ago> But, unless management wants to get rid of estimates and deadlines, it is advocating an antagonistic belief system. I agree that 'at all cost' doesn't seem reasonable. Yet I think they should try very hard to avoid them. Estimates, meeting and deadlines might be required some time. You might had to announce a release date for some new features. That's a deadline you can't always avoid. But you can avoid arbitrary deadlines that are just there to 'motivate' engineers and get them to ship "something". That leads to worse quality and technical debt decreasing overall productivity on the long term.
- bjourne 10y ago> You're right on the surface, in the literal sense I have a feeling that whoever wrote that manifest prefers if it is read literally. ;) I guess that is the heart of the issue, isn't it? The author thinks it would be better if companies adapted to how engineers prefer to work over engineers adapting to how companies prefer to work.
- lisivka 10y agoEstimates are easy to produce, but management wants commitment. For example, if I estimated a task to be 2w and management confirmed that, then after two weeks management will start to be angry at me if I will report that task will need 3x time to finish. 3x error is not uncommon for estimates. If I will avoid estimates, then manager will talk something like "try this task for 3 days and if it will require more than 3w to finish, then skip it, because we will not meet the deadline", which is better way to communicate.
- jon-wood 10y agoYour second option of trying something for a while and then saying if it will take more than 3 weeks to finish is still estimating. I don't disagree that it'll result in a far more reliable estimate as you've had time to really feel out the problem and get an idea of what's really involved, but at the end of it you're still giving an estimate of less than three weeks. I think many people's aversion to estimates comes from a culture like the one you're describing in your first option, one where developers are asked for estimates but they're taken as hard commitments. The solution to that sort of culture is exactly the opposite of the one being proposed in this manifesto - instead of siloing ourselves away further and avoiding contact, we should communicate more. (Good) managers don't get angry at a 2 week task taking 6 weeks, they get angry at finding out that the 2 week task will take 6 weeks only after we hit the point at which they were expecting everything to be done. With a little intuition we can tell that a task is going to miss its deadline long before that deadline hits - presumably we've broken things down into smaller sub-tasks, if we haven't completed 25% of those when you're about 25% of the way in, we're going to miss our deadline. The typical developer has a tendency to convince themselves they'll catch up later on, I certainly do, but in all likelihood we won't. That 25% point is the time to sit down with the manager and talk things over. Bring options, make it clear that if the deadline matters that much some features might have to be dropped, or released later. Or maybe the deadline doesn't matter, but they'll need to rearrange things so that another person is working on a feature which has a deadline 6 weeks out. I get how appealing the proposal to just do away with deadlines, meetings, and regular updates can be, but that's only practical in an organisation entirely staffed by developers without any outside influences. Those influences will include all sorts of things, from investors to the season (woe betide the retailer who didn't bother estimating how long functionality to handle Christmas orders was going to take and released it on the 26th of December because that's when it was done). In the real world you're not building features in isolation so we need a way to communicate to others what they should expect, and when they should expect it.