News Stay informed about the latest enterprise technology news and product updates.

Dude, you’re migratin’ to Vista

Dell has announced its own Windows Vista migration tool, joining a growing list of vendors looking to capitalize on the complexity of deploying the new OS.

Dell calls its offering the Client Migration Solution and claims it can “reduce migration costs by up to 62%.” It automates much of the Vista deployment process and addresses the problems of application compatibility and bandwidth usage. The target audience is businesses with at least 2,500 seats.

Symantec has been using Vista migrations as the main selling point for its Altiris Application Compatibility Suite for more than a year now. And last week Microsoft bought Kidaro, a desktop virtualization vendor whose technology will allow users to run incompatible software on Vista machines.

Even with this month’s release of SP1, Vista complaints are still coming in strong. It remains to be seen whether or not this new spate of deployment tools will help nudge XP users closer to Vista, but at least the products will be available when Vista migrations begin en masse.

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

In our project the Life Cycle Manager is responsible for managing requirement change towards the development team
Feature creep is not an issue. It has happened but in a manageable way.
hey we have always been using agile in our organization the user has always been involved, the management team, technical team everyone but the problem of feature creep seems to be on the increase. this is a sole user and each time she looks at the system she wants either a new feature or a feature to be removed or changed. How best can I handle this situation because it seems the project will never come to an end.
We do have some feature creep, but I don't concern myself with it too much. The team will be asked to give a high-level estimate to change or add new functionality. It is up to the product owner to decide whether that feature is worth the cost of implementing it. It can become annoying at times when someone changes their mind, but responding quickly to change is really what being agile is all about. 
It seems inevitable for us, sometimes desired, even encouraged. It's hard to know every nuance until we're part way into the project. So we budget for some feature creep and we're prepared for it.  The task for us isn't to eliminate it, but to keep it within reasonable bounds.
Feature Creep is inevitable, but the better question might be "did we actually think this through effectively?". More times than not, IME, Feature Creep has not been "wow, that's great, but it would be really cool if it did this too" to "well, we thought we understood what the customer wanted, but as we got into the details, we realized that we would need to do these several additional things for the implementation to be a success".
We need to do a better job with this. We constantly have additional work/features pushed on us, but no one is willing to tell business that means that something else will have to be dropped, or the deadline will have to be pushed.