http://www. PhillySharePoint http://www.PhillySharePoint.org Russ Basiura RJB Technical Consulting www.rjbtech.com http://www.sharepointspecialists.com/ russ@rjbtech.com Welcome to the Philadelphia Area SharePoint User Group This are my notes

AGENDA Quick Intro Announcements Tips and Tricks SharePoint 2010 Developer Framework Governing SharePoint Round Table Q & A

User Group Goal / Objectives Build a local community focused on Microsoft SharePoint Technologies Educate user group members about SharePoint Technologies Transfer knowledge within the community Communicate best practices Introduce new products / solutions

www.PhillySharePoint.org 2010 Coming Soon! Website for user group SharePoint resource documents SharePoint resource websites links RSS Feeds Meeting Event Schedule Past User Group Presentations Live Meetings Public Discussions Member Forums Member Blogs

Upcoming Schedule Next Meeting Wednesday, February 24, 5:30 PM to 8:30 PM Microsoft Greater PA Office, Malvern, PA Ongoing Schedule Last Wednesday of every month 5:30 PM to 8:30 PM

PhillySharePoint Sponsors Microsoft Leader in software solutions RJB Technical Consulting (www.rjbtech.com) Philadelphia-based consulting company Microsoft Gold Certified Partner Practice Area focused on SharePoint and Information Worker Technologies SharePoint 2010 Private Beta Partner

SP2010 Developer Intro

Governing SharePoint

Topics Business Governance SharePoint Center of Excellence Creation, planning, and governance Technical Governance

What is SharePoint Governance? TechNet: Governance is the set of roles, responsibilities, and processes that you put in place in an enterprise to guide the development and use of a solution based on SharePoint Products and Technologies

What is a SharePoint Center of Excellence? A SharePoint Center of Excellence (COE) is established to provide guidance and assistance with design, management and support services to the functional business areas for the utilization of SharePoint to accomplish business initiatives. The COE is responsible for creating standards and providing governance for the SharePoint Shared Services Platform

Challenges Rapid skills ramp-up required Broad technology domain High market demand for expertise limits available resources Balancing project demand for resources Driving cultural adoption (business ownership vs. pure IS technology) Enabling common technology features vs. departmental customization Optimizing performance for shared technology components Keeping pace with technology changes

Un-managed SharePoint…

Successful SharePoint… C-level champions – ownership and steering Consolidated well-managed server farms Consistency, standards, branding, usage policies Automated site provisioning with workflows Set quotas and content expiration dates Assign all sites an owner to maintain content Delete unused sites to avoid confusion and clutter Monitor and report on usage Security policies and enforcement, information management policies Easy to use and powerful Search On-demand/accessible training and support

Governance Goals and Vision Reduce TCO Optimize Remove legacy Drive efficiency Encourage Standards and Consistency Drive common brand Reduce redundant technology Provide best practices Provide Service and Solution Empower business Empower teams Empower end users

SharePoint Center of Excellence

Organization Structure and Objectives Three teams of Subject Matter Experts (SME) that provide input to the governance of SharePoint with the single objective of ensuring a successful business by enabling users. Business ownership Teams of Subject Matter Experts (SMEs) All SharePoint users have some ownership responsibilities

People: SharePoint Specialist Skills SharePoint Project Manager SharePoint Business Analyst SharePoint Infrastructure Specialist SharePoint Creative Designer SharePoint Developer(s) SharePoint Trainer Organizations need to find or develop skills to the shortage of SharePoint skills in the current market. SharePoint Architect Business IT & Dev

COE Approach to Governance Feeder Implement To Standards Feeder To Governance Meetings Issues, needs & wants, etc COE Governance Team Infrastructure Informatics Security Sharepoint Infrastructure Team Business 5 value props\ C&B SIG Iway – move to new portal technology Lotus Notes migration to SharePoint forms Files shares – security issues, duplicate data, no retention policies, difficult seraching Sharepoint User Group Team Architecture Issues App dev Escalation of unresolved issues Decisions Senior Management Team

COE Planning and Implementation Requirements Interview primary Stakeholders Design Follow industry best practices Leverage partner with specialized SharePoint knowledge Implement COE Obtain COE participation by major business areas Build Information Architecture Implement Services Support Leverage managed services for quicker ramp-up Address organization limitation Address information architecture Address communication plan\ Address Education & Training Need ability to support and develop a shared infrastructure Critical for individuals to know that application and infrastructure support is required How do you manage application areas that want to stretch the capabilities and customize sharepoint IBC wanted to limit customizations and leverage office and sharepoint

