Tell me more ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

Some time ago I was involved into a so called death march project. In spite of the Brook's law, I was hired when project was in the yellow zone. Several weeks after I started on my new job, I've been asked and pushed to work overtime even though I didn't have chance to get a grip on the project (actually, it was a probationary period). Even though I didn't have the whole picture of the project, almost from the beginning I started to realize that project was savagely mismanaged.

Not diving into the causes of mismanagement (there are chances that several unpleasant risks might have been triggered all at once putting project into the yellow zone and manager just had to cut the corners), I would like to know what is the project management's ultimate responsibility for the failed project? There's been a discussion about whether it worth considering project failed or not. But let's assume that top-level decision has been made and this decision makes it clear that project has failed. What will be the responsibility/punishment of project manager for the failure then? Probably this should be covered before project is started (even written down, sealed, signed, whatever), but what if the responsibility for the failure has not been discussed and agreed? What is the default option in this case?

Possible answers are:

  • Damaged reputation (both person and company)
  • Dismissal
  • Shutting down the project
  • Torments of conscience

But that seems to be in some way incomplete and each solution might not be applicable in many cases.

Maybe project manager is not the only person who should be responsible for the failure? If not, then who else? Team as a whole, architect, business analyst lead, qa lead? How the responsibility could be shared in this case? After all, who decides?

I would like to get a clear understanding of how to deal with project manager who failed the project due to the mismanagement. Are there any best practices or any case is individual? Should there be some kind of investigation done by upper management in order to reveal mismanagement? If there are some generally accepted measures against people responsible for failure, especially project managers, I would like to hear it from you.

UPD: moved to pm.stackexchange.com: http://pm.stackexchange.com/questions/4581/what-is-the-project-managers-responsibility-for-the-failed-project

share|improve this question
did you search the web for something like project postmortem? – gnat Feb 3 '12 at 12:03
This question is not related to software development, and there is no answer to this question. It depends on the magnitude of failure, how critical the failure is to the success of the company, and even the kindness and compassion of the people or corporate rules that are dishing out the punishment. – Bryan Oakley Feb 3 '12 at 12:04
2  
There is inherent bias for the sponsors of a project against admitting project failure. Most of the time the project will have clearly failed yet for upper management to save face they will try to spin it and make it look like a success. If they are indeed admitting failure then it must have been a spectacular failure. – maple_shaft Feb 3 '12 at 13:02
@maple_shaft: when I've been composing this question, I was actually thinking about failure, which is nearly spectacular. – altern Feb 3 '12 at 13:12

closed as off topic by gnat, thorsten müller, Jonathan Khoo, Tom Squires, StuperUser Feb 3 '12 at 12:27

Questions on Programmers Stack Exchange are expected to relate to software development within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.

1 Answer

There's virtually no scenario, where a project manager should take the fall for the whole team. The project is not the manager's work, it's the team's work and as such, it is the team's responsibility.

Every team member, that did not exhaust the potential for upward management is just as responsible. Did you report arising problems and worrying tendencies to your manager at an early stage? Did you give him feedback on his (mis)management? And if you did and he ignored it, did you discuss the issue with the other stake holders?

For a team, a project manager is an asset, a tool. Failure of the project may be due to the tool not functioning well, but most of the times it is the incapacity of using the tool properly, that is an important factor in project failure.

I am almost certain, that what you describe is a team screw-up. Now that the project has failed, it would seem that nobody feels responsible for the failure. I can only infer from that, that nobody felt responsible for the project's success in the first place. And that is failure on the part of every and each one of your team members.

Therefore, if you want to punish someone, you should punish the whole team. The issues that led to failure should have been brought to attention when they could still be solved. At that time, they could have been met with improvement, not punishment.

share|improve this answer
4  
punishment for failure is a bad strategy it will lead to whistle-blowing, finger-pointing, false figures and blame-avoidance all of which will slow down any project – ratchet freak Feb 3 '12 at 12:30
-1 for punishment. Punishment and blame never make anything better, at least not in business. They are all adults and should be treated as such, not like children. – maple_shaft Feb 3 '12 at 12:58
1  
imagine situation when team successfully delivers in spite of manager's incompetence and total ineffectiveness and the mismanagement. it will be manager who gets the praise. And what will happen if team is tired of overburning/micromanagement/"you name it" and just worn out to successfully deliver? it's team who takes responsibility! they will get no bonuses while manager is untouchable. Seems very fair... :) – altern Feb 3 '12 at 13:49
1  
@maple_shaft: It wasn't me, who put punishment on the table. But I rephrased it, to make it clearer. – back2dos Feb 3 '12 at 15:35
@ratchetfreak: Yes, it would seem, that I was unclear. In the context of this question, punishment is already a chosen strategy and the question itself is already finger pointing. My point is, that the fingers are pointed in the wrong direction. I edited the last paragraph to get that across a little better. – back2dos Feb 3 '12 at 15:37
show 3 more comments

Not the answer you're looking for? Browse other questions tagged or ask your own question.