Why IT governance fails
· Lack of management commitment.
· Too much time devoted to complicated process diagrams.
· Not creating written work instructions and not assigning process owners.
· Roles and responsibilities must be clearly defined and that includes management.
· Concentrating on performance criteria and not quality.
· Trying to implement too many processes at once.
· Failing to maintain momentum.
· Allowing departments to claim sole ownership of a process.
Subscribe and Share!
Did you enjoy this article? Your feedback is very important! I'd like to invite you to keep up to date with the latest posts from Anticlue. We offer several venues. If you have some questions, help can be found here.- Become a Facebook Fan
- Subscribe to Anticlue
- Follow me on Twitter
- Add to Technorati Favorites
- Digg this post
2 Comments to “Why IT governance fails”
I have a feeling someone's project was not as successful as they might have hoped. Have you looked at Scrum?
Hi Jim,
Just so you are aware, I try to keep this blog as a running list of lessons learned or items I need to remember. I thought these where worth adding to the list.
Thanks for reading!
Elyse
Please share your thoughts and suggestions
-
Receive Our eNewsletter
The latest Project Management and Healthcare IT practices
-
About Me
Welcome to the Healthcare IT Project Management Blog of Elyse Nielsen. This is the place where I share the ideas I have learned, the things I’d like to remember, and my thoughts for a brighter future. Find out more.
Subscribe to Our Tips
This weblog is licensed under a Creative Commons License.