sharepoint 2010 sql server 2012 minor issues but mostly ok built to minimum specs for 2010
TRANSCRIPT
Gathering Requirements: Asking the Right Questions for Building a SharePoint 2013 Environment Shannon Bray, MCMChief ArchitectPlanet Technologies
SPC362
Failed implementations? New to Microsoft SharePoint 2013? Need your next project to be successful? You want the list of questions I use?
You are here because …
Many of us have goals and plans to accomplish those goals.
Typically, the more detailed the goals and plans, the better chance you have for success.
SharePoint is no different!
Importance of gathering requirements
So … I have this client ….
SharePoint 2010SQL Server 2012Minor issues but mostly OKBuilt to minimum specs for 2010
So … I have this client ….
• What is the most important question to ask????
Problem Space
• Ignoring minimum requirements• Lack of planning
Phases of a Successful Project
Discover and refine requirements
In This Session …We will discuss questions pertaining to …• Minimum requirements• Planning success• Planning governance• Planning information architecture• Planning business processes• Security requirements• Business intelligence• Role of the Office client• Performance and reliability• Business continuity management
Minimum RequirementsInstallation Scenario Deployment type and scale RAM Processor Hard disk space
Single server with a built-in database or single server that uses SQL Server
Development or evaluation installation of SharePoint Foundation 2013
8 - 10 GB 64-bit, 4 cores 80 GB for system drive
Single server with a built-in database or single server that uses SQL Server
Development or evaluation installation of SharePoint Server 2013
24 GB 64-bit, 4 cores 80 GB for system drive
Web server or application server in a three-tier farm
Pilot, user acceptance test, or production deployment of SharePoint Server 2013
12 GB 64-bit, 4 cores 80 GB for system drive
Minimum RequirementsSQL Servers64-Bit, 4 or 8 cores depending on the number of users8GB for small deployments; 16 GB for medium.For large deployments, it is highly recommended that you review the Storage and SQL Server Capacity Planning Configuration for SharePoint Server 2013.
Stretched FarmIntra-farm latency of < 1ms one way, 99.9% of the time over a period of ten minutes.Bandwidth speed must be at least 1 gigabit per second
Planning SuccessWhy SharePoint 2013?Key players?Organization’s strategic initiatives and mission?Reporting relationships between the stakeholders?Why is each stakeholder involved?Business objectives? Vision statements for each?Business objectives map to initiatives?Any conflicting goals?Parameters of a successful project?Steps to maximize and measure user adoption?Plans for maintenance and monitoring?
Planning SuccessASK: What will determine the success of the project?
If you don’t know the answer to this question before you start, you are not planning for success!!!
Don’t be afraid to ask for specifics!! • Reduction in effort or time?• ROI or cost benefit?
Everything should be measurable!!!
Governance StrategyMembers of governance board?Vision statement of the project?Defined roles and responsibilities?Policies and standards for:
ContentDesignSecurityFeaturesNavigationCustom codeComposite applicationsBranding
Information ArchitectureTypes of sites and how accessed?Content types, site columns, etc. ?Content security?User experience?Document storage?Document metadata?Metadata commonalities?Document storage before SharePoint?Document management policies?Managed terms and keywords?
Planning SuccessRemember: Implementing a tool should not dictate a process
and the tools selected to enable a processes should not dictate the requirements. It is important to remember the requirements first and the technology second.
Business ProcessesProcesses ties to content?Policies around content?Type of browsers?Whose responsible for defining processes? (governance)Whose responsible for workflows? (governance)What composite applications will be available?LOB data?
Security RequirementsWho? When? What? Why? How?Internal and External? Same Rights?Authentication?PII?Data in transit and rest? (SSL, TDE, etc.)Ports? Gateways? Proxies? LB?Anti-virus?Server hardening?Pre-defined network topologies?
Security Requirements (cont.)Rights management?Compliance and auditing?Threats management?Password policies?GPO settings?Groups in AD and\or SharePoint?
Business IntelligenceReports?Charts?Dashboards?Scorecards?KPIs?Excel Services?PerformancePoint?Visio?
Role of Office ClientEnd-user version?Local copy?Offline use?Document caching?Co-authoring?Mobile applications?OneDrive or OneDrive Pro?
Planning SuccessRemember: Don’t ignore SharePoint Online as an option if it fits.
Email, collaboration, instant messaging, VoIP audio and video conferencing can be packaged nicely with Office 365!
It doesn’t have to fit perfectly. Hybrid deployments offerflexibility!
Business ContinuityDefined SLAs?Expected RPO?Expected RTO?Who is responsible for backups? (governance)Who is responsible for DR plan? (governance)How often is plan tested?Location of data centers?Budget?
Performance and ReliabilityConcurrent users?Growth or adoption over X years?Performance metrics?Services?Geographical areas?AD, SharePoint, SQL locations?Peak hours?Monitoring and Maintaining?Expected load?RAM? Distribution? NUMA Boundaries?
Performance and Reliability? (cont.)Network speed?Encryption requirements?Virtual, bare metal, etc. ?Blade distribution? Development and Staging?Software development lifecycle?Custom code?External SharePoint apps?Concerns acquiring hardware?Time allocated for performance and reliability testing?
Demo
Asking the Right Questions …
SummaryEvery Microsoft SharePoint 2013 implementation is different and it is vital to understand the requirements that will help build a system to will promote success. This document is meant to help trigger requirements that may be critical architecture component.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Questions?
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Thank You!
MySPCSponsored by
connect. reimagine. transform.
Evaluate sessionson MySPC using yourlaptop or mobile device:myspc.sharepointconference.com
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.