|
Most of my new-feature-development-requests are land on my - virtual - desktop a few weeks after their promised deadlines...
(Bug fixes are a different story as they flow directly from support to me without management intervention)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
...which makes it all bearable 
|
|
|
|
|
Yup that is what usually usually happens.
MD has an idea and decides it can be done by a certain time. The we get down to specifying the requirements.
Just finished telling one of our devs to refactor because of a change of requirement and brought up the "deadline", bah humbug, f*** the deadline just get the job done and get it done right!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Usually My Team complete tasks within the deadline, But sometimes we extend it because of some reasons at that time it is reasonable.
Nirav Prabtani
|
|
|
|
|
Many times it was observed that Requirement slides but deadlines doesn't...There was a true line says "Walking on water and developing software from a specification are easy if both are frozen"
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
PHB: How long will it take you to do something that you've never done before?
DEV: Realistically, we'll be looking at maybe 50 days' dev work - could be a little bit longer, it's hard to say not having seen the 3rd party API as yet.
PHB: Would you care to reconsider that? I've told the board we'll have it by the end of the month.
DEV: It's the 27th of February today.
PHB Blimey! So it is! We'll put it down as one day, then. Don't let this one over-run the way you did with the last one!
Slogans aren't solutions.
|
|
|
|
|
/ravi
|
|
|
|
|
Or sometimes:
MD: How long will this project take that you've never done before?
Me: A few weeks at least...
MD: Pfff, OK.
Me 30 mins later: Well that's done and out of the way. 
|
|
|
|
|
|
A quote from Doug Adams (Hitchhiker's Guide).
(I know the quote in the form "I love deadlines! I like the whooshing sound as they pass by!" - but that doesn't change the main point.)
|
|
|
|
|
Cool, now I also know where it comes from. Thanks!
|
|
|
|
|
often comes another feature or some dependency with other software of my company which kills the deadline.
And sometimes some hidden and weired bug is creeping out of the code in the release tests. 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
t1 = original estimate -> pure fantasy
t2 = t1 * 2 -> painful
t3 = t2 * 2 -> reasonable
t4 = t3 * 2 -> relaxed
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
a= My deadlines are always unachievable fantasies
b= My deadlines are pretty relaxed
c= b/a ~ 3...4 by expirience
were 3 is more on "My deadlines are generally reasonable"
and 4 becomes very relaxed
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Deadlines, for the defined work, are reasonable.
However, when the scope changes and the original deadline is still desired... well, I deliver for the original scope or tell them the timetable is not achievable.
|
|
|
|
|
In recent years, people requested stuff and it happened. If anything slowed it down, it was getting them to test the application(s). That is, until recently.
Some changes at the top - and actual fear in the eyes of some of these new top players - and they imposed threatening deadlines (at least upon one particular application). To this I've already referred The Lounge[^]
No deadlines worked well because the main couple of developers had real work ethics and we like what we do. I'll admit it's kind of a kick to see hundreds of people with their face in your work.
But I was going elsewhere. We really need a survey on about the interactions not with deadlines but dead minds. There are various forms that want an application and never gave any thought to what it is they want it to do. Or, more specifically, they want 'me' to figure out how they should do their job. They come in various flavors - but a survey on how one disposes of said cretins would be interesting, informative, and perhaps even helpful.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Sounds like we worked in the same place. Dead minds is the right way to say it. In the end it comes down to staying there and work like a robot or to say goodbye and let them rot in the little hell they have made for themselves.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
You know, when it becomes completely impossible to reach the goal, we sacrifice a chicken* to pagan gods...
* We keep one chicken in each technician car trunk.
Then everything goes fine and all the deadlines are always accomplished without problems...
|
|
|
|
|
So that's what you call your juniors.
|
|
|
|
|
Weird. We usually sacrifice up to five goats to appease Baphomet.
Generally, around goat #3, a random developers goes insane and the deadlines become manageable again.
Pretty decent ROI so far. Which deity do you prefer?
|
|
|
|
|
...and are therefore agile enough to respond to changes 
Means, we barely have "hard" deadlines, +/- one sprint, sometimes even two is not a problem in general. And YES, we already had "minus one sprint" more than once and could release sooner than expected.
Sometimes a story is risky or has "*if* this works with that framework, it's a 3, otherwise could be up to 8..." ... and when it comes out, we COULD complete the story with 3 points, then, yes, then we are faster than expected.
This is accepted in the entire company (from the owner, the ceo, sales, marketing, all departments) and the entire company lives "scrum". This is, what makes working here sooo great. Best job I had so far.
|
|
|
|
|
Mike Barthold wrote: the entire company lives "scrum".
IMHO, that's the only way to do agile. The agile methodology has garnered a bad rap because many developers have been forced to follow it in isolation, under the premise that it will magically allow software to be delivered faster. If your company isn't agile, you're doing agile wrong.
/ravi
|
|
|
|
|
|
N_tro_P wrote: In said company though, there are going to be divisions that can use agile and use it effectively.
Good point.
/ravi
|
|
|
|
|
Deadline:
(a) A hardware communication cable that resists all all varieties of handshaking, however friendly.
(b) A vague series of prophesies intended to establish a time-frame by which a certain project should not be complete.
Cheers,
Mick
------------------------------------------------
A programmer is a person who always checks both ways when crossing a one-way street.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
