The Programmers Who Want To Get Rid of Software Estimates
An anonymous reader writes: This article has a look inside the #NoEstimates movement, which wants to rid the software world of time estimates for projects. Programmers argue that estimates are wrong too often and a waste of time. Other stakeholders believe they need those estimates to plan and to keep programmers accountable. Is there a middle ground? Quoting: "Software project estimates are too often wrong, and the more time we throw at making them, the more we steal from the real work of building software. Also: Managers have a habit of treating developers' back-of-the-envelope estimates as contractual deadlines, then freaking out when they're missed. And wait, there's more: Developers, terrified by that prospect, put more and more energy into obsessive trips down estimation rabbit-holes. Estimation becomes a form of "yak-shaving" — a ritual enacted to put off actual work."
Good managers get my best guess.
Bad managers get my worst case.
Horrible managers get my resignation.
Tag: WORKS4ME
Live today, because you never know what tomorrow brings
so, estimating time is a waste of time, but complaining about estimating time is not?
GET BACK TO WORK, MONKEY.
WHY CAN'T WE HAVE BLANK CHECKS
I thought this was funny, but it probably isn't - especially now that I have typed in all lowercase words to get pass the yell filter.
If you penalize me for going over time and budget, my next estimate is 30 eons and 200 trillion USD.
Watch me come in well inside the budget.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Peter Molyneux is that you?
Lets see... What would they say? This is the one-sided conversation, since it doesn't matter what you say anyways.
"Ok, we can accept that estimate."
"Ya, ya, ya, whatever."
"We'll have that information to you by the start of the project."
"The information isn't ready yet, we'll have that by the time you need it."
"I thought we had that to you already. We'll have to check with the information source."
"The PMs have some changes."
"Here's the information, but there are some small changes."
"No, those are small changes, they won't impact the timeline."
"No, you can't have more time, we already made commitments."
"The PMs have some changes."
"What do you mean you won't have it in on schedule? You agreed with the initial estimate."
"You're going to stay here until it's done, I don't care how long it takes."
"I don't care that you've been in the office 30 hours straight, this is your fault."
"We're hiring an off-shore company to help you with the project. Get them up to speed."
"The PMs have some changes."
"Since we have the off-shore team, we need to cut your department back."
"I read an article saying Java is the future. Redo it in Java."
"What do you mean we're waiting on the off-shore company?"
"We fired the off-shore company. You're good, you can get it done in time."
"Ok, hire more people into your department, but we're only offering half the salary, and no more bodies."
"Why is this project so far behind? Don't you know what you're doing?"
"The PMs have these changes."
"Why aren't you done? We're weeks from the deadline!"
"You didn't meet the deadline. Don't you know deadlines are firm. We have commitments."
"I don't want excuses, I want results."
"You and your idiot team are fired. Get out of my building."
[2 months later]
"We need you to come back and finish the project. We need it by next Monday, that should be plenty of time."
"Here's all the new specs. They should be easy to do."
"What do you mean total rewrite, it's only a few chances. You are an idiot. Get out."
[1 month later]
"We need you to come back and finish the project. We need it by" {click}
"We need you to come back and finish the project. We need it by" {click}
"We need you to come back and finish the project. We need it by" {click}
"Why do you keep hanging up on me?" {click}
Serious? Seriousness is well above my pay grade.