SHAREPOINT DEPLOYMENT GUIDE AND CHECKLISTS

1 ESSENTIALS OF A SUCCESSFUL SHAREPOINT DEPLOYMENTSHAREPOINT DEPLOYMENT GUIDE AND 110/23/2007 5:09:30 PMFront SideSHAREPOINT FEATURE AREASSAMPLE HIGH-LEVEL DEPLOYMENT PLANSHAREPOINT GOVERNANCE CHECKLISTSI nformation ArchitectureProject & Operational ManagementDevelopment & Confi gurationInfrastructureTesting & ProvisioningOperational ConcernsEducation & TrainingTaxonomy & NavigationEnterprise SearchSHAREPOINT RESOURCESR everse SideGOVERNANCE TIPS AND MORE INFORMATIONSTEPS TO A SUCCESSFUL MANAGED DEPLOYMENT SHAREPOINT GOVERNANCE PLAN: INTRANET MODELSHAREPOINT PHYSICAL TOPOLOGIESSHAREPOINT CONTAINMENT HIERARCHYSHAREPOINT DEPLOYMENT TEAM ROLESMICROSOFT OFFICE SHAREPOINT SERVER 2007 DEPLOYMENT GUIDE AND CHECKLISTS 210/23/2007 5:09.

2 33 PMMICROSOFT OFFICE SHAREPOINT SERVER 2007 FEATURE AREAS Business IntelligenceCollaborationBusiness FormsPortalContent ManagementSearchPlatform ServicesWINDOWS SHAREPOINT SERVICES SERVER 2007 STANDARDSHAREPOINT SERVER 2007 ENTERPRISECOLLABORATIONDocs/tasks/calend ars, blogs, wikis, e-mail integration, project management lite , Outlook integration, offl ine docs/listsPORTALE nterprise Portal template, Site Directory, My Sites, social networking, privacy controlBUSINESS INTELLIGENCES erver-based Excel spreadsheets and data visualization, Report Center, BI Web Parts, KPIs/DashboardsPLATFORM SERVICESW orkspaces, Management,Security, Storage, Topology, Site ModelSEARCHE nterprise scalability, contextual relevance, rich people and business data searchBUSINESS PROCESS MANAGEMENT WITH WEB-BASED FORMSRich and Web forms based front-ends, LOB actions, pluggable SSOCONTENT MANAGEMENTI ntegrated document management, records management, and Web content management with policies and workfl 310/23/2007 5:09:36 PMENVISIONING Evaluate Microsoft Offi ce SHAREPOINT Server 2007 features Formulate preliminary cost/benefi t analysis Determine project scope (lab, pilot, international/regional DEPLOYMENT , coexistence strategies, etc.)

3 Secure executive sponsorship and fundingPLANNING Assemble Project Teams, Defi ne Roles Review/Detail Technical Requirements Review/Detail Preliminary Enduser and Business Requirements Determine Preliminary Design Objectives Identify Coexistence Strategies Establish Test Lab Environment Perform Risk Assessment Defi ne Communication Strategy Defi ne Education/Training Strategy Review Client Software and Hardware Create Governance Plan with Mission, Vision, and Strategy Plan Server Confi guration Plan Security Plan for performance Plan for network upgrades and WAN considerations Plan for failover and disaster recovery Plan for LocalizationSAMPlE DEPLOYMENT PlAN (1) 410/23/2007 5:09:37 PMPLANNING (continued)

4 Plan Integration Determine need for WSS, MOSS 2007 Standard or Enterprise Plan Collaboration Solutions Plan Enterprise/Web Wikis and Blogging Plan Document/Records Management Plan Indexing/Search Center & Best Bets/Keywords Plan Portal Plan Scorecards Plan Web Content Management Plan Workfl ows Plan Internet Site Plan Extranet Partner Solution Plan Forms Solution Plan Excel Services, KPIs, Reporting Center Plan Maintenance Plan Content and Navigation StructureDEPLOYMENT, IMPLEMENTATION, & CONFIGURATION MANAGEMENT Deploy Pilot System Gather feedback on Pilot and update DEPLOYMENT confi guration Deploy applicable Development, Test, and Staging environments Production Go/No-Go DecisionSAMPlE DEPLOYMENT PlAN (2) 510/23/2007 5:09.

5 39 PMSAMPlE DEPLOYMENT PlAN (3) DEPLOYMENT , IMPLEMENTATION, & CONFIGURATION MANAGEMENT (continued) Deploy Production System Install Hardware Install Software Confi gure Software Confi gure server, software, and network dependencies Confi gure Search Confi gure Document Management Confi gure Personal Sites Review single sign-on service requirements, consider Kerberos Confi gure Microsoft Offi ce SHAREPOINT Server 2007 for extranet use as desired Implement solutions and applicable third party solutions, if any Deploy updates to Client Machines as needed Test and Evaluate SystemPOST-IMPLEMENTATION OPERATIONS, OPTIMIZATION, AND BUSINESS REVIEW DEPLOYMENT Complete Maintain IT Governance through Service/Business Reviews Maintain regular Reporting in Support Operations and Change Management ReviewsFor a complete sample SHAREPOINT DEPLOYMENT Plan, go to: 610/23/2007 5:09.

6 41 PMINFORMATION ARCHITECTURE Ensure understanding of what information architecture is and how it fits in with the Intranet strategy Ensure stakeholders understand why information architecture is critical Consider hiring an information architecture professional Build wireframes for 4-5 most popular pages (for example, a Home page, a Policies and Procedures page, a Department page, and a Search Results page) Design simple sketches for each wireframe (links, content and full functionality to be added later) Create a sitemap to plan the overall structure Create sitemap subsections for popular groups or departments, then build out lower-level sections, such as Project sites Build content types for structured departments, regions, or business site 710/23/2007 5:09:41 PMPROjECT & OPERATIONAl MANAgEMENT Establish a communications plan (include): Who will do communications plan?

7 When the communications will occur? What the communications will contain? What format the communications will be in? Create contacts list and include links for those involved across the DEPLOYMENT , include stakeholders and global operations contacts Define a DEPLOYMENT process for in-house and third-party software Define how changes will be tracked, catalogued, and approved Decide where older versions of configurations, code, and compiled components will be stored Decide if you will be allocating costs back to business or not: WILL NOT: consider where the costs will be centered (compare with e-mail) WILL: Consider what metrics you ll use for the charge back (# of sites, amount of storage, amount of activity, etc.)

8 Establish a SHAREPOINT Governance board to review adoption and controls Solicit executive champions to create management attention to the value of the initiative Encourage business evangelists to share power of SHAREPOINT with other business leaderschange management processdeployment processcommunicationcost 810/23/2007 5:09:41 PMPROjECT & OPERATIONAl MANAgEMENT Define clear roles and responsibilities for the initiation of the SHAREPOINT technologies platforms Define clear roles and responsibilities for the initiation of the SHAREPOINT operation Define strategic teams to address strategy issues Establish cross-functional problem resolution to address complex issues which arise Establish a Change Control Board and Reviews Establish first who will be on the board, then what need to be reviewed, and what is considered for exceptions with a recurring change review.

9 Create a service level agreement around the length of time and approvals necessary to create a site Establish service level agreements for problem resolution through the help desk Negotiate performance service level agreements for the first load of a site, subsequent loads of a site, and performance at remote locations Establish a maintenance window When and how long is an acceptable window for downtime for patching, and pushing changes out to the environment which require worker process resets. Establish a Recovery Time Objective - How long can SHAREPOINT be down for unplanned downtime. Establish a Recovery Point Objective - How long can the business tolerate a recovery from a software, hardware, and datacenter disaster.

10 This will help you in your Disaster Recovery plan. Be sure to test your plan on a recurring and termsservice level 910/23/2007 5:09:42 PMDEVElOPMENT & CONFIgURATION Define what customization tools will be allowed Communicate what actions will be allowed and not allowed in the tools ( unghosting) Establish guidelines for the development of site definitions and mechanisms for coordinating ID usage Communicate policies for site template DEPLOYMENT , such as the requirements for a globally installed template Determine if a central repository will be required for all code installed on the platform Establish standards for building components either on a centralized server or as guidelines for building software Communicate expectations as to reference documentation (compiler generated) and warnings (whether they are allowed)