1. planning for 2013 in our
2010 project
alex pearce

2. me
Director: BFC Networks
SharePoint MVP since 2008
Twitter: @alex_pearce
Personal Interests in SharePoint
• Office 365
• Integration
• Doing as much as you can with OOTB features

3. agenda
• Why bother about 2013 when we are working so hard on 2010?
• Terminology
• Features
• Branding
• Upgrade consideration

4. why
why bother about this?

5. why bother about 2013 now?
• New features that might be better than 2010
• Help make the upgrade process from 2010 to 2013 easier, both from a technical
point of view and the end users
• Prepare for future visions and releases of your platform and when you decide to
go with 2013
• Training
• Don’t lose adoption rate between versions

6. terminology
new words, old words, changed words

7. terminology
• Help with training for 2010 and 2013
• Terminology that is there for 2010 but not 2013
• Terminology that has changed or new to 2013
• The end of lists and libraries (to the end user)

8. lists and libraries

10. terminology - app
what does app mean to different people

11. features
new feature such as communities, improved social, higher
integration with exchange and windows

12. demo – communities

13. site templates

17. demo – site template
differences between the 2010 team template and the 2013 team
template

18. demo – skydrive
offline sync to the desktop with skydrive

19. branding
new masterpage, new design, new ‘metro’ clean cut look and
change of layout

20. branding
• Changes to the general look and feel of 2013
• Additional top navigation
• Terminology changes
• Changes to the standard buttons such as Site Actions

21. You can brand SharePoint
2010 or 2013 anyway you
want. If you want 2010 to look
Sam Dolan like 2013, than why not, it
would help end users
transition between versions.

30. upgrade considerations
• SharePoint Social: 2010 or 2013
• You cannot run cross service applications between a 2010 and 2013 farm
• Only install the service applications you need in 2010 so you don’t have to
upgrade them to 2013 (install them when you actually need to implement them)
• Start in 2010 and move very quickly to 2013 but stay in 2010 mode

31. what to take away
• Re-evaluate requirements from each phrase
• Understand the features you want in 2010 and what they do in 2013
• Understand what the features can do in 2013 that they can’t do in 2010
• User the changes to your advantage (we listened to you and we added this
feature) ;-)
• Brand your site to what you want it to look like with 2013
• There are going to be differences so try and minimise them as much as possible

32. so when do you upgrade?

33. so when do you upgrade?
it depends!