1 / 26

SharePoint Worst Practices: Setting the stage for disaster …

SharePoint Worst Practices: Setting the stage for disaster …. Dan Usher 17 September 2009. Agenda. Introductions Scenario at Hand Bad Practices and Pain Points Proper Approaches Conclusions. Who We Are …. Dan Usher Associate at Booz Allen Hamilton, Inc.

imani-key
Download Presentation

SharePoint Worst Practices: Setting the stage for disaster …

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SharePoint Worst Practices:Setting the stage for disaster… Dan Usher 17 September 2009

  2. Agenda • Introductions • Scenario at Hand • Bad Practices and Pain Points • Proper Approaches • Conclusions

  3. Who We Are… • Dan Usher • Associate at Booz Allen Hamilton, Inc. • SharePoint Infrastructure Engineer and Architect • MCP, MCTS, Security+ • Who are you?

  4. What's this talk about? • SharePoint in the Wild • SharePoint as a Collaboration and Development platform… • Considerations for Frameworks and Governance • What to avoid and what definitely doesn’t work • Full Steam Ahead… Turning the ship around…

  5. Situation • It’s 8 AM on Wednesday morning and SharePoint seems to be a mess… • Users can’t authenticate to the system… • New software patches were pushed over the weekend through SUS… • The development team pushed new software updates out onto the production servers from their dev laptop virtual machines… • The Infrastructure team changed the switch port settings… • DNS server IP addresses were changed… All this happened on one day?!?!

  6. Aye Carumba! Source: http://go.spdan.com/homerscream

  7. SharePoint - How'd we get here? • Did we have a plan in place? • Anything for Development Guidelines? • Anything for Architecture? • Anything for Implementation? • How about change management? • Did you have a vision or business case for the use of SharePoint in place? • Did you have a visioning group work to define needed capabilities and solutions?

  8. What have we done? :-o • Lack of Governance surrounding several key areas: • Development Guidelines • Infrastructure Processes • Architecting for the future • Deployment to the user community • Change Control and Configuration Management

  9. Lack of Development Guidelines • Disposing of Objects improperly • Features, what’s a feature? • Solutions, let’s just deploy it all scattered • Assembly Deployment (GAC vs. bin) • CAS • Source Control Policy • Test Driven Development • Nunit • TypeMock

  10. Return value = null • Zero documentation or implementation guides • We don’t need no stinkin’ source control • Missing QA / Test / Staging • Deploying Code directly to production • Realizing the difference between site definitions, templates and master pages…

  11. Infrastructure Processes? • Unscheduled Maintenance Time • Deploying code without testing in a staging environment • Disaster Recovery

  12. Where’s Central Admin? • Not knowing your tool sets and how to use them… • Stsadm • Powershell • SP Admin Toolkit • PSConfig • SQL Analyzer & Maintenance Plans • Patching Approach… • Is there one?

  13. Turning the ship around… • Approach • Planning • Governance • Documentation • Execution

  14. The Approach • What’s the problemwe’re trying to solve? • Define the Vision • Project Milestones • Define Business Rules, Processes, and Requirements

  15. Cleared for Approach • Trusted Sources on approaches • Ben Curry - @curryben • Bill English - @minnesotabill • Todd Bleeker - @toddbleeker • Joel Oleson - @joeloleson • Andrew Connell - @andrewconnell • Eric Shupps @ericshupps • Rob Foster @lespaulrob • #SamePageAlliance on Twitter • RuvenGotz - @ruveng • Paul Culmsee - @paulculmsee • Andrew Woodward - @andrewwoody • Dux Sy - @meetdux

  16. Planning • Start off with the governance checklist… • http://go.spdan.com/xeurd • Use the sample project plans… • http://go.spdan.com/hmewo • Firm up your stake holders and work to define solutions that meet their needs… • Hire a SharePoint consultant to assist…

  17. Architecting for the future… • Vision… • Use cases… • Planning the enterprise taxonomy and logical architecture… Source : http://bit.ly/sps-ref-wssLA

  18. Defining the Framework • Remaining rigidly flexible for change… • Planning for Data Partitions and Software Boundaries… • Disaster Recovery - both big and small • Defining governance and use of the system. • Site Quotas • MySites • Site Creation Process • User Permissions • SharePoint Designer • Disaster Recovery Plan

  19. Governance • Roles and Responsibilities • Business Rules and Policies • Software Development Guidelines • Infrastructure Implementation and Maintenance Processes • Architecture • System Usability and User Acceptance • Change Management • Training

  20. Documentation • Develop Use Cases to test against • Regression Testing Plan – Test all cases you create • QA • Use the architecture planning documentation examples available from Microsoft - http://go.spdan.com/yfeqp

  21. More Documentation • SharePoint Online development guide - http://go.spdan.com/cmzbm • SharePoint App Dev Guidance - http://go.spdan.com/sp-dev-aug09 • Implementation Guides • Communications • Training • Onboarding • User Documentation

  22. Execution • Making sure that stakeholders, users, designers and developers are going in the same direction • Visioning Team • Business Requirements and Solutions Development • Change Control Board • Project Plan & Milestones

  23. Defining a Framework for Success • Figure out what the system will be doing before deployment… cast a vision and stick to it! • Ensure process and governance are developed and used not only for Developers and Designers, but for the end user. • Keep the user base informed, don’t expect them to go in the web part gallery on a regular basis - explain what’s new!

  24. Questions?

  25. SharePint Anyone?

  26. And that’s a wrap… • Follow me on Twitter – twitter.com/usher • Follow my blog – http://www.sharepointdan.com • IM? • gTalk danusher79 • Live danusher@live.com • E-mail: dan@spdan.com

More Related