With the world becoming increasingly dependent on technology, it is not surprise to anyone that IT projects are literally coming out of the woodwork. If that is not a big enough pill to swallow, IT projects, regardless of their particular industry, fail at a higher rate than infrastructure projects. All of this means that the project manager's role is crucial, and is even more crucial when it comes to healthcare IT projects.
Healthcare is a big business and is only continuing to grow. Because of this, technology must adapt and transform to meet the needs of the public. Failed healthcare IT projects are nothing new. However, they surely are something that can be learned from. In every failure is a lesson that can be used for a future project - a lesson that can help to save, or better, someone else's life.
Lessons learned means finger pointing at stakeholders. The lessons learned aren't brought to enough detail to actually be helpful to anyone unless they have no experience with project management. Stakeholders, unless they've worked in IT cannot imagine the complexity of IT projects. Stakeholder "buy in" cannot exist without an understanding of that complexity. The books early mapping of IT projects to construction project is glossed over and can span the length of a book this size. While not entirely inaccurate it doesn't map to the reality of IT projects. Requirements for IT projects are enormously complex and they shift rapidly, at the core of these requirements are user level requirements. While this is brought up for Google health, it's ignored for most of the projects.
1 of 1 people found this review helpful