VIRTUALISATION
How to make a software roll-out fail, part 4 | How to make a software roll-out fail, part 4 |
|
| by David Heath | |
| Monday, 05 October 2009 | |
|
Rolling out a major project (ERP for instance) requires that a lot of complex factors are brought together harmoniously. However, such a project can be brought down by more mundane choices; here's another common one.
Featured Whitepaper
5 Best Practices for Smartphone Support
However, there are a few more 'issues' that are currently arising. Let me remind you, go-live is tomorrow and we have been in an activity-halt since early last week. There is an increasing backlog of customer orders (obviously!). The project is being managed out of an office in Sydney – just about everyone connected with the project has a public holiday today! Maybe, just maybe, this would have been the busiest day of the entire project, but no – on the penultimate day, everyone relaxed. Data cleansing has become a bigger and bigger issue. The New-Era project combines the activities of a number of business units with overlapping customer lists. Merging this data into a single coherent customer list has taken far longer than expected. It is no-where near complete. One of the business units (generally, multiple units occupy each location) has invested a lot of time ensuing that the training and reference materials are complete and usable. Other units keep seeing this material and asking (nay pleading) to get a copy as it is far better than their own. These are people who should have already been trained and be eagerly awaiting the change-over. Seems like they're neither! Speaking of eagerly awaiting, it seems that none of the key users who are expected to login first tomorrow morning and check that "number 5 is alive" has their new password. Fun times ahead... but at least all the 'big-wigs' are in town for the launch celebration party. By themselves, I expect! |
| < Next story in category | Previous story in the category > |
|---|





Tags




