|
Make ROI calculations and business justifications for application projects prior to implementation
Beware feature creep-limit growth in application scope by devising a project plan and sticking with it
Strive to finish on time, leaving out optional features if necessary
Map out business processes before implementing applications
Don't customize unless absolutely necessary; be willing to adopt application best practices
Avoid a "big bang" all-at-once implementation; roll out applications one module at a time to minimize pain and maximize business returns
Carefully weigh platform and integration issues; don't be swayed by features alone
Don't dictate an implementation; solicit-and act on-user feedback
Get the business side to take ownership of an application
Train, train, train
|