82,891
edits
Banner IT project: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{g}}{{a|tech|}}A fine principle; a forlorn actuality. | {{g}}{{a|tech|}}A fine principle; a forlorn actuality. “Banner” IT Projects thrill middle managers and terrify everyone else. They tend to get described with aspirational adjectives: “Transformational”. “Paradigm-shifting”. “Game-Changing". They are usually accompanied by scores of enthusiastic, [[powerpoint]]-toting [[business analysts]]. | ||
Measured against their original [[terms of reference]], there is no such thing as a complete or successful banner IT project. Usually they continue in perpetuity and, like chronic fatigue syndrome, you just have to live with them. Occasionally they are (finally) implemented, but even then limp along unsatisfactorily without delivering a tenth of their original promise. A successful banner IT project is simply one that is not so catastrophic that it doesn’t need to be immediately replaced (or worked around using excel spreadsheets, hand-filled forms and a scanner). | Measured against their original [[terms of reference]], there is no such thing as a complete or successful banner IT project. Usually they continue in perpetuity and, like chronic fatigue syndrome, you just have to live with them. Occasionally they are (finally) implemented, but even then limp along unsatisfactorily without delivering a tenth of their original promise. A successful banner IT project is simply one that is not so catastrophic that it doesn’t need to be immediately replaced (or worked around using excel spreadsheets, hand-filled forms and a scanner). | ||