John Stover presented at a technology conference on SharePoint: the good, the bad, and the ugly. He began by explaining what SharePoint is and how it is commonly used today. He then discussed how to plan for SharePoint success by defining objectives, requirements, workloads, and technical environments. Stover also provided recommendations on training, support, and governance. He wrapped up by emphasizing the importance of testing and providing examples of how not to implement SharePoint and ensure failure.

1. 2011 Technology Conference & Expo
SharePoint:
The good, the bad, and the ugly
12/7/11 3:15PM
Hub Tag: #Tech11 LS2
John Stover

2. Agenda
• What is SharePoint?
• How is it being used today?
• Plan for success
• Ensure failure
• Discussion

4. What is
SharePoint?

5. What is SharePoint?
This is still a question I get asked when out
visiting customers… It’s kind of magical in a
certain way. It’s a really special kind of
product… It’s kind of like an operating
system…
- Steve Ballmer, CEO, Microsoft

6. [SharePoint is] a general purpose infrastructure
that connects people to people and people to
information.
- Steve Ballmer, CEO, Microsoft

7. SharePoint
Today

9. SharePoint in Associations

10. What is the
#1
Critical Success Factor?

11. Do Not Implement SharePoint

12. SharePoint is easy
• Easy to install
• Easy to use
• Easy to configure
• It’s in the cloud

13. Value
Technology provides
no benefits on its own;
it is the
application of technology
to business opportunities
that produces ROI.

14. Define
specific solutions
with
specific objectives

15. Understand your Objectives

16. Objectives should support mission
Direct or Indirect

17. Find a balance.
Beware paralysis by analysis.

18. Bad Requirement
REQ 301.1: The system's
capacities shall meet or exceed
minimum system capacity
requirements set forth in REQ
290.45 of this title (relating to
Minimum System Capacity)

19. Three C’s
•Capture
•Clarify
•Confirm

20. Don’t just Showcase Features

21. More Bad Requirements
• Support multiple languages
• Provide workflows
• Provide distributed content
authoring
• Provide robust security
• Include Social
• Must Be Mobile

22. Better Requirements
• Provide a Project Calendar with high-level
deadlines and deliverables
• Visually display task assignments and
deadlines
• Email alerts of major document revisions to
executive team

23. What environment do I need?

24. Workload
Data
Reliability

25. Technical Planning
1. Support
2. Downtime
3. Capacity
4. Availability
5. Disaster

26. Calculate Workload?
• Average daily RPS (Requests Per • Web Browser - Social Interaction
Second) • Web Browser - General Interaction
• Average RPS at peak time • Web Browser - Office Web Apps
• Number of unique users per day • Office Clients
• Average daily concurrent users • OneNote Client
• Peak concurrent users at peak time • SharePoint Workspace
• Total number of requests per day • Outlook RSS Sync
• Expected workload distribution • Outlook Social Connector
• Web Browser - Search Crawl • Other interactions(Custom
• Web Browser - General Collaboration Applications/Web services)
Interaction

28. Audience Considerations
• Staff Only – Internal
• Staff Only – Remote Access
• Partners Customers Members
• Internet Sites
• Hybrid? Staff, Members, Customers, and
Anonymous Users?
• Browser Types?
• Mobile?

29. Performance and Reliability
• Availability?
–99.9%, 99.99%, 99.999%
• Responsiveness?
–3 seconds?
• Resource Utilization?
–CPU and Available Memory

30. Two Tier
Web
&
Apps
SQL

31. SharePoint can run on a Single Server

32. Virtual or Physical
SQL Server performance tests indicate that the
same throughput (compared to a physical
server) can be achieved in a guest virtual
machine at a cost of slightly increased CPU
usage
- Plan Virtual Architectures, Microsoft TechNet

33. Do Not Host

34. Simple Plan for Success
Pilot
Test
Optimize

35. Staffing

36. Roles?
• End User
• Site Owner
• Site Collection Administrator
• Help Desk
• Farm Administrator
• Evangelist
• Developer
• Architect

37. Training
&
Mentoring

38. Typical Training
A significant volume of
information is transmitted from
one to many in a short time with
limited opportunity to apply and
limited personalization.

39. Contextual Solution-Based Training
• Skill-Building
• Just in Time
• Personalized
• Based on YOUR solution
• Accessible when you need it

40. Mentoring
• Understand Capabilities
• Knowledge vs skills
• Share information
• Broader perspective

41. Ongoing Issues

43. General Recommendations

44. Build a
coordination team with
cross-functional
representatives

45. Governance:
Who can do
what where?

46. SharePoint can
start simple…
and can turn into an
enterprise project.

47. If you still need ideas to FAIL
• Don’t Use Roles
• Don’t Use SharePoint Security
Groups
• Make Everyone an Owner
• Don’t Test. Better yet, rely on others
to test.
• Migrate EVERYTHING

48. Even more ways to FAIL!
• Duplicate Content
• Ignore Content Types
• Ignore Metadata
• Don’t use Templates
• SharePoint exists in a vacuum

49. Thoughts?

50. Contact Information
John Stover
CEO and Principal Consultant, Invenio
john@invenio-partners.com
540-686-1686
Invenio-Partners.com