2011 Technology Conference & Expo                  SharePoint:            The good, the bad, and the ugly               12...
Agenda• What is SharePoint?• How is it being used today?• Plan for success• Ensure failure• Discussion
What isSharePoint?
What is SharePoint?This is still a question I get asked when outvisiting customers… It’s kind of magical in acertain way. ...
[SharePoint is] a general purpose infrastructurethat connects people to people and people toinformation.- Steve Ballmer, C...
SharePoint  Today
SharePoint in Associations
What is the           #1Critical Success Factor?
Do Not Implement SharePoint
SharePoint is easy• Easy to install• Easy to use• Easy to configure• It’s in the cloud
Value   Technology provides no benefits on its own;          it is theapplication of technologyto business opportunities  ...
Define specific solutions        withspecific objectives
Understand your Objectives
Objectives should support mission        Direct or Indirect
Find a balance.Beware paralysis by analysis.
Bad RequirementREQ 301.1: The systemscapacities shall meet or exceedminimum system capacityrequirements set forth in REQ29...
Three C’s•Capture•Clarify•Confirm
Don’t just Showcase Features
More Bad Requirements     • Support multiple languages     • Provide workflows     • Provide distributed content       aut...
Better Requirements• Provide a Project Calendar with high-level  deadlines and deliverables• Visually display task assignm...
What environment do I need?
WorkloadDataReliability
Technical Planning1.   Support2.   Downtime3.   Capacity4.   Availability5.   Disaster
Calculate Workload?•   Average daily RPS (Requests Per       •   Web Browser - Social Interaction    Second)              ...
Audience Considerations• Staff Only – Internal• Staff Only – Remote Access• Partners Customers Members• Internet Sites• Hy...
Performance and Reliability• Availability?  –99.9%, 99.99%, 99.999%• Responsiveness?  –3 seconds?• Resource Utilization?  ...
Two TierWeb &AppsSQL
SharePoint can run on a Single Server
Virtual or PhysicalSQL Server performance tests indicate that thesame throughput (compared to a physicalserver) can be ach...
Do Not Host
Simple Plan for SuccessPilotTestOptimize
Staffing
Roles?•   End User•   Site Owner•   Site Collection Administrator•   Help Desk•   Farm Administrator•   Evangelist•   Deve...
Training    &Mentoring
Typical TrainingA significant volume ofinformation is transmitted fromone to many in a short time withlimited opportunity ...
Contextual Solution-Based Training• Skill-Building• Just in Time• Personalized• Based on YOUR solution• Accessible when yo...
Mentoring• Understand Capabilities• Knowledge vs skills• Share information• Broader perspective
Ongoing Issues
General Recommendations
Build acoordination team with   cross-functional   representatives
Governance:Who can dowhat where?
SharePoint can   start simple…and can turn into an enterprise project.
If you still need ideas to FAIL• Don’t Use Roles• Don’t Use SharePoint Security  Groups• Make Everyone an Owner• Don’t Tes...
Even more ways to FAIL!•   Duplicate Content•   Ignore Content Types•   Ignore Metadata•   Don’t use Templates•   SharePoi...
Thoughts?
Contact Information       John Stover        CEO and Principal Consultant, Invenio       john@invenio-partners.com        ...
Success with SharePoint
Success with SharePoint
Success with SharePoint
Success with SharePoint
Upcoming SlideShare
Loading in …5
×

Success with SharePoint

429 views
342 views

Published on

ASAE Technology Conference 2011.
Conversation that Matters: SharePoint - Good, the Bad, and the Ugly

Presenter: John Stover

Wednesday December 7, 3:15 – 4:30 pm

