SharePoint can be used as a platform for building business applications. It provides capabilities for infrastructure, content management, and user interfaces. There are different strategies for developing applications on the SharePoint platform, including connecting, extending, and building on top of SharePoint. Information architecture and governance are also important considerations for the platform. Composite applications that combine multiple services can help organizations rapidly respond to changing business needs.
6. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
9. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
10. The “clock speed” of business change has increased
Before After
Predictability and stability Rapidly changing needs
Manageable change Unexpected change
Enough time to react Shorter windows of opportunity
Long term planning was enough Planning for the unknown
How do we respond to
these changing needs?
11. Tension between business and IT
EMPOWERMENT How do we CONTROL
Access
Agility
break this Governance
Management
Adaptability Centralization
Self-service
Innovation
paradox? Consolidation
Cost controls
12. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
14. Mind the “Value” Gap
The value traditionally What is required by the
seen from infrastructure business need
Standardized activities Innovation
Utility Business value
Non differentiating Differentiation
The value gap
15. The “Value” Gap
Platform for Platform for
productivity business solutions
SharePoint Business domain
SharePoint
Technical gap Business domain app
16. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
17.
18. Platform Capabilities
Feature Areas The Big Three
Search 1. Infrastructure
Workflow 2. Content Management
Service Applications 3. User Interface
Extensible Service Infrastructure
Administrative Features
Business Intelligence
Composite Applications
SharePoint Designer and Visio
support for workflows
19. Platform - Infrastructure
• ASP.NET HTTP Pipeline
• Application Security
• Packaging and Deployment
• Service Applications
20. Platform – Content Management
• External Data
• Business Intelligence
• Search
• Workflow
• Data Model User Interface
• Social Features
• Metadata Management
22. Example: Partners and SharePoint ECM
Foundational ECM
Supplemental ECM
Embrace and Extend Workloads with Partners
* E-mail Archiving provided by Exchange
23. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
24. Platform Strategies
• Solutions that Integrate with
Connect SharePoint so two products work
together
• Integrated solutions that extend
Extend SharePoint’s offering by adding
“New” SharePoint capabilities
• Applications built on top of
Build On SharePoint platform that leverage
multiple SharePoint capabilities
25. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
26. Information Architecture
Site and Site Collection Structure
Content Modeling and Content Type Definitions
Metadata Schemas and Taxonomy Management
Search Integration
Managed Administration
27. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
28. Back to Empower vs. Control
How should capabilities be divided between
Central IT and Business IT?
How should the two teams be constructed?
Standardized activities Innovation
Utility Business value
Non differentiating Differentiation
29. SharePoint Applications
People-centric
Surfacing within the familiar user interface
of the Office and SharePoint platform
Collaborative
Helping groups of people participate
in ad-hoc and unstructured processes that
largely occur outside enterprise systems
Composite
Helping respond rapidly to business needs by
combining multiple services and functionality in
role-based solutions, in many cases without code
30. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
32. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
33. Composite Applications
NO-Code Use Enterprise Keep Control
Solutions Data Everywhere Over End User
• Browser-Based • Expose Enterprise Solutions
Customizations Data using • Manage Custom
• SharePoint Designer Business Code with Sandbox
Solutions Connectivity Solutions
• Create Workflows Services
• Manage Desktop
• Browser • Surface Enterprise Solutions with Viso,
Data in Outlook, Forms, Access
• SharePoint
Word, Workspace Services
Designer
• Provide Full Read • Deployment
• Visio
and Write Access, packages provide
• Use Access Services offline and online
to publish databases deployment online
• Enable SEARCH or on premise
across Enterprise • SharePoint
data systems Application
marketplaces
34. Composite Applications in SharePoint
Leveraging a rich set of building blocks across many scenarios
LOB Human
integration workflow
Document Reporting
processing and
Analysis
Application Web sites
experience
35. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
36. Solution Thinking
Content-Centric People-Centric
Applications Applications
--When it’s the --When it’s the
CONTENT PEOPLE/ROLE
that matters that matters
It’s
BOTH, actu
ally.
37. The Puzzle Pieces
The Players on the Team
Why is there a Need for a Platform?
The Big Question… Build? or Buy?
The Value Gap
Out of the Box Perspectives
Build Strategies related to SharePoint
Information Architecture
Does a Platform need Governance?
Role that Users Play
Composite Applications
Solutions as a Type
Case Management
38. Case Management as a Type
A Framework Rich for Entity Life Cycle
for multiple Extensibility • Contract Lifecycle
application • Process Analytics Management
types • Rapid Creation/ • Product
Modification of the Development –
• Aggregation of Data Process Product Lifecycle
• Ad Hoc Workflow Mgmt
• Integrate with
• Structured process Physical Processes • Customer Lifecycle
Management
39. Case Management
• A Framework for multiple application types
• Horizontal and Vertical Business Solutions
– Professional Services
– Product Development and Manufacturing
– Research, Healthcare, Life Sciences, Insurance
– Issue Tracking for all
• Platform Leverage
– Document Sets, Content Types, Site framework
– People and Social Connection
– Workflow – Business Process Management
– Task Assignment and Tracking
– BCS connection to LOB data
General SharePoint strategy for building out features…. Base functionality Provide methods for partners to build out and up Consolidate (?) There is a limit to the feature “blanket” that Microsoft can apply during design/development time.
Connect – Content Embedding, Search, Single Sign-OnExtend – result is often building blocks custom web parts, workflow actions, list or site workflows, field types, event receivers, content types, information-management policies, search indexing pipeline, user-defined functions for Excel, etc.Build On -