x Table of Contents
Building the Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Strategy Brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Architectural Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Engagement Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Presentations and Demo Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Chapter 6
Gathering the Resources for SharePoint Implementation . . . . . . . . . . . . . . . . . . . . . 113
Building SharePoint 2010 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
What Procedures Detail Rules Concerning SharePoint Project Resource Data? . . . 114
Using SharePoint 2010 Sites for Project Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Building SharePoint 2010 Resources: The Tasks Ahead. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
What Is the Output of the Resource Gathering? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Gathering Business Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
SharePoint Business Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
SharePoint Architect and Technical Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Chapter 7
The Business of SharePoint Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Describing SharePoint Business Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Information Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
How Is Information Architecture Defined?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Further Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Chapter 8
SharePoint Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
When to Customize SharePoint 2010 and Some Reasons for Doing It . . . . . . . . . . . . . . . . 137
Development Environment Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

The Project Manager Specifies the Configuration Management Policy . . . . . . . . . . . . . . . 166
How to Apply Configuration Management in SharePoint . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Bring the SharePoint Item Under Control As It Develops. . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Control the Item Prior to Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Bring the Configured Item Under Configuration Management at the Right Time . 170
Establish a Configuration Baseline for Each Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
A Configuration Status Account Provides History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Changes to Configured Items Must Be Controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Chapter 11
Making Sure SharePoint Meets User Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Data Growth Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Content Usage Policies and Governance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Training and Education Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Roles That Need Training. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Monitoring and Maintenance Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Finding Out What Users Want To Do with SharePoint 2010 . . . . . . . . . . . . . . . . . . . . . . . . . 187
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
xii Table of Contents
Chapter 12
Producing the System Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
SharePoint 2010 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
64-Bit vs. 32-Bit Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Before You Begin Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
System Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Functional Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Performance Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Human Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
System Management Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

What do you think of this book? We want to hear from you!
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

. . xv
Acknowledgments
There are so many to thank and praise:
First and foremost, my greatest thanks go to my partner, Kaye, and my two daughters, Fifi
and Skye; I am utterly blessed to have you in my life. The inspiration for this book came from
them, and their support through the long evenings of writing was truly magnificent!
To Troy Lanphier, the technical editor for this book, my heartfelt thanks for your tireless work
on keeping my thoughts on track and making sure I reworked and further defined sections of
the book.
To Roger LeBlanc, who brilliantly copyedited the book, my hat’s off to you, sir. Making the
book really stand out in terms of formatting and ensuring my “grammar” was correct at all
times was due to your awesomeness (if that’s a word!)—many, many thanks.
To Sumita Mukherji and Kristen Borg at O’Reilly, thanks a ton for your aid in shepherding this
book to the end! And, of course, Kenyon Brown, my acquisitions and development editor,
who is the person most responsible for making this book happen; thank you for being there
all the time to help me out, giving me guidance on format and style, and directing the book
to the relevant people. This made the book a fantastic adventure, and I really hope we can
work together again.
There must be loads of people at O’Reilly, all aiding this book, so thanks to all of them.
Of course, I did get inspiration, aid, and knowledgeable guidance from a host of people—all
brilliant technologists, SharePoint champions, architects, administrators, developers, project,
and program managers, all of whom I stand in awe. They have helped me properly struc-
ture my thoughts and given me guidance and knowledge in areas I could cover but needed
review. Several are detailed in the book as well as in their blogs and mine.

. xvii
Preface

Detail and understand the client’s current business collaboration processes
•
Define requirement specifications to match defined user requirements
•
Design, plan and produce a system specification, including rules for management
and governance
•
Gather requirements from the users; for example, site premise, structure, information
analysis, data content typing, organizational structure, and stakeholder management
xviii.
•
Design the solution; for example, taxonomy, metadata, content formatting, capacity,
logical and physical design
•
Define the implementation process; for example, procedures, guidelines for use, gov-
ernance, testing, verification, validation, and customization
•
Design the support environment; for example, create SLAs, backup and restore, disas-
ter recovery and business continuity, staffing, and training processes
•
Detail and carry out the installation and configuration of SharePoint 2010
•
Create testing plans and verification exercises to ensure the resiliency and availability
of the platform
•
Define processes to ensure that you can educate and train the users to be productive
with the SharePoint implementation
Who.This.Book.Is.For
If you are responsible for configuring, implementing, designing, or managing a SharePoint
environment (or a combination of those roles), or if you are considering implementing

Chapter.4:.SharePoint.Planning.and.Control:.Start.As.You.
Mean.to.Go
Chapter 4 describes the process for planning and controlling SharePoint implementation
activities. It provides guidance on the procedures that are relevant to SharePoint deploy-
ment. This chapter focuses on and identifies those procedures that should be considered
during a typical SharePoint project lifecycle.
Chapter.5:.Building.Your.SharePoint.Team
A successful implementation is achieved through a dedicated, skilled staff that is given clear
goals. The most important thing in deploying SharePoint is to ensure your team is defined
properly. This chapter lists the team members, their responsibilities, skillsets, and discusses
how each of them contribute to the project.