What I Learned At The Consolidation | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Executive
Resources
|
Home > Features > Case Studies
… or where’s a work breakdown structure when you need one? Some fundamental lessons were learned the hard way on a complex datacenter consolidation project that failed to meet one urgent (but ultimately undefined) objective. Here’s the first-hand account from a veteran program director.
Project Yourself is an ongoing series that invites project professionals to share practical advice, personal insights and pet peeves based on their experiences in the field. Anonymity, if desired, is assured. To submit an article for consideration, contact the editor.
“Guys, can I ask a question?” The tone of meeting changed with this inquiry from the CIO. “How long have we been at this?”
The weekly status update meeting of our transition team’s progress suddenly took an awkward turn. The team had been hard at work for the past 12 months trying to integrate a recent company acquisition. The progress had been slow and had failed to produce any big successes (or financial gains, for that matter) for all of the effort and money that had been spent so far.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement