Dan Usher and Scott Hoag28 July 2012Microsoft, New York City, NY

Worst Practices ofSharePoint 2010

Thanks to Our Sponsors!

who are we?

Infrastructure Consultant at Applied Information Sciences8 years of experience with the SharePoint platform from MCMS 2002 to SharePoint 2010 today Enjoys discussions about user adoption, search, and world peaceRecently returned from a trip around the world…

ScottHoag

ciphertxt

who’s that other guy?

Lead Associate at Booz Allen Hamilton7 years of experience with SharePoint going back to adventures with STS 2001 and SPS 2003 with fun in the SharePoint 2007 and 2010Follows the SharePoint Credo - ADIDASAll Day I Dream About SharePointEnjoys discussions about Claims AuthZ, SmartCard AuthN, Atomic Molecular Optics & the Big Bang TheoryEnjoys whey protein biscuits

DanUsher

usher

and what about this guy?

introductions

a few ground rules…

housekeeping

Please remember to turn in your filled out bingo cards and event evaluations for prizes.SharePint is sponsored by Summit 7 Systems across the way at the Hilton NYC.Follow SharePoint Saturday New York City on Twitter @spsnyc and hashtag #spsnycCell Phones set to vibrate, Phasers set to stunQuestions? Don’t get the Jargon or Acronyms? Ask a question

agenda

IntroductionsHouse KeepingCommon ChallengesBad Practices and Pain PointsProper ApproachesConclusions

what's this talk about?

SharePoint the Product vs. SharePoint the Platform Collaboration Development Administration

Considerations for Frameworks and Governance Technical Business Social

Potholes and cracks in the roadRecovering from disaster…

it’s also about…

Avoiding ending your day like this…

SharePoint as a product

SharePoint is our… File Share Calendar Forms Management System Web Content Management Tool Records Management System Digital Asset Management

…universe

SharePoint as a platform

SharePoint hosts my… Time Tracker Help Desk Center FAQ Center Event Planning Productivity Hub Inventory Tracker Knowledge Base Lending Library Asset Tracker

…which keeps my business moving forward.

common challenges

common challenges triangle

Technical

BusinessSo

cial

it can boggle the mind…

what are your pain points?

technical challengesAuthentication and AuthorizationExternal Accessibility and ExtranetsSystem Scalability and CachingSearchUsability / Client IntegrationUser Interface Design and BrandingApplication Lifecycle ManagementMigration ChallengesNew Capabilities IntroducedTraining3rd Party Products and Integrated SystemsVariations and Multi-Lingual

business challenges

System Adoption Design of System Accessibility of System Lack of Features Lack of FederationBusiness Process ManagementResource Availability and TrainingMulti-Generational Culture DifferencesHosting Solutions – To the Cloud?Mobile, Disconnected and Distributed WorkforcesIT Shops disconnected from Business Users

social challenges

What is ‘Social’?Disabling or not planning for OOTB functionality of MySites, Audiences, etc.Information SilosLack of / Too much GovernanceNo planning for structured metadataNot leveraging folksonomy, ratings, etc.Lack of Directory Structure Impacts Active Directory information (Manager, Reports,

etc) Findability of sites, communities and

documents

typical user base

They’re not technically savvy

They don’t want to deal with “the SharePoint”

They want results

bad practices and pain points

planning

Do you have a plan?Ensure business, technical, and social plans align.

“If you have no plan, you plan to fail.”

technically speaking how'd we get here?

Did we have a plan in place? Development Guidelines Architecture Plans (Physical and Logical) System Design Document Implementation Documents/Installation Guides Change Management Plan Requirements Traceability MatricesDid 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?What about Agile development methods?

what didn't we do right?

Lack of Governance surrounding several key areas: Business Drivers for what the system is

for Development Guidelines Infrastructure Processes Architecting for the future Deployment to the user community

development disasters

Source Control ManagementDevelopment Methodologies Not having a methodology…

Release based, Waterfall, Agile? Not understanding Agile… but trying to practice

it… Test Driven Development (Nunit, TypeMock) Continuous Integration

Separate Development and Quality Assurance EnvironmentsSolution Types and Issues Farm Based Solutions Sandboxed Solutions

typical coding practices

more development disasters

Features, Web Part Packs, Solution Packages Scoping of Solutions Solution Behavior (bin / GAC / Sandbox) Install, Deploy, Retract, Remove

Knowing the differences between a site definition, a web template, and a master page… Branding mattersLack of Documentation Requirements, Design, Implementation

Disposing of Objects Properly

enterprise infrastructure processes

IT Governance & Service Level AgreementCapacity PlanningSystem MaintenanceDisaster RecoveryContinuity of Operations RTO / RPO / RLO

Sourc

e:

Sean M

cDonough @

spm

cdonough

operations and maintenance

Scheduled and Emergency/Unscheduled Maintenance TimeDeploying code without testing in a staging environmentLack of regression pathDisaster RecoveryBusiness Continuity of Operations

knowing your tools

what’s in your IT Pro toolbox?

STSADM and PowerShellPSConfig argumentsCustom PowerShell CmdletsCHM files of TechNetSP Admin Toolkit and Diagnostic Management StudioSQL Analyzer & Maintenance PlansULS Log Spy ViewerFree Trials from ISVs

alternative approaches

turning the ship around…

Approach

Planning

GovernanceDocumentation

Execution

the approach

What’s the problem we’re trying to solve? Being able to define both the mission and the

vision…

Project Planning and Execution PMBOK DMAIC Agile

Define Business Rules, Processes, and Requirements

planning

Start off with the governance checklist… SharePoint 2007 - http://go.spdan.com/xeurd SharePoint 2010 - http://

go.spdan.com/sp2010gov

Use the sample project plans… SharePoint 2007 - http://go.spdan.com/hmewo SharePoint 2010 - http://

go.spdan.com/sp2010project

Firm up your stakeholders and work to define solutions that meet their needs…Hire a SharePoint consultant to assist…

architecting for the future…

Vision…Use cases…Planning the enterprise taxonomy and logical architecture… Physical architecture?Logical architecture?Sources:

http://bit.ly/sps-ref-wssLA http://go.spdan.com/kuouhhttp://go.spdan.com/2010tech

defining the framework

Remaining rigidly flexible for change…Planning for Data Partitions and Software Boundaries…Disaster Recovery - both big and smallDefining governance and use of the system Site Quotas MySites Site Creation Process User Permissions SharePoint Designer Solution Types (Sandboxed vice Farm) Disaster Recovery Plan

misconceptions and gotchas

Recycle BinDisaster Recovery “Oops”Recovering across DomainsConsolidating and Migrating Build Numbers Workflow History

GovernanceSocial

diversity of governance

governance

Roles and ResponsibilitiesBusiness Rules and PoliciesSystem Usability and User AcceptanceInfrastructure Implementation and Maintenance Processes Software Development GuidelinesArchitectureChange ManagementTraining

It’s not just a piece of paper

governance by committee

governance

…shouldn’t be defined by a single individual…shouldn’t just be technical in nature…should take into consideration the purpose of the system…will make or break your deployment…must be flexible to change…determined by a committee and revisited

service management

service management takeaways

Determining realistic service level agreementsProviding adequate staffing to meet your end user needsKeeping the end user in mind

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 SharePoint 2007 - http://go.spdan.com/efpxr SharePoint 2010 - http://go.spdan.com/yfeqp

more documentation

SharePoint Online Development Guide - http://go.spdan.com/cmzbm

SharePoint App Dev Guidance SharePoint 2007 -

http://go.spdan.com/sp-dev-aug09 SharePoint 2010 - http://go.spdan.com/dwyee

Implementation Guides Communications Training Onboarding User Documentation

executionMaking sure that stakeholders, users, designers and developers are going in the same direction Visioning Team Business

Requirements and Solutions Development

Change Control Board

Communicate with the business They can’t hear you if you’re not screaming

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!

striving forward

Implement feedback mechanismsReview and refine processes and proceduresAdapt to the needs of the user base and organizationRemain rigidly flexible

at the end of the day

questions

evaluations

How to find usFollow us on Twitter@usher@ciphertxtRead our blogs http://www.sharepointdan.com http://psconfig.com