This session includes:
• Pain points
• Lessons learnt
• Sensible questions
• Common sense thoughts
…you decide what applies to you!
SharePoint On-Prem IS ALIVE!
“When it comes to the cloud, we’re “all
in,” but we’re also realistic. We have a
large on-premises installed base that’s
important to us, and we’re committed to
future releases of the server.”
– Jared Spataro, Senior Director,
Microsoft Office Division, “Yammer and
Enterprise Social Roadmap Update”
• Do you understand what you
are trying to achieve?
• Will you have service
• What is the purpose/s of the
• Understand different capability
behaviours e.g. Collaboration
apps will be read/write
intensive VS WCM read
The G-Spot – Governance!
Governance is SERIOUS stuff and
you can’t afford to not think about it.
“SharePoint Governance is a
guideline of rules within your
organisation, including what, why,
when, where and how
#SPGovManifesto” – Andy Talbot(!)
The SharePoint Governance
There are multiple governance
axis, but from a platform perspective, at a
minimum you should have considered :
Part of the story:
• Consensus Orientated
• Follows the rule of law
• Effective and Efficient
• Equitable and Inclusive
• Can you afford not too?
• Maintains standards
• What’s more expensive; testing or
loss of service / poor user
• It should be baked into ALL
deployments and configuration
Understand test types
• Understand what to test AND when
• Update test plans to reflect changes:
- Platform changes
- New developments
• Don’t undervalue your QA team
Go a little deeper
Understand what each type of
test area means
• Who is/will be doing this task?
• Who is assigned to work on this task?
• Who’s head will roll if this goes wrong?
• Who has the authority to take decision?
• Anyone who can tell me more about this
• Any stakeholders already identified?
• Anyone whose work depends on this task?
• Who has to be kept updated about the
DAD MOM SON DAUGHTER
C A/R C C
Bake dinner in
Roles & Responsibilities
Different each role comes a mix of
Understand who is responsible for what in
Sometimes we overlook things
(shocking!). Maybe we didn’t
stop to consider:
• When will product support
• Base or Project cost?
• How long can I keep my
• Understand vendor product and
• Helps you to plan ahead for
• Underpins personal
development planning (right?)
• To be current
• Stored in an appropriate place
(e.g. don’t store SharePoint DR
docs in SharePoint!)
• Version controlled
At a minimum the following
should be documented:
• On boarding process
• Build & Configuration
• DR plan
• HLD’s & LLD’s
• Test plans
Successive Layers of Defence
• Project Governance
• Architecture Governance
• Information Governance
• Release Management
• Quality Assurance
• Solution delivery aligns to
• Changes are communicated to
all platform stakeholders
• Peer review opportunities
• Switching on features may
affect others (e.g. Auditing)
SharePoint Centre of
See Andrew Woodward’s deck
Resources & People
• Often we ask for more system
resource, but don’t plan for
more human resources
• Do we on-board people
properly, or are they left
guessing on your standards,
• Do you encourage and foster learning
• Do you recognise emerging talent?
• Shouldn’t each capability have a base
achievement standard? E.g.
Certification, internal standards, etc.
• Does training align with product
Technology is nothing without people
Capturing User Feedback
• Do we really LISTEN?
• Is it EASY for users to feedback?
• Do we REVIEW feedback?
• Do we MEASURE THE VALUE of
delivery against customer
• Do we let GOOD IDEAS DIE?
Sometimes we need to realign for
various different reasons, e.g.
• Mergers & acquisitions
• Improve efficiency and effectiveness
• Senior management changes
• Market response
• Change of strategy
Have we thought about how we would
approach this if the need arose?
Who makes the Decisions?
Carefully consider who should AND
shouldn’t be making different types
of decisions. Worryingly it’s not
always the right people, e.g.
• Project Managers making technical
decisions (tick boxing?)
• Techies making business decisions
• Power Brokers (you know the type!)
Do decisions support the vision? “To
It’s important to:
• Have a communication plan
• Get across the intended value
• Set expectation
• Use it to promote cultural
• Show that you listened
• Promote recent successes
• Warn about service disruption
• Set an internal expectation
• Encourage commitment and
• Encourage early warning of
• Enjoy what you do!
• Establish triage process
• Understand your estate
• Identify trends, update training and FAQs
• Encourage community feedback, possibly
with Gamification techniques
• Recertification process?
• Monitor growth
• Storage reduction opportunities
• Plan for Site Quotas & Content
• Understand boundaries, limits and
thresholds, and respect them!
• Site creation control
• Service Separation
• Storage Tiers / IOPS
• Profile expected traffic patterns
(account for time differences in
• Understand usage age patterns of
each web app – determine the
best architectures to fit (e.g
Collaboration – large read / write)
• Understand caching options and
what they do (which can impact
• Office Web Apps (SP2010)
Get the Balance right
• What will come first, Load or
• Do you understand your points
• Have you planned for the
Architecture / Topologies
• Properly planned?
• Physical & Logical design
• Use it to understand how to
change your farm/s
• Traditional vs Streamlined
Technical diagrams for SharePoint
• Understand the difference
between scaling UP and scaling
• Plan Content Databases
(quotas, thresholds, warnings,
• Understand caches (e.g. Blob,
distributed, object, page)
• System Logs
• Functional Requests
• Support Issues
….are you being PROACTIVE or REACTIVE?
• Do you understand your hardware
• If on a managed platform, do you
understand your suppliers refresh
cycle and limitations? Understand
exit strategies too
• Will purchase restrictions prevent
changes in topology
• Does your company have a cloud
strategy for the future?
• Do you know what to do if you
introduce new hardware (e.g. update
SQL Alias, web.config, etc.)
3rd Party Tools
• Upgrade ready?
• Infrastructure requirements
• Support model
• Understand your procurement
• Licencing, perpetual or annual?
Have we planned for growth
e.g. enough seats
• Understand your corporate
• Be as upgrade ready as possible
• Understand deprecated features
• Learn architectural changes, both
logical and physical
• Microsoft Product Line
"How would Microsoft deploy this
technology?" or "how would Microsoft
do it?" It was from this simple question
that the PLA was born.
Typical for support and
Take time to:
• Understand the ‘Continuum of
• Agree on standards
• Agree communication methods
• Understand the QA process
• Major public holidays (different
from country to country)
• 99.9% uptime really means ‘x’
• Understand why you’re making a
• SP’s, CU’s, PU’s, COD, etc.
Understand the differences -
• READ THE RELEASE NOTES! It
might fix one thing and break
Backup & DR
• You’ve planned for it, right?
• Test annually
• RPO’s/RTO’s still correct?
• Have you over engineered? e.g.
If no point in time recovery,
why are you SQL full logging?
• Understand what dependent
applications and process maybe
BC / DR
You cannot know it all.....
• SharePoint Centre of Excellence
• Product Owners
• Design Working Group
• Information Governance (SPIG )
• Steering Committees…
The ‘C’ Word – CHANGE!
“Changing behaviours at work requires
changing the environment that
surrounds people when they’re at
work” Marc D Anderson (@sympmarc)
Is it time for gamification as an
approach to facilitating changing
“Questions are guaranteed
in life; answers aren't”
/AndyTalbot @SharePointAndy SharePointAndy.com