Worst Practices of SharePoint 2010

1,030 views
885 views

Published on

In a perfect world, SharePoint systems are well planned with defined requirements, stakeholder approval, and methodology approaches. Oh, and unlimited budgets. But the reality of SharePoint implementations is deployments and operations are typically not what might be seen through rose-colored lenses.

In this session, you will learn what the instructors have seen in terms of worst practices and approaches for getting a system implementation and deployment back on track, as well as methods to fix and optimize operations that may not be addressing your system's current needs. For all of the things that can go wrong with your SharePoint implementation, one of the best things we can do is learn from others. From not accepting that implementing an established information architecture and having an available infrastructure are core tenets of every SharePoint installation to managing SLAs with your end users. Come to this class to hear not only worst practices, but also worst experiences.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,030
On SlideShare
0
From Embeds
0
Number of Embeds
76
Actions
Shares
0
Downloads
25
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Worst Practices of SharePoint 2010

  1. 1. Worst Practices ofSharePoint 2010
  2. 2. Thanks to Our Sponsors!
  3. 3. who are we? Scott Hoag ciphertxt
  4. 4. who’s that other guy? Dan Usher usher
  5. 5. and what about this guy?
  6. 6. introductions
  7. 7. a few ground rules…
  8. 8. housekeeping
  9. 9. agenda
  10. 10. whats this talk about?      
  11. 11. it’s also about…
  12. 12. SharePoint as a product      
  13. 13. SharePoint as a platform         
  14. 14. common challenges
  15. 15. common challenges triangle
  16. 16. it can boggle the mind…
  17. 17. what are your pain points?
  18. 18. technical challenges
  19. 19. business challenges    
  20. 20. social challenges  
  21. 21. typical user base
  22. 22. bad practices and painpoints
  23. 23. planning“If you have noplan, you plan tofail.”
  24. 24. technically speaking howd we get here?       vision business case
  25. 25. what didnt we do right?     
  26. 26. development disasters       
  27. 27. typical coding practices
  28. 28. more development disasters    
  29. 29. enterprise infrastructure processes Source Sean McDonough @spmcdonough 
  30. 30. operations and maintenance
  31. 31. knowing your tools
  32. 32. what’s in your IT Pro toolbox?
  33. 33. alternative approaches
  34. 34. turning the ship around… Approach Execution Planning Documentation Governance
  35. 35. the approach    
  36. 36. planning  http://go.spdan.com/xeurd  http://go.spdan.com/sp2010gov  http://go.spdan.com/hmewo  http://go.spdan.com/sp2010project
  37. 37. architecting for the future…Sources: http://bit.ly/sps-ref-wssLA http://go.spdan.com/kuouh http://go.spdan.com/2010tech
  38. 38. defining the framework       
  39. 39. misconceptions and gotchas  
  40. 40. diversity of governance
  41. 41. governance It’s not just a piece of paper
  42. 42. governance by committee
  43. 43. governance
  44. 44. service management
  45. 45. service management takeaways
  46. 46. documentation    http://go.spdan.com/efpxr  http://go.spdan.com/yfeqp
  47. 47. more documentation  http://go.spdan.com/cmzbm  http://go.spdan.com/sp-dev-aug09  http://go.spdan.com/dwyee   
  48. 48. execution    They can’t hear you if you’re not screaming
  49. 49. defining a framework for success
  50. 50. striving forward
  51. 51. at the end of the day
  52. 52. questions
  53. 53. evaluations
  54. 54. How to find us @usher @ciphertxt  http://www.sharepointdan.com  http://psconfig.com

×