AITS-0110
SharePoint 2013 Upgrade
Kick-off Meeting
July 9, 2014
Agenda
Project Overview
Scope & High-Level Tasks
Project Processes
Impact, Dependencies, and
Assumptions
Risks & Issues
Project Team
Project Overview
This project will upgrade all existing SharePoint
2010 farm environments (Development, Test,
Production) to SharePoint 2013. These SharePoint
environments are part of the enterprise shared
service to the university
(
http://web.uillinois.edu/sharepoint
)
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
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
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
Site Collection Administrator (SCA)Role
Identify when their site collections
will be upgraded. S
elect 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
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
https://intranet.uillinois.edu
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
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
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
https://intranet.uillinois.edu/sites/spboard/Shared 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
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
non-production environments.
Provide time for department testing.
Project Team
Role/Participant Responsibility
Amin Kassem Director of SharePoint Shared Service provides overall project oversight and approval of deliverables
SharePoint Shared Service Advisory Group
Provide consultation on project deliverables Shawn Lee, Brad Horn, Larry
Gibson, Hussain Zaidi and Tyler Rubach
Conduct technical planning, upgrade installations, and systems testing
Amanda Hemming, Deb Bramowicz
Provide functional analysis and testing, serve as the main liaisons with end-users
DBAs Conduct Database provisioning and configuration
CRM Communicate preparation information to Site Collection Administrators
QAs Conduct vulnerability, load, and accessibility testing Windows Administrators Server provisioning
Deployment Implement the upgrade to production environments Security Provide security assessment and sign-off
Noni Ledford Provide project management oversight to ensure project deliverables meet the requirements.