15. Get-SPName
15
MCMS 2002
SharePoint Portal Server 2003
Windows SharePoint Services (WSS) 2.0
Microsoft Office SharePoint Server 2007
Windows SharePoint Services (WSS) 3.0
18. Newborn (2001)
18
3 distinct products
Developed in isolation
Built to meet distinct business
needs:
Portals
Search
Collaboration
Content Management
19. Child (2003)
19
Cohesive product (SharePoint)
begins to emerge
SPS & STS teams merged in 2002
Takes a few releases for
merger to be complete
SP & CMS teams merged in 2004
20. Adolescent (2007)
20
The product's relationship with
Office is pivotal in its history
Important for integration
Staying inside the Office suite
didn't really make sense
22. Adult (2010)
22
Beware of server-side code
And don’t touch the hive !
Or the database for that matter
Sandbox solutions
Primitive implementation of apps
Focus on client-side dev
23. SP2010 Was Truly V1
23
Replaced Shared Service Provider
(SSP) with Service Applications
Tighter Office integration
Vastly improved Search
Client side scripting
Web Services
24. SP2010 Was Truly V1
24
PowerShell
Integration of 2 distinct products
developed by 2 different teams
SP2010 brought Server / Foundation
branding
Relevant name – finally !
25. Adult (2013)
25
Service applications blown out
Workflow
WAC
Search
Distributed Cache
SP social arrived
Quickly left the party (Yammer)
Forms are back ?
28. SPToday
28
Is an on-prem implementation still required?
In 2003 our view of the "cloud" was this:
29. SPToday
29
“I think we're going to live in a hybrid world for a
number of years to come and ... folks that have been
in this industry for a while get that and are under no
illusions that hybrid is going to be the reality for a lot
of established businesses today and it's just what
we're going to be dealing with for some time.”
- Chris Johnson, Group Product Manager Office 365
Microsoft Cloud Show E034
30. Hybrid: The New Paradigm
30
Why? (many reasons)
Customers want new features
Only available in the cloud
Customers can't upgrade
Because of their customizations
Many can't even migrate
Some are still on 2007 even though
mainstream support has ended
Data residency issues
31. SPFuture
31
Jeff Shuey predicted (2011) :
“…there will be a boom in solutions that look
nothing like SharePoint does today. SharePoint will
reach it’s true potential when it becomes intrinsic
and invisible to the applications we use every day.”
- AIIM, “The Future of SharePoint (and Windows
7 Phone)”
32. SPFuture: Today’s Problems
32
SP is huge
Does many many things
Unwieldy deployments
Content Sprawl
Fancy fileshare
Very customizable
35. SPFuture: Prescriptions
35
Needs to do less to be more
Microsoft tried to
Build the world
Shift the paradigm (metadata)
But the world wasn’t ready for it
Is Microsoft doing this again with Cloud?
36. SPFuture: Customer Tips
36
“Which best practice today is tomorrow’s deprecated feature?”
- Mark Rackley
If Microsoft signals that something is going
away avoid it (if possible)
Exchange Public Folders
SharePoint Designer
InfoPath
Farm & Sandbox Solutions
40. SPBusiness
40
Examples of non-aligned requests from
the business
Move search box to the left 20px
Make SP look unlike SP
Don’t call it “SharePoint”
46. SPAdmin
46
SP IT Pro’s are not redundant
Why? Hybrid
Administration is crucial
Many moving parts
Everything is connected
47. SPAdmin
47
Admins need strong dev skills
#1 reason = PowerShell
High-level understanding of SP dev:
Technologies
Techniques
48. SPDev
48
“The number one mistake a developer can make is
opening Visual Studio before investigating what
can be done out of the box.”
- Mark Rackley
49. SPDev
49
Devs are not redundant
Despite cloud limitations
Many new client-side
opportunities
Development is crucial even though
Farm solutions are disappearing
Sandbox solutions are deprecated
App model is still wobbly
50. SPDev
50
Devs need strong Admin skills
Lots of moving parts to track
How does everything work together?
Devs need strong SP knowledge
To avoid re-creating the wheel
52. Why Collaborate?
52
What happens when Devs, Admins, and
the Business don’t work together?
Mess
Confusion
Zero goal-alignment
Delays
Hostile workplace
Working together isn’t easy, but it’s worth it
53. Playing Together
53
Dysfunctions of a Team
1. Status & Ego :: Focus on Results
2. Avoid Accountability :: Promote Standards
3. Lack of Commitment :: Increase Engagement
4. Fear of Conflict :: Resolve Conflicts as they arise
5. Absence of Trust :: Promote Trust & Vulnerability
54. Playing Together
54
Trust is something that:
We ought to give freely to others
We should expect to be earned (from others)
Can be gained through vulnerability
55. Playing Together
55
Beyond Trust commit to being:
Transparent
Willing to engage
Able to call people out
Eager to set high standards
Results oriented
56. Recap
56
Recognize competing interests
Attempt to resolve the differences
Observe the product’s development
Work to follow & adapt
Hybrid is the new paradigm (whether msft likes it or not)
http://www.microsoftcloudshow.com/podcast/Episodes/034-discussing-on-premises-sharepoint-sharepoint-online-in-office-365-and-the-state-of-sharepoint-with-fpweb-s-rob-lemear-iv