Simple feature, sure...
-
Ops, there goes the release date. Anyone ever add a simple feature that breaks the app's release date? ...I guess I should use release dates :) oh yea, death to sovereign bank and there over draft fees.
Take a look at my corner of the net at Code Research Center
-
Ops, there goes the release date. Anyone ever add a simple feature that breaks the app's release date? ...I guess I should use release dates :) oh yea, death to sovereign bank and there over draft fees.
Take a look at my corner of the net at Code Research Center
Simple and feature shouldn't be used in the same sentence. Realistically, whenever a feaure is added without it having been planned for the release, it will break the release date.
PM : How long is it going to take to complete feature "X"?
Me : As long as I take. Next topic, please.:)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
-
Simple and feature shouldn't be used in the same sentence. Realistically, whenever a feaure is added without it having been planned for the release, it will break the release date.
PM : How long is it going to take to complete feature "X"?
Me : As long as I take. Next topic, please.:)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
Or... "Will this be achieved by [Some Predetermined Timeframe]?" "No, Next question please." :)
------------------------------------ "Children today are tyrants. They contradict their parents, gobble their food and tyrannize their teachers. I despair for the future." Socrates 400BC
-
Ops, there goes the release date. Anyone ever add a simple feature that breaks the app's release date? ...I guess I should use release dates :) oh yea, death to sovereign bank and there over draft fees.
Take a look at my corner of the net at Code Research Center
Yes, I should simply not except any feature requests within 2 weeks of the due date.
John
-
Ops, there goes the release date. Anyone ever add a simple feature that breaks the app's release date? ...I guess I should use release dates :) oh yea, death to sovereign bank and there over draft fees.
Take a look at my corner of the net at Code Research Center
Indeed. Unfortunately people are given to believe that estimates are fact, when they are in fact just estimates.
10110011001111101010101000001000001101001010001010100000100000101000001000111100010110001011001011
-
Ops, there goes the release date. Anyone ever add a simple feature that breaks the app's release date? ...I guess I should use release dates :) oh yea, death to sovereign bank and there over draft fees.
Take a look at my corner of the net at Code Research Center
Marketing: "Hey, guys, how long will these new features take?" [quick developer huddle] Developers" "Well, if we work lots of nights and weekends, we can get it done in three months." Marketing: "Gee, we just put out a press release saying the product will be out next week, so hey, guys, how long will these new features take?"
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
Ops, there goes the release date. Anyone ever add a simple feature that breaks the app's release date? ...I guess I should use release dates :) oh yea, death to sovereign bank and there over draft fees.
Take a look at my corner of the net at Code Research Center
No, I've never worked on projects that had release dates.
-
Indeed. Unfortunately people are given to believe that estimates are fact, when they are in fact just estimates.
10110011001111101010101000001000001101001010001010100000100000101000001000111100010110001011001011
MidwestLimey wrote:
Unfortunately people are given to believe that estimates are fact, when they are in fact just estimates.
I hope you don't mind if I use this the next time I am asked why an estimate is off. <background> Management: How long will it take to complete this project? Developers: Since we don't have the requirements (requirements were still in progress at the time) it is impossible to estimate. Management: Well then take an educated guess. Developers: About 18 months. Management: It can't take that long; you have 6 months to complete it. 3 months later Management: It looks like OUR estimate is way off and we will not be finished in 6 months. Me: We told you it would take 18 months. 6 months was never OUR estimate. You imposed it on us. Management: Be that as it may come up with a realistic estimate based on the requirements. (the requirements are in final review at this point) 1 week later Developers: It will take 2 years to complete this project. 1 week later Management: Hold off on all development while we get estimates from another department (who at that point had been studying the project for 3 months and requested another month before submitting a development schedule) </background> P.S. – forgot to mention that during this time management, in their infinite wisdom, switched development language from Perl to ColdFusion, because ColdFusion was a RAD (rapid application development) language. This is not necessarily a bad thing but it neglects to take into account that the development team was put together because of their knowledge of Perl and only one developer had ever used ColdFusion to develop a few reports.
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopes -
Ops, there goes the release date. Anyone ever add a simple feature that breaks the app's release date? ...I guess I should use release dates :) oh yea, death to sovereign bank and there over draft fees.
Take a look at my corner of the net at Code Research Center
lol we have a release going live for 11 May. Currently there is no work to do on it - we have developed to the requirements and everything has passed our own internal testing. Yet earlier today we were told we'll need to be in work the weekend of 9 May and 10 May in case the client wants any extra features adding or any changes over the weekend. :mad:
-
lol we have a release going live for 11 May. Currently there is no work to do on it - we have developed to the requirements and everything has passed our own internal testing. Yet earlier today we were told we'll need to be in work the weekend of 9 May and 10 May in case the client wants any extra features adding or any changes over the weekend. :mad:
lol :)
Take a look at my corner of the net at Code Research Center