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.
To read the rest of this post, subscribe or sign in with your
π Free account.
It'll only take a moment.
