SharePoint 2010 overview

30
Overview

Transcript of SharePoint 2010 overview

Page 1: SharePoint 2010 overview

Overview

Page 2: SharePoint 2010 overview

Meet changing

business needs

Manage IT costs

and complexity

Drive insight from complexity

Work with customers and partners

Embrace Millennial work styles

Comply with regulations

Integrate line-of-business systems

Provide scale agility

Enable innovation

Protect intellectual property

Page 3: SharePoint 2010 overview

Business Collaboration Platform

Page 4: SharePoint 2010 overview

Single Platform

Anywhere Access

Rich User Experience

Page 5: SharePoint 2010 overview
Page 6: SharePoint 2010 overview

Participation Anywhere

Social Connections

Informal Knowledge

Page 7: SharePoint 2010 overview
Page 8: SharePoint 2010 overview

Management Efficiency

Flexibility and Compliance

User-centric

Page 9: SharePoint 2010 overview
Page 10: SharePoint 2010 overview
Page 11: SharePoint 2010 overview
Page 12: SharePoint 2010 overview

Editing conflict

resolved by merge

engine

Synchronizing only

updated sections

(deltas)

Local copy saved for

offline access

Page 13: SharePoint 2010 overview

Enterprise Deployment

Knowledge Amplification

Better Answers, Faster

Page 14: SharePoint 2010 overview
Page 15: SharePoint 2010 overview
Page 16: SharePoint 2010 overview

Data interaction

Organizational Effectiveness

Decision Making

Page 17: SharePoint 2010 overview

SharePoint Insights

Page 18: SharePoint 2010 overview

SharePoint Insights

Page 19: SharePoint 2010 overview

Solution Deployment

Data Connectivity

User-Driven Solutions

Page 20: SharePoint 2010 overview
Page 21: SharePoint 2010 overview

Artist Tracker > Artists

Artists

Contracts Artist Name Address City State

Artist

Mandible

Artist Name: Mandible

Agent: Andrew Datars Quartet

Stuck in the Mud

Tastes like chicken

Deathrattle

Jay Hamlin Trio

Down on the Bayou

Concourse

Down on the Bayou

Concourse

Concourse

Jay Hamlin Trio

My Artists

Page 22: SharePoint 2010 overview

IT Productivity

Deployment Flexibility

Scale with Governance

Page 23: SharePoint 2010 overview
Page 24: SharePoint 2010 overview

©2009 Microsoft, Microsoft Dynamics, the Office logo, and Your potential. Our passion. are trademarks of the Microsoft group of companies. The information herein is for informational purposes only and

represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on

the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR

STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

••

•••

•••

Page 25: SharePoint 2010 overview

Sentri applies an agile approach adapting the best features of SCRUM and Configuration to projects where early success must be demonstrated yet requirements may not be fully known. The approach is lightweight and manages development work through frequent and small releases. It emphasizes working solution as the primary measure of progress.

The approach is founded on solid and proven software engineering best practices

• Test driven development, continuous integration, re-factoring, standards-based implementation, build on object-oriented analysis and design and service oriented architectures.

Customer Benefits

• Specifically designed to efficiently cope with change. Avoids high cost of change management and inflexible solutions in traditional approaches. Involves stakeholders in the evolution of the solution.

• Customer satisfaction by rapid, continuous delivery of useful software.

• Focuses on producing prioritized, usable features.

• Identifies and communicates problems early.

• Quality of resulting solution is greater than with traditional approaches.

How Does Sentri Agile Development Work?

• Small teams of highly skilled, multi-disciplined Consultants.

• A series of iterations (in the order of weeks not months) where each sprint is a mini Configuration Cycle.

• Visible, usable increments to deployed solution.

• Value is placed on real-time and ongoing communication as opposed to heavy weight documentation.

• Usage of modern lightweight development tools to allow ‘quick’ change.

• Regimented opportunities for change management to allow prioritization and focus on delivery.

Page 26: SharePoint 2010 overview

Functionality Intranet

Phase I II III

Collaboration

Real-Time Presence and Communication √

Social Networking Web Part √ √

Standard Site Templates √ √

Wikis √ √ √

Blogs √ √

People and Groups Lists √ √

Calendars √ √

Time Tracking √ √ √

Real-time Links and Technical Support (e.g. Live Link)

√ √

Email Integration √ √ √

SMS/MMS Integration √ √

Task Coordination and Project Activity √ √

Surveys √ √

DOA and P&L Collaboration √ √

Overview Dashboard √ √

Issue Tracking √ √ √

Page 27: SharePoint 2010 overview

Functionality Intranet

Phase I II III

Portal My Site Personal Site √ √

Content Syndication √

Privacy & Security √ √

Site Directory √ √

User Profiles and the Profile Store √ √

Audience Targeting √ √ √

Site Manager √

Mobile Device Support √ √

Portal Site Templates √

Portal Sites and Documents Roll-up Web Parts √ √ √

Colleagues and Memberships Web Parts √ √

Integration with MS OFFICE (Access, Excel, PowerPoint, and Word)

√ √ √

Integration with Outlook √ √ √

Demonstration Links √

Integration with Portal Designer Tools √ √

Page 28: SharePoint 2010 overview

Functionality Intranet

Phase I II III

Search

User Interface √ √

Search Results √ √

Enterprise Content Sources √ √

Relevance √ √

Administration and Management √ √

Indexing Controls √ √

Security √ √ √

People Search √ √

Search & Replace √

Business Data Search √ √

Page 29: SharePoint 2010 overview

Project Initiation, Planning

Requirements Analysis

Requirements Prioritization

Non-functional Requirements Analysis

Create Initial Infrastructure

Requirements Workshops Audience / Users Needs Analysis

Week X Week X

SharePoint Architecture Fit / Gap analysis

Week X

Phase I

Implementation Release 1

Iteration1

Iteration 2

• The project is organized in a series of releases focusing on delivering usable and prioritized functionality incrementally through short iterative cycles

• Specific timeline and functionality will be created as part of project initiation and planning

• Project plan (timeline and functionality) for each iteration as well as release cycle will be adjusted throughout, allowing user adoption and validation

Week X

Implementation Release 2

Iteration 3

Iteration 4

Initial iterations will be 2-3 weeks in duration.

It is important to validate and get

feedback early and set stage for adoption

success.

Iteration 5

Phase II

Week X

Implementation Release 3

Iteration 6

Iteration 7

Iteration 8

Phase III

R2 iterations will be 3-3 ½ weeks in duration.

R3 iterations will be 3-3 ½ weeks in duration.

Week X

Production Release

Update Initial Infrastructure

Week X QA

Create / Update Production Infrastructure

Create near-production ready Infrastructure

Week X QA

Week X QA

Page 30: SharePoint 2010 overview

•Schedule a detailed requirement analysis session/s •Provide a high level understanding & a “Solution approach document (includes business goals/milestones, design, development, QA & deployment process)” •Provide a SOW based on our understanding, effort estimation with pricing.