Take this scenario: delivery of a major upgrade to a critical business application which demands a new version of Windows to work on desktops is running late. All the time has gone into optimising the application itself but it is now thrown ‘across the fence’ to the IT team responsible for deployments and given three weeks to go live with the new application on all 1,000 devices across the organisation.
Because the deployment team is the last barrier to getting this application into wide use, they come under intense pressure to get a new Windows Operating System deployed alongside this new application. They can then be positioned, unfairly, as the barriers to the successful project delivery.
All too often this leads to a rushed deployment project. This might satisfy the timescales of the project team responsible for getting this new business application live, but it simultaneously sets up hidden support and adoption issues and costs for years to come.
OneDeploy addresses this issue by having supportability and re-deployment coded into its DNA, making it easy to adapt and deploy new requirements of a wider project team even at the last minute.