Gathering Requirements: Asking the Right Questions for Building a SharePoint 2013 Environment Shannon Bray, MCSMChief Architect, Planet Technologies

SPC102

Shannon BrayMCSM: SharePointMCM: SharePoint 2010MCT, MCSD, MCSE, MCPD, MCITP, …Chief Architect, Planet TechnologiesAuthor

ProblemspaceIgnoring minimum requirementsLack of planning

Phases of a Successful Project

Discover and refine requirements

Analyze and prioritize

requirements

Design a solution that meets the requirements

Govern solution delivery,

operation, maintenanc

e

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 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

Planning SuccessKey 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?

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?

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?

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?

Demo

Architecture Concepts

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?

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!

Evaluate this session now on MySPC using your laptop or mobile device: http://myspc.sharepointconference.com

MySPC

© 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.