Education and Training End user Site owner Site Designer Basic Site Designer Adv SharePoint Site User Owner Developer Russ Develop a detailed Training Plan Plan as part of time and budget for implementation and adoption User Training and resources Help desk training Administrator training (site administrators) IT Pro training Developer training Internal user groups, lab sessions, support sites Local resources – training partners, user groups, etc… Use less invasive training methods such as SharePoint tip of the week emails Identify and communicate best practices

Communications Plan Communications, Communications, Communications Business – Need elevator speech IBC need a better shared drive (K.I.S.S) –messaging that users can understand Communicate with the users constantly about SharePoint Communication Plan Setting Expectations for the Business Launch / Migration Steady State Marketing Support Plan Training Plan

Information Architecture Communications, Communications, Communications Business – Need elevator speech IBC need a better shared drive (K.I.S.S) –messaging that users can understand Communicate with the users constantly about SharePoint Communication Plan Setting Expectations for the Business Launch / Migration Steady State Marketing Support Plan Training Plan

Technical Governance Process and Operations Deployment Development and Configurations Physical Architecture Site Topology Process Models for Development Lifecycle

Processes and Operations Create and Publish Usage Guidelines for your Users How content should be organized How security should be done Style guidelines (colors, fonts, etc.) Dimensions for design elements Workflow procedures Appropriate usage guidelines Practice guidelines Russ Project & Operational Management Communication planning: who, what, when, how, etc… Deployment process Change Management Service Level Agreements (SLAs) Roles and Responsibilities Charge back service? Sponsorship of implementation Platform ownership Best practices ownership Ad hoc usage vs. managed/structured usage Operational Concerns Monitoring Scheduled maintenance windows Disaster recovery Quotas Reporting Database management

Deployment Site Provisioning Concepts Site Deployment Rules Master Pages, Page Layouts, Site Templates List Templates, Site Columns Web Parts Features Content Types Navigation (inheritance) Blocked File Types Auditing Policies Self Service Site Management Site Use Confirmation and Deletion Site Collection Quotas and Locks

Development and Configuration Identify tools allowed Site definitions and templates, list templates Source code and build control Support Standards and best practices Branding, themes, master pages and layout page development Consistency with existing corporate branding Data View web parts Next steps are master page updates or adding layout pages for specific uses Pretty typical to start with some basic branding – logo and color scheme… Creating and managing theme usage Composite applications Development & Configuration Identify tools allowed Site definitions and templates, list templates Source code and build control Support Standards and best practices Branding, themes, master page and layout page development Consistency with existing corporate branding Data View Web Parts Development Are you going to allow custom development? How are applications built? By who? Where? How are they tested? Can you adopt your current SDLC process? How are application deployed? Operational transfer Maintenance Storage Quotas Example By default SharePoint imposes a 50MB limit on the size of a single document that can be uploaded into a document library. 50 MB of storage is allotted for each user’s My Site. 100 MB of storage is allotted for all Top-level Team Sites. Team Site administrators receive alerts when storage is at 90% of quota. SharePoint administrators can override storage quota for Site Collections if necessary.

Physical Architecture Software/Licensing Hardware Architecture Security Model (Centralized vs decentralized) Performance Monitoring Network Topology Disaster recovery Software Licensing Requirements -          details the licenses that are required to construct the configurations listed in the Physical Architecture section -          Recommended Software Security Model -          Centralized vs Decentralized -          Active Directory and Sharepoint -          Organizational Units -          Sharepoint Groups -          Roles, Rights and responsibilities Performance Monitoring -          You can find below a list of basic object/counters that can be used to monitor Microsoft Office Sharepoint Server performance through the performance monitor. It is highly recommended that this monitoring be in effect. Network Topology -          This section details the network topology that is in place to support the Sharepoint environments. Disaster Recovery American Water has 2 Data Centers, one in Haddon, NJ and one in Hershey, PA. For the purpose of disaster recovery, the Hershey Data Center is the main location where all American Water Sharepoint Production servers are located while Haddon is the secondary location where data will be recovered in case of disaster affecting the Hershey Data Center. As shown in the diagram below, the Network topology in Haddon Data Center is the same as the Network Topology in the Hershey Data Center (see detail network topology section).   Disaster recovery approach -          The Sharepoint disaster recovery approach -          Backup/Restore Policies and Guidelines

Process Models for Dev Life Cycle Code Introduction Coexistence Dev UAT Authoring POC Validate Test Users Workflows BPM Prod Release Management Configuration Management Operations monitoring, security and patch management Communications and service management Code propagation testing and deployment SharePoint Tips You Must Know PACKAGE IT! Features & Solution Deployment Packages will ensure basic process Source MUST BE Packaged .wsp or DENY Best way to push and manage deployed code Test, test, test - Be sure to see what happens after you use it, then remove it Even Configuration can be pushed via features & solutions http://www.codeplex.com/spconfigurator Consider virtual environments for Dev, Test/UAT Where do you draw line between

Thank you