256. Software Build Definition template Software Build Definition template 170 specifications, configuration management to con- trol 49 SQL connectivity rules 125 instance for SharePoint 2010 96 layer testing 206 service accounts access 202 SQL Server 94, 193 installing 226 SQL Services security provision between SharePoint and 96 team role in SharePoint install 95 staffing profile 64 Staffing section in implementation 84 Stage environment 59 and production environment 168 stakeholders 25. See also clients buy-in 3 consensus 189 environment approval by 224 identifying 42 standardization in SharePoint implementation 1 Startup phase of implementation plan preparation during 73 “Statement of Works” document, source code availability in 146 State role 193 static capacity requirement for SharePoint 199 stealth install 8, 10 storage costs, records-retention policy and 132 storage needs, quotas and 158 storage resource management (SRM) 179 Strategy Brief session 107–108 Strategy Team for Governance Committee 154 subcontractors 102 deliverables expected from 54 and external dependencies 55 ownership of SharePoint tools and 146 Subsystems Level test 209 subtasks 58 success 137 Success Criteria task 118 supportability of SharePoint 7 support for SharePoint, description 156 support training 233 sustainability 7 System Center Operations Manager, management pack 186 System Development Life Cycle (SDLC) 145 system requirements for hardware 130 System Specifications document 79, 189 availability, reliability and maintenance 202–204 benefits 190 contents 190, 196 design constraints 210–211 functional requirements 198 human requirements 201–211 integration testing 209–211 interface requirements 204 overview 198 performance requirements 199–201 standard approach to recording 196–197 system management requirements 202 test requirements 205–209 topology 194–196 t Tactical Team for Governance Committee 154, 155 tasks for building resources 118 delegating 30, 58 for implementation project phases 117 listing in One-Stop Shop 218 planning to meet delivery schedule 75–76 in Project Plan Build phase 161 for resource documentation building 118–122 for SharePoint install 225–227 in Work Breakdown Structure 57–58 taxonomy organizational 133 SharePoint provisions for 100–101 System Specifications on 199 team 15. See also project manager building 107–110 business analyst 98–100 communications 106 developers 104–107 external consultants 102–107 information analyst 100–102 interfaces in organization 93–97 member responsibilities 68 Project site for 115 role 95–97 SharePoint 2010 administrator 92 SharePoint 2010 One-Stop Shop 93 users. See also training. 257 SharePoint architect 91–92 Terms of Reference (TOR) 97 testers 106 TOR for each member 88 team building in Project Startup Checklist 43 Team Productivity, risks 44 Team Site Administrator, training needs 184 technical authority project manager and 70–71 SharePoint architect and 124–126 technical client 25 technical design 130 technical personnel 1 technical resources 13, 114 client understanding of customization require- ments 137 technical reviews 90 technical support levels of teams 156 ongoing 41 technical team 34, 42–43 training in SharePoint 41 technical work record of 79–80 review 80 technologies, required for SharePoint 2010 94 templates 204 Terms of Reference (TOR) 68, 88–89, 241 for business analysts 99–100 for external consultant 104 for information analysts 102 posting to SharePoint One-Stop Shop 107 for project manager 70, 71, 89–91 for SharePoint administrator 92 for SharePoint architect 91–92 for SharePoint One-Stop Shop 93 for SharePoint teams 97 test environment 59, 139 for installation 79 scope 142 separation from other environments 146 testers 106 testing 80 backups 176 pilot system 223 production environment 231 types of 207–208 Testing documents 126 third-party products 31 third-party support. See subcontractors three-tier farm, deployment 195 time analysis for network 63 timeframe for customization work 139 of SharePoint implementation 7, 54 tracking, configuration management capture of information on 49 training 60, 106–107, 232–233. See also education in One-Stop Shop 218 planning 181–185 roles needing 184–185 Statement of Operations on 157 Training Coordination group 184 transaction log shipping 238 two-tier farm, deployment 194 U unified infrastructure 5 uptime guarantees 204 usability, criteria for 201 Usage and Health role 193 user acceptance environment 139 separation from other environments 146 User Acceptance phase 59 user acceptance testing (UAT) 55, 144 user accounts 222 user interface 36 in SharePoint 200 System Specifications for 201, 204 User Profile role 193 user profiles, configuring 228 User Profile Services 55 user requirements 18, 198 capturing 178 implementing SharePoint to match 1 importance 187 and Service-Level Agreements (SLAs) 185 and SharePoint design 213 SharePoint implementation and 175 User Requirements document 79 users. See also training approval of environments 224 decision on web site creation 150 education 16, 76 effect of number on Web servers required 195 information on characteristics 201 258. user search requests, server role responding to training strategy 183 Web site customization by 104 user search requests, server role responding to 192 V validation and verification, web resources 144 vanity URL, redirection with 215 Variables and Settings document 222 Variables and SharePoint 2010 Configuration docu- ment 125 Verification and Validation Plan 49 requirement to generate 81 Verify and Validate section in Project Startup Checklist 69 versions 169, 170 virtualization 131 virtual machine (VM) 147 for development environment 141 Windows Server2008 R2 Hyper-V 110 vision of client 17, 25, 53, 98, 175 for project 28 Visio role 193 Visio Services 19 VMWare/VirtualBox 141 V&V plan. See Verification and Validation plan W WBS. See Work Breakdown Structure (WBS) Web Analytics role 193 Web Applications section in implementation 85 Web Content Accessibility Guidelines 204 Web front ends (WFEs) 192 server configuration 227 web resources on accessibility 204 on Business Connectivity Services 20 on capacity needs 179 on certification 138 on dashboards 36 deployment guide 194 on development environment 140 on disaster recovery strategies 238 on document records and control procedures 114 on Enterprise Content Management 150 on file referencing system 77 on information architecture 134 Microsoft case studies 28 Microsoft e-learning courses on SharePoint 183 on Microsoft Project 2010 74 on minimum hardware and software for Share- Point 196 on resource building 118 on rich workflows 21 risk management procedure 45 on Schedule, Timeframe and Budgets 54 SCOM 2007 Management Pack for SharePoint 2010 186 on SharePoint 18 on SharePoint configuration 227 on SharePoint install 226 Software Build Definition template 170 on System Development Life Cycle 145 on system requirements 130 System Specification worksheets 197 on training 218 training resources for administrators 182 on transaction log shipping 238 on user requirements 187 on validation and verification 144 virtual machine for download 147 whitepapers on planning and architecture 197 Web Server Groups 195 Web Server role 192 web sites controlling user creation 179 user customization of 104 whitepapers on planning and architecture 197 wiki pages 215 Windows operating systems 5 development environment in 140 Windows PowerShell 185 Windows Server 94 Windows Server 2008 R2 Hyper-V virtual machine 110, 147 Windows SharePoint Services (WSS) 18, 226 Word role 193 Work Breakdown Structure (WBS) 75 customization included 137 for development tasks 105 header tasks in program schedule 60 in Project Plan 57–59 set up 63 worksheets for System Specifications . 259 Workflow Manager, training needs 184 work schedule, formulating 42 worksheets for System Specifications 196 About.the.Author Geoff Evelyn enjoys over 25 years in Information Technology with over 10 years of experi- ence in SharePoint, covering development, design, and implementation. He specializes in SharePoint information systems design, architecture, implementation, planning, governance and automation—all in the land of SharePoint. Geoff headed the team that introduced SharePoint to the Scottish Highland University in 2001 and then over 30 other Scottish colleges. He went on to help implement, manage, and govern SharePoint in many global companies. Geoff is a Fellow of Institute of Analysts and Programmers and a member of the Institute for the Management of Information Systems, and has published many articles and guides on SharePoint, all available on his website, www.stationcomputing.com. Stay in touch! To subscribe to the Microsoft Press ® Book Connection Newsletter—for news on upcoming books, events, and special offers—please visit: What do you think of this book? We want to hear from you! To participate in a brief online survey, please visit: Tell us how well this book meets your needs —what works effectively, and what we can do better. Your feedback will help us continually improve our books and learning resources for you. Thank you in advance for your input ! microsoft.com/learning/booksurvey microsoft.com/learning/books/newsletter . analysts 102 posting to SharePoint One-Stop Shop 107 for project manager 70, 71, 89–91 for SharePoint administrator 92 for SharePoint architect 91–92 for SharePoint One-Stop Shop 93 for SharePoint teams. organization 93–97 member responsibilities 68 Project site for 115 role 95–97 SharePoint 2010 administrator 92 SharePoint 2010 One-Stop Shop 93 users. See also training. 257 SharePoint architect 91–92 Terms. See also clients buy-in 3 consensus 189 environment approval by 224 identifying 42 standardization in SharePoint implementation 1 Startup phase of implementation plan preparation during 73 “Statement