Your SlideShare is downloading. ×
  • Like
Planning for SharePoint 2013 in our 2010 project
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Planning for SharePoint 2013 in our 2010 project



Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Site tmeplates
  • Site tmeplates
  • Site tmeplates
  • Site tmeplates
  • Site tmeplates
  • Site tmeplates
  • Site tmeplates
  • Site tmeplates
  • Site tmeplates
  • Site tmeplates
  • Site tmeplates


  • 1. planning for 2013 in our 2010 project alex pearce
  • 2. meDirector: BFC NetworksSharePoint MVP since 2008Twitter: @alex_pearcePersonal 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. whywhy 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. terminologynew 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
  • 9. terminology - appwhat does app mean to different people
  • 10. featuresnew feature such as communities, improved social, higher integration with exchange and windows
  • 11. demo – communities
  • 12. site templates
  • 13. demo – site templatedifferences between the 2010 team template and the 2013 team template
  • 14. demo – skydriveoffline sync to the desktop with skydrive
  • 15. brandingnew masterpage, new design, new ‘metro’ clean cut look and change of layout
  • 16. branding• Changes to the general look and feel of 2013• Additional top navigation• Terminology changes• Changes to the standard buttons such as Site Actions
  • 17. You can brand SharePoint 2010 or 2013 anyway you want. If you want 2010 to lookSam Dolan like 2013, than why not, it would help end users transition between versions.
  • 18. 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
  • 19. 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
  • 20. so when do you upgrade?
  • 21. so when do you upgrade? it depends!