SharePoint: What You Need to Know Before Upgrading


Published on

Perficient's Senior Architect Suzanne George outlines the key things you need to know before you upgrade your company's SharePoint implementation, including:
SharePoint terminology, features and versions
Roadmap planning
Licensing, upgrade and development tools
Undefined or forgotten costs
Requirements examples
Migration project plan
Content Migration Methodology

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

SharePoint: What You Need to Know Before Upgrading

  1. 1. What you need to know before upgradingSharePoint 2010<br />Prepared By: Suzanne George<br /><br />Sr. Architect<br />Perficient - Microsoft West Region<br />May 2011 <br />
  2. 2. Know your SharePoint..<br />The more you understand the new features of SharePoint and its improvements/features the smoother your upgrade will be.<br />Key point to remember<br />SharePoint is an enabling framework which connects the Microsoft Product line such as SQL Server, Project Server, etc.<br />Know your SharePoint<br />Terminology<br /><br />Versions - go beyond ‘cool’ and determine what you need <br />Which version do I need? CALs?<br /><br />Features – which features will be implemented when?<br />Use the crawl, walk, run methodology<br />Physical location – Will the farm be hosted or in-house and what will the SLA be?<br />2<br />
  3. 3.
  4. 4. Roadmap Planning<br />Define the business roadmap – The key to minimize risks and surprises is planning. In most cases the SharePoint upgrade is not a “double-click” process.<br />If you fail to plan, then you plan to fail!<br />Run a cost-analysis to understand the cost-benefit of upgrading. Stay focused! SharePoint is a framework and contains lots of features – prioritize those benefits!<br />Training, training, training!! Your staff need to either a) have months to research (ie: Bing!) how to handle the upgrade or you need to get training. This includes Administrators, Developers, End-Users, etc.<br />Inventory your current system – take time to look at your current system (even if it is paper-based) and determine what features of 2010 you will need to implement, then update your project plan.<br />Have a backup plan – Things happen, take longer, and don’t work as expected so plan for Murphy should the worse case scenario happen. Further, at each project milestone meet with all parties to discuss Go-no-Go.<br />Get a second line of defense – In other words find someone who has done this before. <br />4<br />
  5. 5. Costs involved<br />What are the costs involved to upgrade? Answer: Depends…<br />SharePoint 2010 licensing<br />depends on your version … <br />Cost calculator by Bamboo<br />Hardware upgrade needs<br />do you need to upgrade your hardware to 64 bit? Memory? <br />Development environment<br />UAT/staging environment<br />Production environment<br />Development Tools<br />Visual Studio 2010, TFS 2010, ReSharper, SQL server 2008R2<br />Migration tools – roll your own or use 3rd party product?<br />Upgrade desktops/laptops/etc<br />5<br />
  6. 6. Cost continues<br />Often forgotten or not defined costs…<br />New installation budget 25 man weeks of effort for a basic install / configure<br />Project management, basic governance<br />Development – design, integration, code, QA<br />Administration<br />Custom webparts<br />Custom webparts – budget 1-2 weeks for each (some will take less, some will take more)<br />Administration<br />Migration of data – depends on upgrade method – budget 2+ weeks depending<br />Are you restructuring your site map?<br />Consultants<br />Do you need extra resources to make this happen<br />The unexpected consultant - “The Wolf”<br />UAT / QA testing<br />Users of the application testing<br />Load testing/performance<br />6<br />
  7. 7. SharePoint Roadmap Process<br />7<br />
  8. 8. An example roadmap<br />8<br />Q1<br />Q2<br />Q3<br />Q4<br />Planning, Communication and Oversight<br />Roadmap<br />Foundation (Global Support)<br /><ul><li>Technical Architecture (Prod, QA, Dev)
  9. 9. Branding Standards
  10. 10. Development Standards
  11. 11. Security Model
  12. 12. DR, HA and Archive Architecture
  13. 13. User Acceptance Planning and Testing
  14. 14. Functional Use Cases / Wireframes
  15. 15. Program Planning
  16. 16. Governance
  17. 17. Information Architecture
  18. 18. Taxonomy
  19. 19. Multilingual Architecture
  20. 20. Base Site Structure
  21. 21. Search
  22. 22. UX Branding
  23. 23. Training Plan
  24. 24. Organizational Plan
  25. 25. Communications Plan</li></ul>Migration (SharePoint 2010)<br /><ul><li>Current State Content and Customization Analysis
  26. 26. Current State Security and Access Model
  27. 27. Current State Data Usage and Access Analysis
  28. 28. Usage Questionnaire Completion
  29. 29. Foundation Gap Analysis
  30. 30. Migration Plan
  31. 31. Migration Execution
  32. 32. Migration Acceptance Testing</li></ul>Value Applications<br /><ul><li>Transaction Integration
  33. 33. Business Intelligence
  34. 34. BPM
  35. 35. Search Results
  36. 36. Personalization
  37. 37. Notes Applications
  38. 38. CRM
  39. 39. Extranet /Internet
  40. 40. RIA
  41. 41. Mobile</li></ul>Transition<br /><ul><li>Performance Testing
  42. 42. Go Live Planning and Support
  43. 43. User, Admin and Dev Training
  44. 44. User, Admin and Dev Doc’s
  45. 45. Production Support</li></li></ul><li>Prioritized / Risk Adjusted Requirements Example<br />9<br />
  46. 46. Example of a migration project plan<br />10<br />
  47. 47. Governance<br />SharePoint can make a good process better and a bad process worse…<br />What is governance?<br />Policies, roles, responsibilities, and processes that guide, direct, and control how an organization's business divisions and IT teams cooperate to achieve business goals. <br />Define business process first – implement second<br />Organizations try to implement SharePoint 2010 to solve business processes which have not been defined yet.<br />Don’t get complicated – keep it simple, improve and add as business needs require.<br />MSDN has a good governance policy you can modify<br /><br />Hire a consultant? <br />11<br />
  48. 48. Preparation - Find issues before you upgrade<br />Issues do not disappear when you upgrade, make sure they are resolved (if possible) in your current environment.<br />Verify your existing SharePoint 2007 environment is up to date with patches<br />Use the pre-upgrade check on your existing system and resolve any issues – check for missing features and custom field errors<br />Check for broken links in existing sites<br />Review and identify all customizations – make sure you have the code and/or installer for each!<br />Optimize your large lists<br />Optimize your content databases<br />Upgrade to 64 bit environment<br />Understand any/all UI changes and authentication methods<br />12<br />
  49. 49. Upgrade Philosophy<br />Some ideas which will help you during the upgrade process<br />Detect and Discuss issues early<br />Report critical issues early<br />Do NOT implement a solution which will lose data<br />Keep as much of your content and settings as possible<br />Minimize downtime<br />Continue when possible<br />Be reentrant<br />Keep the administrator / architect informed<br />13<br />
  50. 50. Content Migration Methodology<br />14<br /> 2010 Perficient, Inc. Confidential. All rights reserved.<br />
  51. 51. Execute Upgrade / Next Steps<br />15<br />Build / Upgrade Farms<br />•Services farm<br />•Content farm<br />Minimize downtime<br />•Use read only with fallback environment<br />•Build for upgrade parallelism<br />Deploy customizations<br />•Use Solutions whenever possible<br />Monitor progress<br />•Watch upgrade status indicators<br />•Ensure upgrade process is on schedule<br />Maintenance<br />•Administration<br />•Development – Bug Fix<br />Assessment<br />•Review deployment<br />•Review new feature requests<br />
  52. 52. Summary<br />A successful upgrade can only be developed with the commitment of management and staff.<br /><ul><li>Access – provide access to business and technical teams that have the knowledge to provide the necessary input
  53. 53. Flexibility – grant flexibility to team members schedules to attend meetings and collaborate on concepts
  54. 54. Responsive Decision Making - empower teams to make responsive decisions on behalf of the organization
  55. 55. Governance Board – oversight of a governance board to review and provide direction
  56. 56. Collaboration – engage in the roadmap process with a highly interactive approach</li></ul>16<br />Path to successful upgrade/implementation<br /><ul><li>Learn
  57. 57. Build a business justification
  58. 58. Develop a roadmap
  59. 59. Governance
  60. 60. Plan / Test / Implement
  61. 61. Validate
  62. 62. Evolve</li></ul>X<br />
  63. 63. Client Roster<br />Partial Client List<br />17<br />
  64. 64. About Perficient<br />18<br />Leading Technology Consulting & Solutions Firm<br /><ul><li>Founded in 1997
  65. 65. $240MM+ in annualized Revenue
  66. 66. Over 1,400 highly-experienced Consultants
  67. 67. 19 Locations across North America
  68. 68. 80+% of Revenue from recurring Clients
  69. 69. Served over 400 Clients in past 12 months</li></ul>Software Solutions Expertise, including:<br /><ul><li>Enterprise Portals & Content Management
  70. 70. SOA, EAI and BPM
  71. 71. e-Commerce and Product Information Mgmt
  72. 72. Business Intelligence/ETL
  73. 73. Customer Relationship Management
  74. 74. User Experience/UCD
  75. 75. Significant Integration Expertise</li></ul>Key Differentiators<br /><ul><li>Focused expertise, lower cost, faster time-to-value
  76. 76. IT Solutions with Business Focus
  77. 77. National consultants overlay Local delivery model
  78. 78. Mature, proven Project Methodology
  79. 79. Global Development Centers in China & Europe
  80. 80. Healthcare Thought Leadership</li></li></ul><li>Thank you!<br />For further information, please contact:<br />Suzanne George<br /><br />Sr. Architect<br />Perficient - Microsoft West Region<br />Twitter: spgenie<br />19<br />