AITS-0110 SharePoint 2013 Upgrade

Transcription

1 AITS-0110 SharePoint 2013 Upgrade 1 Kick-off Meeting July 9, 2014

2 Agenda Project Overview Scope & High-Level Tasks Project Processes Impact, Dependencies, and Assumptions Risks & Issues Project Team Budget & Schedule

3 3 Project Overview This project will upgrade all existing SharePoint 2010 farm environments (Development, Test, Production) to SharePoint These SharePoint environments are part of the enterprise shared service to the university (

4 Project Goals Upgrade SharePoint 2010 farms to SharePoint 2013 in Development, Test, and Production environments. Keep the same URL for SP 2013 (intranet.uillinois.edu) The SP 2010 site will be called old.intranet.uillinois.edu SharePoint 2013 upgrade methodology Upgrade the core infrastructure to SP2013 Retain site collections in SP2010 compatibility mode Upgrade individual site collections. Site Collection Administrators select one of two options below: 1. Site collections to be upgraded when the infrastructure goes live 2. Site collections to be upgraded by the Site Collection Administrator within 6 months of the infrastructure goes live date SharePoint 2010 will be decommissioned 6 months after the infrastructure goes live

5 5 Project Scope In Scope All existing SharePoint 2010 farm environments will be upgraded to SP 2013 All existing SharePoint 2010 site collections on the Shared Service will be upgraded to SP 2013 Decommissioning of all SharePoint 2010 environments 6 months after SP 2013 goes live Implementing new servers for SharePoint 2013 environments (Development, Test and Production) Disabling Remote Blob Storage (RBS) Out of Scope No new functionalities other than default SharePoint 2013 enhancements No migration from SharePoint 2007 to SP 2013 Cutover to SiteMinder authentication

6 6 High-Level Tasks Identify site collections to be upgraded with the farm upgrade Develop project plan Build Development (complete) and Test environments Run test upgrade of identified site collections Site Collection Administrators coordinate testing of their sites Site Collection Administrators coordinate communication to their user communities Coordinate deployment activities Build Production environment Execute dress rehearsal of the migration upgrade Production GO LIVE Decommission SharePoint 2010 farm & upgrade all site collections to SP 2013

7 7 Site Collection Administrator (SCA)Role Identify when their site collections will be upgraded. Select one of the two options: 1. Site collections to be upgraded when the infrastructure goes live 2. Site collections to be upgraded by the Site Collection Administrator within 6 months of the infrastructure goes live date

8 8 Site Collection Administrator (SCA) Role Coordinate their site collections upgrade with their department in regards to: Communication Schedule Testing Test all site collections (SP 2013 and SP 2010 compatibility mode) Report issues to 2013 Upgrade discussion board Provide time for department testing Ensure issues resulted from testing are resolved How to look for help Post your questions to 2013 Upgrade discussion board on

9 9 Site Collection Content Owner Role Informed and aware of the schedule, changes, updates, etc. Report any issues or concerns to the SCA Test and verify the content is migrated completely and correctly

10 10 Project Processes Weekly Operation Team Meetings Review project status, action items, issues, risks, decisions Monthly meeting/communication for Site Collection Administrators SharePoint for document collaboration Change of scope will be considered according to process in the Project Charter Issues/Risks/Decisions reviewed in project status meetings

11 11 Impacts, Dependencies, Assumptions Impact: Business functionalities may be impacted depending on what departments built with their SharePoint 2010 Dependencies: Control Point Bamboo Alerts Plus ARC GIS Assumptions: By the SharePoint customization policy, if third party customizations don t work they will not delay the SharePoint 2013 upgrade Documents/Policy and Governance Documents/SharePoint 3rd Party Add-On Policy and Expectation.docx New servers are acquired and tested for the project implementation Tasks will be prioritized by the team, and project team resources are available to work on this project

12 12 Risks This project requires acquisition of multiple servers for the environments upgrade. We can t upgrade if we don t have the servers. We mitigate this risk by proactively requesting funding to acquire the servers. Due to the number of site collections and their variances, the upgrade is complex. We mitigate this risk by planning for high quality testing in nonproduction environments. Provide time for department testing.

13 13 Project Team Role/Participant Amin Kassem SharePoint Shared Service Advisory Group Shawn Lee, Brad Horn, Larry Gibson, Hussain Zaidi and Tyler Rubach Amanda Hemming, Deb Bramowicz DBAs CRM QAs Windows Administrators Deployment Security Noni Ledford Responsibility Director of SharePoint Shared Service provides overall project oversight and approval of deliverables Provide consultation on project deliverables Conduct technical planning, upgrade installations, and systems testing Provide functional analysis and testing, serve as the main liaisons with end-users Conduct Database provisioning and configuration Communicate preparation information to Site Collection Administrators Conduct vulnerability, load, and accessibility testing Server provisioning Implement the upgrade to production environments Provide security assessment and sign-off Provide project management oversight to ensure project deliverables meet the requirements.

14 14 Estimated Effort Effort Participant Hours of effort SharePoint Administration Shawn Lee, Brad Horn, Larry Gibson, Tyler Rubach, Hussain Zaidi 1040 hours Deployment Debbie Peterson 40 hours Security Troye Kauffman 20 hours Functional Testing Amanda Hemming, Deb Bramowicz 80 hours Database provisioning Chris Newman 100 hours Communication Mark Pollard 40 hours Testing QA 40 hours Windows Administration TBD 80 hours Project Management Noni Ledford 120 hours Post-deployment support Shawn Lee, Brad Horn, 50 hours Larry Gibson, Tyler Rubach, Hussain Zaidi TOTAL 1610 hours

15 15 Proposed High-level Schedule Identify site collections to be upgraded with farm upgrade Build Test environme nt and run test upgrade of site collections Site Collection Testing in Test environme nt Deployment activities: Build Production environment & execute dress rehearsal Production GO LIVE Decommis sion SP 2010 all site collections are upgraded Now July 31 st 2014 By August 31 st 2014 Sept-Dec weeks before go live January 2015 July 2015

16 16 Next Steps By July 31 st, Site Collection Administrators need to request if they would like their site collections to be upgraded when the infrastructure goes live Go to Select 2013 Upgrade Click on 2013 Upgrade Request Select reply and provide the requested information described in the discussion item Start Planning phase Build Test environment Develop project plan and communication plan

17 17 Questions? Comments? Concerns?