2. Speakers Michael Van Cleave Sr. Architect & Practice Lead MCT, MCPD, MCTS, MCSD.NET Paul Papanek Stork SharePoint MVP & Author Chief Architect & Practice Lead MBA, MCT, MCSE, MCSD, MCDBA, MCTS, MCITP, MCPD…
3. Agenda Assessing your needs What’s New in SharePoint 2010 Choosing the right version / licensing Pre-Implementation Planning Governance and Policies Assessing your existing infrastructure Designing a Taxonomy Establishing Metrics for Success Implementation Approach & Adoption DIY, Outsourcing, etc. Driving User Adoption Best Practices/Avoiding Common Pitfalls
4. What’s New in SP2010 Too much to cover in a quick overview A few important changes for everyone: Fluent User Interface (the Ribbon) Sandboxed Solutions Claims based Authentication Managed Metadata Service Social Computing improvements Feel free to ask about other new features in SP2010 and we’ll talk about these during the Q & A…
5. Which Version is Right for you? SharePoint Foundation Platform for collaboration Foundation for Web-based applications SharePoint Server Standard Everything in Foundation Enterprise Content Management SharePoint Server Enterprise Everything in SharePoint Server Standard Business Intelligence for the Enterprise Standard or Enterprise licenses for the Internet
7. Audience Survey What is your primary role in implementing SharePoint 2010? Decision Maker, Influencer or Sponsor Admin, Architect or Developer Analyst or End User Consultant
8. Pre-Implementation Tasks Create a Governance Team Choose people from different areas of the company with a vested interest in project Understand and Document your Needs Inventory content and content sources Evaluate the infrastructure (Hardware, AD, etc.) Identify business problems & opportunities Outline Line of Business Applications that will integrate with SharePoint Create written requirements – don’t “wing it”!
9. Pre-Implementation Planning Who will need to access SharePoint Will all the users be accessing the servers internally? Externally? Both? How many users are you anticipating? Availability and Recovery What type of SLA’s will you have on downtime? How often will you be backing up your SharePoint environment (RPO/RTO) Will some sites in your structure have different recovery objectives than others? Will you be moving to Office 2010 or using any 3rd party products?
10. Audience Survey Where are you on the SharePoint 2010 adoption curve? Already using SharePoint 2010 Will upgrade once the product has been out awhile (e.g. after the first service pack) Unsure – need more information No near-term plans to upgrade
11. Designing a Site Taxonomy Taxonomy: “the practice and science of classification” Can refer to sites, content, search, metadata… Different hierarchical structures for sites Functional Based on business functions Usually wide but not deep Divisional/Departmental Based on organizational structure Usually deeper than Functional Hybrid Combination of Functional and Hybrid
13. Implementation Approach Assess internal skills/assets IT Pro Information Architecture Software Development Evangelist & Trainer Get outside assistance if you need it SharePoint 2010 is new and different – use a specialist! Use consultants who provide technology transfer Look at prior SharePoint implementation experience Plan for User Adoption Change is hard - create value for End-Users Train Administrators, Content Owners & End Users Decide what to do with legacy data Not everything needs to be in SharePoint
14. Avoiding Pitfalls Don’t make it an IT-Driven project Involve people from all levels of the organization in planning Seek consensus in your planning, not democracy Don’t shortcut the planning process! Set realistic and measurable goals Don’t be afraid to ask for help. New technology isn’t always “Do it Yourself” Follow an iterative, milestone-based approach
15. Best Practices Create a simple, flexible taxonomy - your needs will change over time Recruit business user champions that embrace change Make sure your implementation works for all of your committee’s requirements Establish a communications plan; SharePoint is about empowering users Provide training for everyone - powerful tools are rarely intuitive
16. Audience Survey What do you see as next steps? Assess& Document business requirements and/or current SharePoint environment Planning& Design for a SharePoint 2010 implementation Learn more about SharePoint 2010 Deploy SharePoint 2010 in the enterprise
17. SharePoint GamePLAN Jumpstart your SharePoint 2010 Deployment 2-5 Day Session with a Sr. SharePoint Architect MVP or MCM Includes Education on SharePoint 2010 Brainstorming & Requirements Development Assessment – hardware, AD, skills, etc. Planning & Implementation Roadmap $8,500 + travel for a 4-day engagement Email Info@ShareSquared.com or call 800-445-1279 x300 to schedule
18. Downloadable Brochures Several handouts are available for download from LiveMeeting: SharePoint 2010 GamePLAN Enterprise Content Management GamePLAN SharePoint Composer/Maestro
19. Resources and Q & A Assessment, Planning & Implementation Schedule a SharePoint GamePLAN engagement Contact us for guidance or assistance with SP2010 Learn more about SharePoint 2010 Next Webinar: Social Networking Features, Integration & Governance in SharePoint 2010 Online resources 2010 Upgrade & Migration Resource Center http://technet.microsoft.com/en-us/sharepoint/ee517214.aspx Licensing Q&A:http://tinyurl.com/2010Licensing Version Comparison:http://tinyurl.com/EditionComparison TechNet Governance:http://tinyurl.com/SP2010Gov Link to AIIM Blog: http://aiimcommunities.org/users/dkruglov Contact Us Info@ShareSquared.com 800-445-1279 - Option 2
Editor's Notes
PAUL WILL START 10 MINUTE TIMER Blended SharePoint 2010 & .NET Solutions
PAUL
PAULBullet Points from the email blast• How to assess your existing infrastructure• Choosing the right SharePoint licensing to fit your needs• Estimating the ROI for a SharePoint implementation• Building a Governance Committee• Pre-implementation activities including Taxonomy, Content Inventory, Site Design/Hierarchy, etc.• Skills Inventory & Requirements • Sponsorship, Training & Adoption• Avoiding the SharePoint Meltdown• Best Practices for Configuration & Deployment
PAULOther possible additionsWord Automation ServicesBusiness Connectivity ServicesOffice Web Applications
PAUL
PAUL
SURVEY - PAUL
MichaelThe first and most critical part of the implementation of SharePoint is actually gathering information about how everyone is going to use the solution. Gather a Governance team and discover each areas pain points or objectives that they have for a successful SharePoint implementation.Understand all of the different areas of SharePoint that will need to be implemented. Where is content currently storedWho owns the contentHow will other want to find that contentHow will different areas in your organization use SharePoint?Will they want to use workflow processes and document managementWill they be heavily dependent on document storage and searchability?Will they use it primarily for team collaboration? Will there be a need for integrating different applications with SharePoint?
MichaelWho will need to access the SharePoint implementation?Only internal people (domain users)?External Contractors/Partners?External Domain Users/Employees?How many people do you anticipate that will access the environment?This will point to how your physical farm will need to be constructed and also other security considerations.This will also be good time to figure out what you have to license and how many licenses you will need.Availability and RecoveryDoes your organization have any standard SLA’s that you will have to abide by?Examples would be:SharePoint only needs to be available between 6am and 10pm during the workday.SharePoint needs to be available within 2 hours of a downtime event.SharePoint needs to be recovered to specific point in time.How often will you need to backup your environment?Recovery Point Objective = How often will you be backing up your system? (The more granular the more expensive usually)Recovery Time Objective = How quickly will you be able to recover the system in event of a failure? (The faster the more expensive usually)Will different sites need different recovery objectives or SLAs? One department may only need Document storage with slight interaction with SharePoint on a daily basisAnother department (Accounting/HR) might be crippled if they are not able to access their content within an hour of an event.
Michael
MichaelThere are really a few different strategies as to what type of site structure you can build.FunctionalGenerally builds out function based areas regardless of department or division. It will usually end up being a wider set of sites than deep.As the business or company changes it is usually easy to adapt.Divisional/DepartmentalThis is how most organizations view their structure.It is completely based on the structure of the company and how the internal hierarchy of the company is formed.This can and usually does get to be a very deep structure that can affect search results and how search sees a piece of contents relevancy.This can be difficult to change as the business or company changes.HybridFor organizations that don’t or can’t fit in one structure or the other generally a middle ground can be found by merging the best of the two concepts.
Michael
Paul
PAUL
PAUL
PAUL
PAULIf they need help, we’ve had access to SharePoint 2010 for over a year – we can guide them thru the processMentionDownloads, Recording & Email invite to ECM in SharePoint 2010 WebinarExplain SharePoint GamePLAN Q & A - EVERYONE
PAUL
PAULIf they need help, we’ve had access to SharePoint 2010 for over a year – we can guide them thru the processMention Downloads, Recording & Email invite to ECM in SharePoint 2010 WebinarExplain SharePoint GamePLAN WEBINAR: Tuesday October 26th 11:00 AM PSTCOMPOSER Site: About to get a makeover as a branded 2010 site, build using Composer & MaestroPRICING / LICENSING: Free SharePoint Foundation Version – Composer Only~$299 for Foundation BuildComposer Standard and Enterprise is sold per-UserMaestro Standard and Enterprise is sold per-serverSee the site for pricing details & info in a follow-up email w/ the Q & A contentQ & A - EVERYONE