How Not to Run an IT Project: A Case Study
You have to read this to believe it.
The reasons for IT project failure almost always stem from people—not machines. After all, they don't tell themselves to make bad decisions.
Because so many organizations attempt to hide their dirty laundry, though, rarely do we see an insider’s account of the precise points at which a project derailed. In this Cutter Consortium Executive Report, I provide a detailed case study to examine these issues at one organization. While I'm at it, I discuss data quality and data governance.
If you want to view this post, you'll need to suscribe to this site.
Sign up to continue reading this content.
