sharepoint 2010 vs. sharepoint 2013 feature comparison

12
SharePoint 2010 vs. SharePoint 2013 Feature Comparison March 2013 ©2013 SUSAN HANLEY LLC

Upload: trankhue

Post on 11-Jan-2017

242 views

Category:

Documents


4 download

TRANSCRIPT

Page 1: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

SharePoint 2010 vs. SharePoint 2013

Feature Comparison

March 2013

©2013 SUSAN HANLEY LLC

Page 2: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

SharePoint 2010 vs. 2013

2

From a document collaboration perspective, the structures of both versions are the same – so if you create a metadata architecture for documents in 2010 it should be fully upgradable to 2013.

The most significant upgrades in document management are in the user experience – including drag and drop to upload documents and the ability to edit managed metadata in a datasheet view.

The primary differences are in the social experiences, especially with discussion boards. The 2013 discussion board (with Community features enabled) creates and engaging “Facebook-like” activity stream, which is far more user-friendly than the same feature in SharePoint 2010. The added visual appeal is important because getting people to use the discussion board instead of commonly used “who you know” networks will take some planning and effort. If the software is engaging and familiar it will help with “stickiness.”

The other significant improvement is search, which you will see in the examples on the next few pages.

Page 3: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

SharePoint 2010 vs. 2013 Feature Comparison |

Representative Examples

3

Business

Scenario

SharePoint 2010 SharePoint 2013

Document

Collaboration

• Support for enterprise content types and

shared metadata so that attributes and

structures can be maintained in one place

and shared across the enterprise, vastly

improving search results.

• No difference in approach for organizing

content so investment in defining content types

and metadata is fully leveraged in 2013.

• Several helpful user experience improvements in

the application of metadata, including the

ability to edit managed metadata in a datasheet

(spreadsheet) view.

• “Drag and drop” ability to upload documents to

SharePoint libraries (without having to open

library in “explorer view’).

Search • Comprehensive enterprise search with the

ability to use Boolean operators to create

search queries. For example: search for: cats

AND dogs.

• Wildcard search available. For example, as

search for ho* would find homes, horses,

houses, etc.

• Faceted search refiners to easily narrow

results based on metadata.

• Define search scopes to target to specific

collections of content.

• “Best bets” can be defined to force certain

results to the top of search results.

• Significant improvements in user experience.

• Visual display of contents as you hover in search

results.

• Best bets now called Promoted Results.

• Search remembers what you have previously

searched and clicked and displays these values

as query suggestions at the top of the results

page.

• Results show number of times a document has

been viewed.

• Results pages allows you to page through

PowerPoint presentations without leaving the

search results page.

• One click to “view in library.”

Page 4: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

SharePoint 2013 Benefits | Improvements in search start

when users type in the query …

4

Type-ahead and

recent personal

searches shown to

individual

Visibility in to

results you’ve

found before – to

help address “I

know I’ve found

that document

before” issues

Page 5: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

SharePoint 2013 Benefits | … and the experience is even

more productive during results

5

Hover over search

results to see

content without

having to leave the

results page.

View how many time this item has been

viewed by others

Step through

results and

content without

leaving the

search page to

be sure this is

the right

document.

Want to find

out where

the

document

came from?

One click to

the library.

Send a link to the document to

someone else right from search

results.

To get notified about updates to

the document, click to Follow

from search results

Open directly to the

page by clicking

from “Take a look

inside”

Page 6: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

SharePoint 2010 vs. 2013 Feature Comparison |

Representative Examples

6

Business

Scenario

SharePoint 2010 SharePoint 2013

Expertise

Location

• Support for user profile – both standard and

custom attributes

• People are searchable – and search can be

scoped to people

• Users define core areas of expertise in the

“Ask me about” column.

• Default people search displays most recent

documents authored by that user

• Follow people to see updates based on their

Newsfeed posts and what they are publishing

Social

Computing

• Very limited capabilities.

• Users can post a single status that is not

retained and not searchable.

• New status wipes out the old status so

statuses feel very static.

• Each user has a Newsfeed that is similar to a

Facebook activity stream.

• See stream of the entire organization or filter

based on topics and people you are Following.

• Post or reply in the stream using @mentions

and #hashtags.

• Activity posts are saved for as long as you

decide to retain them (most organizations align

this policy with email retention) and are

searchable.

