When Is It Time to Kill a Project?
April 16, 2009 | Author: PM Hut | Filed under: Miscellaneous
When Is It Time to Kill a Project?
By Ron Rosenhead
Below are the main reasons behind killing a project:
- When the project has formally ended i.e. all the deliverables have been accepted by the client and the project formally closed.
- When it is obvious that the project will not deliver against the original business case.
- When the project is so over budget that you are simply pouring money into a sinking hole.
- When key stakeholders object to or clearly do not buy into the project and without them, the project will clearly not succeed.
- When the project does not fit with the overall strategy of the company.
- When risks are so high that too continue would impact negatively on the company.
- When you have delivered 80% of the project and the other 20% meant 80% more time and the return on investment was not worth it.
Ron Rosenhead is a trainer, consultant speaker and coach all in the area of project management. He has vast consultancy and training experience and you can read his blog at http://www.ronrosenhead.co.uk
Related Articles
No comments yet.
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.










