1. Microsoft Deployment Workshop Deploying Office 2003 Editions Joe Liptrot Linkpad Limited

2. Agenda 1. Office installation options 2. Office compatibility 3. Migrating applications - Application Compatibility Toolkit 4. Access / Word / Excel migration issues 5. Project Management 6. XP - the road to Longhorn

3. Solution Accelerator for BDD

4. Agenda The Problem Space Microsoft Solutions Framework (MSF) Cost Development Solution Components

5. Challenged Succeeded Failed Based on more than 13,522 projects Challenged = Completed but over budget or past the original deadline The Problem Space 15% 51% 34% “When projects fail, it’s rarely technical.” Jim Johnson, The Standish Group

6. What Are the Obstacles? Separation of goal and function Separation of business and technology Lack of common language and process – Unclear goals – Unmanaged scope changes Failure to communicate and act as a team Processes that are inflexible to change

7. Common Desktop Deployment Issues Application compatibility – Don’t know about the Application Compatibility Toolkit and how it can solve “compatibility” issues. Application packaging – One of the most common issues that delays deployment projects – Start too late, low or no experience, low quality packaging and/or testing Deployment logistics Lack of people and processes No business case – Technically-driven projects with no or low business buy-in Lack of functional requirements from both IT and the business

8. Microsoft Solutions Framework (MSF) MSF offers guidance on how to organize people and projects to plan, build, and deploy successful IT solutions

9. Feature Teams Advantages and Disadvantages of Feature Teams Advantages – Divides the work into discrete, definable parts – Applies specialized expertise in areas where it is needed – Ensures adequate cross-discipline involvement in the team – Most importantly, fosters ownership of the problem space involved: – Empowerment – Accountability – Results in a high degree of focus Disadvantages – Ironically, the team's high level of focus – Can cause the feature team to develop tunnel vision – Lose contact with the larger project that is tasked to establish the new infrastructure – When this happens, the decisions will be sub-optimized at best, but could easily lead to contradictory and mutually exclusive strategies being adopted by two or more feature teams

10. Solution Components Solution Guide Technical Guides Templates Solution Scripts Solution Guide for project management, envisioning, and planning Technical Guides broken into Feature Teams for each set of procedures Templates for documenting the entire project, including: planning, communication, and analysis Code needed to enhance automation and integration between tools and procedures

11. BDD Project Deliverables Business Case Statement of Work Project Schedule Vision & Scope Functional Specification Risk Assessment Communication Plan Training Plan Test Plan Migration Plan Deployment Plan

12. Typical Project Schedule Full Enterprise Deployment: 12-18 months Prepare for Enterprise Rollout: 3-7 months Lab Testing Pilot Deployment Approval Process Enterprise Rollout 3-4 Wks 1-3 Months 2-5 Months 6 Months Average timeline from Group of 35 Enterprise Customers

13. Cost Development

14. Failure in Project Communication…

15. Welcome to this TechNet Event FREE bi-weekly technical newsletter FREE regular technical events hosted across the UK FREE weekly UK & US led technical webcasts FREE comprehensive technical web site Monthly CD / DVD subscription with the latest technical tools & resources FREE quarterly technical magazine We would like to bring your attention to the key elements of the TechNet programme; the central information and community resource for IT professionals in the UK: To subscribe to the newsletter or just to find out more, please visit www.microsoft.com/uk/technet or speak to a Microsoft representative during the break www.microsoft.com/uk/technet

16. http://www.microsoft.com/uk/technet