What do you know...
-
The project I said would take 4 weeks, that management demanded be done in 2 weeks (without working late) is finished in 2 weeks. With a lot of bugs and no unit tests. :doh:
-
The project I said would take 4 weeks, that management demanded be done in 2 weeks (without working late) is finished in 2 weeks. With a lot of bugs and no unit tests. :doh:
There are three main aspects to any project: -Quality -Features -Delivery Date One of these will vary. You decide.
Steve Wellens
-
I did realize this, too late. I finished in 2 weeks and the first thing they said was "we should have said 1 week." But now that it is in Test they're finding out that vague requirements, a lack of direction from the Business and a compressed time frame have led to a lot of gaps, not just in the code but in what they actually wanted the application to do. If this thing goes live in less than another 2 weeks I'd be surprised. And that would bring me right back to my original 4 weeks.
We call that iterative development, take their vague specs and lack lustre involvement and turn out a prototype. That gives them something to get excited about and gets them involved. The actual project will finish in about 8 months if ever! The most you can hope for is that the changing requirements don't break your data structure requiring a major refactor.
Never underestimate the power of human stupidity RAH
-
We call that iterative development, take their vague specs and lack lustre involvement and turn out a prototype. That gives them something to get excited about and gets them involved. The actual project will finish in about 8 months if ever! The most you can hope for is that the changing requirements don't break your data structure requiring a major refactor.
Never underestimate the power of human stupidity RAH
For what its worth, one of my personal observations (that I have never seen anywhere) is that long projects often fail because of schedule stretching due to feature creep. With a short project, there is close to zero feature creep, and in my observation, success rates (measured by customer satisfaction) are higher. If you did it in 2 weeks, it is almost agile regardless of what processes you used. :-)
-- Harvey
-
For what its worth, one of my personal observations (that I have never seen anywhere) is that long projects often fail because of schedule stretching due to feature creep. With a short project, there is close to zero feature creep, and in my observation, success rates (measured by customer satisfaction) are higher. If you did it in 2 weeks, it is almost agile regardless of what processes you used. :-)
-- Harvey
We had some time and motion people in recently and we were discussing our development methodologies etc. We were accused of using agile, it turns out we do the agile style without the formal agile crap that goes with it! Haven't done a sprint in 30 years, as for daily meetings, not a chance.
Never underestimate the power of human stupidity RAH
-
We had some time and motion people in recently and we were discussing our development methodologies etc. We were accused of using agile, it turns out we do the agile style without the formal agile crap that goes with it! Haven't done a sprint in 30 years, as for daily meetings, not a chance.
Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
it turns out we do the agile style without the formal agile crap
Same here. We're a casual agile (note the lower case 'a' there) shop. We did have the grand poobah once try to start code reviews, in which he was going to have the hardware engineers review our code, and we were going to review the hardware engineers' designs. We left his body in the stocks until the local flock of turkey vultures had picked his skeleton clean.
Software Zen:
delete this; -
The project I said would take 4 weeks, that management demanded be done in 2 weeks (without working late) is finished in 2 weeks. With a lot of bugs and no unit tests. :doh:
AnalogNerd wrote:
With a lot of bugs and no unit tests.
That is how we roll out projects too. They finish on unrealistic schedules and no one seems to care. They just assign the inevitable problems that plague the project like it is just another day at the office. It seems the new modus operandi in these times of low budgets and under staffed projects. I believe you can have it fast, you can have it right, you can have it cheap; choose two. :doh:
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopes -
Mycroft Holmes wrote:
it turns out we do the agile style without the formal agile crap
Same here. We're a casual agile (note the lower case 'a' there) shop. We did have the grand poobah once try to start code reviews, in which he was going to have the hardware engineers review our code, and we were going to review the hardware engineers' designs. We left his body in the stocks until the local flock of turkey vultures had picked his skeleton clean.
Software Zen:
delete this;I'd love to do code reviews, code to a testing framework, proper specs and have a QA team, in my dreams!
Never underestimate the power of human stupidity RAH
-
I'd love to do code reviews, code to a testing framework, proper specs and have a QA team, in my dreams!
Never underestimate the power of human stupidity RAH
Ah, but did you notice who was going to review what: this moron wanted hardware guys to review software, and vice versa. He must have been hit with a larger than usual stupid stick that day.
Software Zen:
delete this; -
There are three main aspects to any project: -Quality -Features -Delivery Date One of these will vary. You decide.
Steve Wellens
A long time ago I saw a quote that said something like "Fast. Cheap. Good. Pick two." Yours makes more sense for my situation since I'm salaried and "cheap" isn't a factor. I'll be using this from now on. Thanks!
-
AnalogNerd wrote:
With a lot of bugs and no unit tests.
That is how we roll out projects too. They finish on unrealistic schedules and no one seems to care. They just assign the inevitable problems that plague the project like it is just another day at the office. It seems the new modus operandi in these times of low budgets and under staffed projects. I believe you can have it fast, you can have it right, you can have it cheap; choose two. :doh:
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopesI saw this Dilbert comic this weekend [^] My new response will be "I can fail at any speed you like." :laugh:
-
I saw this Dilbert comic this weekend [^] My new response will be "I can fail at any speed you like." :laugh:
AnalogNerd wrote:
My new response will be "I can fail at any speed you like."
Good quote, I'll use it too. :thumbsup:
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopes