Project requirements are changing again

[foozball3000]

..And we're supposed to finish the project off tomorrow.
We'll just have it finished, then management will announce that these new features must "quickly" be added.

If only I smoked...
If only I drank...
but i decided to code.

On the other hand, this might present the opportunity to point out that there's a reason why we should have a proper design phase that includes actual user stories. Not just the manager's opinion.
/wishes

 

[Keeper]

would you like to hire a hitman? going rate is R250.

Edit: make it R200.

 

[foozball3000]

would you like to hire a hitman? going rate is R250.

Do you always lead people into temptation when they can resist the least?

 

[Bizkit87]

scope creep is a dirty old biatch !!!!

 

[arabbess]

send the management the costs impact of the features..include dramatic increase in cost of ownership should the new features be installed..

 

[midrange]

Build in an Easter Egg: in the unlikely event a user hits the Enter key c:\Windows gets deleted.

 

[guest2013-1]

send the management the costs impact of the features..include dramatic increase in cost of ownership should the new features be installed..

+1

I usually do that and they back down quickly and say "lets just get this project done with so we can then go back at a later stage and add those later"

 

[davemc]

You're just shooting yourself in the foot by doing what they want.

The end product produced will not be polished enough and will devalue the apparent quality of your work significantly.

When it comes to raise / promotion time, your product is the only thing that you can use to argue your case, and a rushed product is not evidence of anything useful.

 

[Necuno]

that is why you should let your customer sign off exactly what they wanted and exactly what you are giving them anything after that is done if its completed with extra costs and again those changes are singed for and noted each time...