Application Subjugation
That title was too good to pass up. So how do we go about 'subjugating', or taking control of, our Notes applications? So, I had a little fun, but here's my top ten list!
10 Reasons to Gain Control of Your Notes Applications
Without control:
10 Reasons to Gain Control of Your Notes Applications
Without control:
- IT can’t be aligned with the business. (This is somewhat important since the business usually pays for these projects.)
- manual processes will continually lead to errors. (If you don’t believe me, just try typing “d space k space” 100 times in a row.)
- you won’t be able to measure end user satisfaction. (If you can’t measure it, they probably aren’t satisfied.)
- change requests take longer to implement. (This can result in the infamous change request to the change request.)
- costly downtime will happen more often. (As it turns out, inexpensive downtime will happen more often too.)
- development groups won’t be able to function as a development team. (Even development teams of one will have trouble agreeing on the version number and the source code version of the production code.)
- regulatory audits become disruptive, time-consuming, costly and labor intensive. (I guess that’s redundant.)
- risks become significantly greater. (And unlike gambling, that does not mean the payoff is bigger.)
- IT will be misused, abused and confused. (Hopefully that’s not the usual case.)
- business opportunities will be squandered. (I just wanted to say “squandered”.)
Category IT Governance
| Permalink |
|
|
|
|
|
