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

Re:How should I behave as a developer in a project that's he... by sageikosa on Wednesday May 29, 2013 @09:08AM (#5786026)

The downside to such a strategy might be that the reason for the impending failure is the manager, and/or the level up as well.

Most organizations operate (and should operate) according to what the top-level decides should happen. If the top-level defaults on that responsibility, then chaos will ensue.

In those cases a value judgment of the process is a value judgment of the organization, and most astute managers realize it sometimes before the "innocent" (i.e., socially naive on organizational dynamics) system builder guy realizes it.

[ Parent | on HN ]

Re:How should I behave as a developer in a project that's he... by Nursie on Wednesday May 29, 2013 @10:06AM (#5786324)

Well yeah, the reason I mentioned the level up is that sometimes your manager is the problem, and sometimes your manager isn't telling the business about the problem.

If both of those are part of the problem (don't worry! All is well!), rather than realistic (we know there are serious problems here but we think there's a chance/we'd like to try anyway), then it's time to think about the systemic problems and consider finding yourself a new job (IMHO).

[ Parent | on HN ]