Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How should I behave as a developer in a project that's headed for failure?

programmers.stackexchange.com

Post reply on HN
Print view View original

1–10 of 163 posts

Re: How should I behave as a developer in a project that's headed for failure?

#2

Post by Nursie »

Be professional. State your concerns to your manager, and probably a level up as well. Make it clear that you don't have any confidence in the project as planned and you think that the cause is a hopeless one.

Then (assuming you want to keep working there, as the author seems to) make it clear that if they still want to go ahead then you are fully committed to helping them to the best of your abilities.

But a project in as bad a state as described? Get another job.

Re: How should I behave as a developer in a project that's headed for failure?

#3

Post by edw519 »

Choose from 2 extreme alternatives:

a. Treat this project as if it were your sick child on life support.

b. Treat this project as if it were a gazelle being ripped apart by a pride of lions.

If you choose (a), do anything and everything you can to save it. Be open and sincere and stop at nothing.

If you choose (b), prepare a resume and run the other way. No sense risking your own well-being on a lost cause.

The worst thing to do would be to make any choice in between these two.

Re: How should I behave as a developer in a project that's headed for failure?

#6

Post by harryf »

In a culture like that appears to be, it's pointless to be that guy screaming about the upcoming iceberg. No one will listen. Far better to be the guy with solutions once fail happens.

Frankly this sounds like the sort of environment where introducing scrum would be a big step forward. As the developer, knowing a good scrum consultant to introduce to the company might be a good move, once the fail happens.

Re: How should I behave as a developer in a project that's headed for failure?

#8

Post by Trufa »

edw519 wrote: post #3

Choose from 2 extreme alternatives: a. Treat this project as if it were your sick child on life support. b. Treat this project as if it were a gazelle being ripped apart by a pride of lions. If you choose (a), do anything and everything you can to save it. Be open and sincere and stop at nothing. If you choose (b), prepare a resume and run the other way. No sense risking your own well-being on a lost cause. The worst…

I think you should post that comment as an answer, it is very graphical but helpful!

Re: How should I behave as a developer in a project that's headed for failure?

#9

Post by smackay »

I'd be hesitant to raise concerns, on what appears to be a relatively small project, in case you become the scapegoat and a way for either the manager or your colleagues to point the finger at you for not being a team member and hence the reason the project failed.

Since it's only 6 weeks to the deadline it is probably worth pitching in and trying to make it work. If failure is going to be a big deal then you'll all be looking for jobs anyway. Alternatively it might turn out that the deadline was not so crucial and you will be able to sort out the mess.

Always remember that rats are first to desert a sinking ship - you don't want to end up with being labelled as such.

Post reply on HN