• Follow #Hashtags to get notified when new

content relevant to your area of interest is

added.

• @mention someone to direct an activity post to

their attention (as in Twitter).

Page 7: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

Social Computing Examples | 2010 vs. 2013

7

Users can update a

personal status.

People who view

the profile page

can leave a note.

Some activities

surfaced in a

“Recent activities”

feed.

SharePoint 2010

SharePoint 2013

• Rich, familiar social

experience

• Status updates

saved and

searchable.

• Follow people,

documents, topics.

• Engage with others

in the feed.

• Indicate

“agreement” with

likes.

Page 8: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

SharePoint 2010 vs. 2013 Feature Comparison |

Representative Examples

8

Business

Scenario

SharePoint 2010 SharePoint 2013

Communities of

Practice

• Must configure an “out of the box” template

to align with community objectives.

• Community site is just an instance of a

standard team site – with similar

requirements for managing access and

assigning privileges.

• Simplistic discussion list.

• New “Community” site template completely

focused on conversations.

• Access very different from team sites – users can

observe conversations and then “join” a

community when they want to post.

• Community can allow anyone to join or can

require approval by a Moderator before

allowing someone to become a “Member.”

• Becoming a member means you are

automatically “Following” the community site.

• Member photos show up next to all posts.

• “Gamification” options to encourage

participation – points, badges, and a “top

contributors” leaderboard.

• Designated users can be “gifted” a badge – to

identify someone as an “Expert” or “Thought

Leader” so that discussion participants can

easily distinguish contributions.

• Ability to categorize conversations by topic with

an image – to create a welcoming environment

and encourage interaction.

Workflow • Several “built in” workflows with additional

options available in SharePoint Designer.

• Significant enhancements, including new ways

to create and visualize workflows.

• Existing 2010 workflows should upgrade.

Page 9: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

9

SharePoint 2013 | Communities Site template – visual

categories to organize content, see list of Members

“Roll-over”

message shows

activity by

category

Page 10: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

10

Out of the Box Discussion List

SharePoint 2010 vs. SharePoint 2013

SharePoint 2010

SharePoint 2013

Page 11: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

SharePoint 2010 vs. 2013 Feature Comparison |

Representative Examples

11

Business

Scenario

SharePoint 2010 SharePoint 2013

Collaborating

with others

outside the

workgroup on

individual

documents

• Difficult to do if the person not on the team

does not have access to edit the document

on the team site.

• Only the site owner can grant permissions.

• Author can create a “document workspace”

and invite the guest to edit, but then has to

publish the final document back to the main

site.

• “Share” button easily visible for any site and

document.

• Any user can invite someone to edit an individual

document “in place,” but all invitations are

approved by the site owner. (easier to

collaborate, but still controlled) This feature

makes it easier to collaborate with people

outside the immediate workgroup but requires

that site owners carefully manage permissions

when the collaboration is finished.

• Users who request access to a site have an

opportunity to explain why they need access so

that site owners can make better decisions about

whether or not to grant access.

Page 12: SharePoint 2010 vs. SharePoint 2013 Feature Comparison

SharePoint 2010 vs. 2013 Feature Comparison |

Representative Examples

12

Business

Scenario

SharePoint 2010 SharePoint 2013

Mobile Access • Teams can create mobile views for sites but

not necessarily for different types of mobile

devices..

• Optimized mobile browser experience - provides

a lightweight, contemporary view browsing

experience for users to navigate and access

document libraries, lists, wikis, and Web Parts.

• Device channels - you can render a single

published SharePoint site in multiple designs to

accommodate different device types.

• Business intelligence - SharePoint Server 2013

enables a user to view certain kinds of dashboard

content. This includes PerformancePoint reports

and scorecards, and Excel Services reports in iOS

5.0 Safari browsers on iPad devices.

• Office Web Apps - allows users to view Word,

Excel, and PowerPoint documents in mobile

browsers.

Branding

(creating a

custom look and

feel)

• Significant SharePoint knowledge required

to design the user interface for SharePoint

sites.

• The new features in a publishing site minimize

the amount of SharePoint knowledge that is

required to successfully design and brand a

SharePoint site.

• Professional web designers who know HTML,

CSS, and JavaScript already have the skills

necessary to design a SharePoint 2013 site – and

can use their preferred tools such as

Dreamweaver to create designs for SharePoint.