In this highly conversational session, John discusses SharePoint implementation best practices. These are often best learned and easily defined when things go wrong. You are invited to share your stories as well as lessons learned. Help those currently in the beginning or in the midst of SharePoint implementations.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
429
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Success with SharePoint

  1. 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. 2. Agenda• What is SharePoint?• How is it being used today?• Plan for success• Ensure failure• Discussion
  3. 3. What isSharePoint?
  4. 4. What is SharePoint?This is still a question I get asked when outvisiting customers… It’s kind of magical in acertain way. It’s a really special kind ofproduct… It’s kind of like an operatingsystem…- Steve Ballmer, CEO, Microsoft
  5. 5. [SharePoint is] a general purpose infrastructurethat connects people to people and people toinformation.- Steve Ballmer, CEO, Microsoft
  6. 6. SharePoint Today
  7. 7. SharePoint in Associations
  8. 8. What is the #1Critical Success Factor?
  9. 9. Do Not Implement SharePoint
  10. 10. SharePoint is easy• Easy to install• Easy to use• Easy to configure• It’s in the cloud
  11. 11. Value Technology provides no benefits on its own; it is theapplication of technologyto business opportunities that produces ROI.
  12. 12. Define specific solutions withspecific objectives
  13. 13. Understand your Objectives
  14. 14. Objectives should support mission Direct or Indirect
  15. 15. Find a balance.Beware paralysis by analysis.
  16. 16. Bad RequirementREQ 301.1: The systemscapacities shall meet or exceedminimum system capacityrequirements set forth in REQ290.45 of this title (relating toMinimum System Capacity)
  17. 17. Three C’s•Capture•Clarify•Confirm
  18. 18. Don’t just Showcase Features
  19. 19. More Bad Requirements • Support multiple languages • Provide workflows • Provide distributed content authoring • Provide robust security • Include Social • Must Be Mobile
  20. 20. 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
  21. 21. What environment do I need?
  22. 22. WorkloadDataReliability
  23. 23. Technical Planning1. Support2. Downtime3. Capacity4. Availability5. Disaster
  24. 24. 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
  25. 25. Audience Considerations• Staff Only – Internal• Staff Only – Remote Access• Partners Customers Members• Internet Sites• Hybrid? Staff, Members, Customers, and Anonymous Users?• Browser Types?• Mobile?
  26. 26. Performance and Reliability• Availability? –99.9%, 99.99%, 99.999%• Responsiveness? –3 seconds?• Resource Utilization? –CPU and Available Memory
  27. 27. Two TierWeb &AppsSQL
  28. 28. SharePoint can run on a Single Server
  29. 29. Virtual or PhysicalSQL Server performance tests indicate that thesame throughput (compared to a physicalserver) can be achieved in a guest virtualmachine at a cost of slightly increased CPUusage - Plan Virtual Architectures, Microsoft TechNet
  30. 30. Do Not Host
  31. 31. Simple Plan for SuccessPilotTestOptimize
  32. 32. Staffing
  33. 33. Roles?• End User• Site Owner• Site Collection Administrator• Help Desk• Farm Administrator• Evangelist• Developer• Architect
  34. 34. Training &Mentoring
  35. 35. Typical TrainingA significant volume ofinformation is transmitted fromone to many in a short time withlimited opportunity to apply andlimited personalization.
  36. 36. Contextual Solution-Based Training• Skill-Building• Just in Time• Personalized• Based on YOUR solution• Accessible when you need it
  37. 37. Mentoring• Understand Capabilities• Knowledge vs skills• Share information• Broader perspective
  38. 38. Ongoing Issues
  39. 39. General Recommendations
  40. 40. Build acoordination team with cross-functional representatives
  41. 41. Governance:Who can dowhat where?
  42. 42. SharePoint can start simple…and can turn into an enterprise project.
  43. 43. 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
  44. 44. Even more ways to FAIL!• Duplicate Content• Ignore Content Types• Ignore Metadata• Don’t use Templates• SharePoint exists in a vacuum
  45. 45. Thoughts?
  46. 46. Contact Information John Stover CEO and Principal Consultant, Invenio john@invenio-partners.com 540-686-1686 Invenio-Partners.com

×