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. 1
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. 2
Typical SharePoint Implementation
Typical Scenario:Server admin installs Windows Server
SQL admin installs SQL
SharePoint admin installs MOSS
Some basic branding is implemented
Sites are created for departments (HR, IT, Finance, etc) and managers are assigned full control of their sites.
A little later….
Random SharePoint projects begin to appear
Users are given access uncontrolled
Changes are made with SharePoint Designer
Other custom functionality is created
Custom development is being done and implemented
Still even later….
Users begin to complainInformation is difficult to find
Inconsistencies exist in documents and branding
The ad hoc changes cannot be easily modified
Organization struggles to fix the problems
By this point, SharePoint has a massive black eye!
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. 3
The set of policies, roles, responsibilities, and processes that you establish in an enterprise to guide, direct, and control how the organization uses technologies to accomplish business goals.
10
Why should we bother with Governance?
SharePoint has been described by some as a virus – once it gets into an organization it grows rapidly and can soon become a disorganized collection of sites users and links.
Creating a proper governance plan helps to address this problem.
ComplianceDefine standards for UIRules for what can be changed
Service Level Agreements (SLA)Length of time and approvals to create a siteProblem resolutionPerformance levels
Content ExpirationHow often should content be reviewed?
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. 4
Development and Customization PoliciesWhat tools are allowed?
How is new functionality introduced?
InfrastructureDefine tiered environments and process for moving code/content
Governance plan (cont)
MaintenanceScheduled downtimes
Unscheduled downtimes
Disaster RecoverySingle file recovery
Single or multiple site recovery
Server recovery
Catastrophic failure
Governance plan (cont)
IT ControlUser
Empowerment
Balance between IT and Users
A well designed governance plan gives users just enough flexibility to create what they need, but also provides enough control so that the solutions retain manageability.
Protect your investment – take the time to create a governance plan!
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. 5
Define Success
What is success?
Different for everyoneCould be usage?
Ability to shutdown a file server or app?
New functionality?
What were your goals for SharePoint?
Define Goals Early
Goals
They should be clearly stated
They should be tied to business objectives
They should be quantifiable
Getting the Lay of the Land
Who owns the “SharePoint” Intranet or Portal?CIO or IT
HR
Marketing
Corporate Communications
Why does it matter? What’s the difference?
Existing Legacy or Alternative Deployments
What already exists? What can you learn from these?
Current Intranet solution
Existing Departmental web solutions
Collaborative File Shares
Personal Storage /shared drives (i.e. U:\, S:\ drive) Public Folders
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. 6
Roles on the SharePoint Team
• Responsible for the overall SharePoint Implementation. Has ultimate responsibility to direct the implementation of SharePoint in relation to the organizations goals and initiatives.
SharePoint Owner
• Responsible for the server installation, configuration, operations and maintenance of SharePoint Farm.
SharePoint Infrastructure Administrator
• Liaison between the IT Support and the End Users. Responsible for SharePoint Central Admin settings such as: search configuration, top level site creation; SharePoint user security.
Global SharePoint Analyst
• Responsible for SharePoint branding and solution layouts. Global SharePoint Designer
• Responsible for the support of end users through the function of the Help Desk.
Global SharePoint Help Desk
Roles on the SharePoint Team cont.
• Responsible for custom SharePoint development using .NET, Java, InfoPath or SharePoint Designer.
SharePoint Developer
• Responsible for defining the requirements for SharePoint solution. Helps gather and define requirements for proposed solution.
SharePoint Solution Owner
• Responsible for the design of the SharePoint solution based on the direction from the Solution Owner.
SharePoint Solution Designer
• Responsible for managing SharePoint Sites. Manages user access to the site, uploads content, designs site and manages first level user support.
SharePoint Solution Administrator
• End user that uses SharePoint in the course of their daily work. They browse / search SharePoint sites to access forms, policies or general information.
SharePoint End User
Team Alignment
Business Alignment
Responsible for representing SharePoint as a Business Solution to
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. 7
What if you don’t have the ideal team?
Options for adding to the SharePoint TeamHire new employee
Train an existing employee
External Consultant
Consider time and budget constraints
Common for companies to hire a consultant to provide a sanity check to assist employees.
SharePoint Team and GovernanceBusiness Alignment
Responsible for representing SharePoint as a Business Solution to
the Organization.
SharePoint Owner
Global SharePoint Analyst
Infrastructure Support
Responsible for developing and maintaining the SharePoint Farm.
SharePoint Infrastructure Administrator
End User Support
Provides day to day support for SharePoint Solution End Users
Global SharePoint Help Desk
Global SharePoint Designer
Global SharePoint Developer
Governance Committee
Responsible for developing SharePoint Governance Policies that will be enforced through all SharePoint based solutions.
SharePoint Owner
SharePoint Infrastructure Administrator
Global SharePoint Analyst
Global SharePoint Designer
Global SharePoint Designer
Global SharePoint Help Desk
Represent a cross section of organizationExecutive level (not from IT)
Management
Lower level
Varying tenure
Governance Committee Members Governance Committee Responsibilities
Align portal initiatives with overall business goals
Approval of changes
Resolve conflict/issues
Determine standards and policies
Some make the distinction between a Governance Committee and a Portal Steering Committee
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. 8
Governance Committee Responsibilities
Meet regularly with defined success criteria and measureable goals
Reduction of help desk calls
Fewer escalations
Conduct Usability Surveys
Review itself annually to revise structure, membership, and responsibilities
Bottom line
There are many distinct roles for a SharePoint Project
Although there is always going to be some overlap, it is important that one person isn’t the Jack of All Trades
An effective Governance Committee will help to ensure the long term success of your SharePoint implementation
Topologies
SharePoint scales from a single server install all the way to very large farms of servers
Uses assignment of roles to span multiple servers
Spread the roles out across as many servers as you need and have at it.
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. 9
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. 10
How many servers?
It depends!How much data?
Performance expectations
SLA
What are users actually going to be doing?
How much budget do you have? Ass
ess Determine
organization-specific data, enter into tool
Rec
om
me
nd Inputs
analyzed, best-fit topology Recommended Si
mu
late Run
Simulations-”What If” analysis R
epo
rt Report is Generated in Excel/Visio format (summary or detail)
microsoft.com/technet/SolutionAccelerators
SharePoint Capacity Planning Tool
Development Environment
Ideally each developer should be using their own VM
It is possible to have several developers use a single server but can be challenging – lots of IISRESETS!
Move code in structured manner between environment
Solution framework
Document any custom changes
Same process for disaster recovery
Keep good notes!!!
Developers and Servers
Developers and Server Administrators need to work together!
Server admins are responsible for keeping servers running
Developers should document the functionality they are asking the administrators to put on the servers• Documented roll back plan!!!
SharePoint is an environment where working in a vacuum can be very dangerous!
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. 11
Tiered Environment
Developer VM
Dev Server
Staging/QA
Production
Break fix
Quick note about installations
Make sure your SharePoint Administrator is following some guidance
Build a strong foundation!
It is easy to make mistakes
Beware of the Basic or Stand Alone install
Bottom line: Have your admin read up on installation or get some training. It will save you time and money
Authentication
Question:
“What method of authentication is best?”
Answer:
Windows Authentication. SharePoint was designed with this in mind. Many functions require Windows Authentication to work like Search.
Windows Authentication: NTLM vs. Kerberos
Kerberos has its benefitsNo double hop problem
More secure
Less authentication traffic
DownsideRequires extra work to setup
Domain needs to be in order (Server time off by > 5 minutes and auth fails)
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. 12
Final word on authentication
Windows Authentication uses Active Directory as the basis for storing user information
Forms based authentication (FBA) allows user information to be stored outside of AD
SQL
ADAM
Etc.FBA is a good option for Extranets
It is not without its drawbackshttp://www.sharepoint911.com/blogs/john/archive/2008/08/07/setting-expectations-forms-based-authentication-fba-with-sharepoint.aspx
Disaster Recovery
Backup optionsSQL Backups
SharePoint Backups
3rd Party Products
What should you backup?SharePoint databases
Custom files on the file system (dlls, images, etc)
Solutions and templates
IIS Settings
Governance Checklist
Define SLAs for uptime and performanceFault tolerance level
High Availability?
Plans for future expansion (scale up vs out)
Define tiered environmentsWhat can you do in each environment?
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. 13
Governance Checklist
Database sizingEstimate initial size
Expected growth
Archive strategyShallow
Deep
The structure of shared information environments to improve usability.
Taxonomy
User Interface design
Navigation
What is Information Architecture?
Content is king!
Usability is the key to happy users
Happy users = Happy stakeholders
Often neglected during SharePoint projects, but critical to success!!!!
Why does IA matter? What is taxonomy?
Think back to biology classKingdom, Phylum, Class, Order, Family, Genus, Species
For portal purposes it is the classification and organization of the content
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. 14
Why is the taxonomy so important?
The portal is going to be a wasted project if the users cannot find the information that has been stored there.
Imagine going into a hardware store with no names on the aisles!
Don’t forget search50% of users navigate50% of users search
Types of taxonomies
Business unitsTry to avoid the org chart
SubjectHard to create universal subject headings
Ex. Yellow Pages
FunctionalBased on the business’ functions
Methods for creating taxonomy?
Card sorting & Software
Industry based templates
Design team
Card Sorting Technique
Using members from the different stakeholders, separate content into cards and then sort into a logical manner and place headings on the content
Then observe the findings of several different users to see where the organization overlaps
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. 15
Industry Based Templates
Depending on your industry there may be taxonomy templates already available.
It is best to take the template and mold it into your business’s culture.
The design team
Stakeholders (all the way down to users)
Information Architects
Planning committee
Determining the Content
Combine team knowledge with interviewsCan be surveys or even log parsing
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. 16
Metadata and Columns
Metadata is data about dataIt allows you to capture information about an item or document. The information will make it easier to search, sort, filter, and group.
Want more metadata?Add a column
Navigation
Like security navigation is inherited
Links may be added or removed
The main elements are:Quick Launch Bar (Current Navigation)
Top Link Bar (Global Navigation)
Breadcrumb
Navigation with Multi Site Collections
Manually recreate on every site collection
Common image pulled in by master page
Create some thing like a DHTML menu that is referenced by master page
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. 17
Audience Targeting (Cont.)
The following content can be targeted:Navigational links
Web Parts
Documents in a library
Items in a List
MOSS Search is Awesome!
WSS Search is cool too!
Same technology behind both
WSS Search only works within the site collection
MOSS can crawl just about anything
Biggest difference? WSS Search just runs
MOSS Search has lots of configuration options
Remember MOSS Search and SSP
Feature Breakdown – Content Sources
WSS – Just your SharePoint Site Collection
MOSS Standard– All of your SharePoint Sites at once and add things like
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. 18
Keyword/Best bets
Highly under utilized
Keyword is what your user is searching forCan assign a definition to display
Best bet is what you think they wantLinks to any web url
Administered by site collection admin
Internet vs. Intranet vs. Extranet
Keep your audience in mind
Each of these environments will have different taxonomies and information architecture for both security and usability.
Governance Checklist
Ensure stakeholders understand why IA is important
Create site map of IAInclude sites and pages
Note site collections, content dbs, security, or other crucial items
Define permissions!!!!!!
Publishing or not?
Who owns the taxonomy?
Governance Checklist
Define major pieces of content and where it lives
Site Columns and Content Types
METADATA!!!!!!
Define Rollup strategy
Decide if templates are requiredWhat’s in the templates specifically?
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. 19
Governance Checklist
Process for new site creationIs it a site collection or a site?
How is it approved? Created? By who?
Define the enterprise search strategyWhat is searched?
What is the expected search behavior and results?
What does branding mean?
What does it mean to you?
Pretty much all user interface design is branding….
Look and feel
Web part design and rendering
XSLT
Anything you see on the screen is branding!
Why brand?
Consistent Look and FeelMaster Pages and Themes
Content Page TemplatesSite Columns and Content Types
Page Layouts
Editable ContentWeb parts
Field Controls
WSS vs. MOSS Branding
WSSMore geared for managing documents.
Sites only have one active master page applied to all content pages.
No user interface for switching master pages it all has to be done manually
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. 20
WSS vs. MOSS Branding
MOSSRobust capabilities for publishing traditional web pages
Ability to change master pages and page layouts
More robust controls available for designers and developers to use
Can use different page layouts for the same content (ex. Article Left, Article Right)
Much better option for public facing sites
SharePoint Themes
Master Pages
Page Layouts
SharePoint Elements Controls, Web Parts, etc.
Branding Methods for SharePoint
Intranet vs. Extranet vs. Internet
Internet siteFew authors/many consumersHeavily styledPerformance, usability, accessibility
Intranet siteMany authorsSubstance over styleLess variables to consider
ExtranetFocus on security of contentBalance of style and substance
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. 21
OOTB Themes Custom Themes
Master Pages
Think back the to the old days – when you wanted to change the look and feel for a site you had to change EVERY page.
Master pages allow you to change the look and feel for an entire site simply by making changes to a single file
The glue that holds everything together
Can’t have a SharePoint site without it – even if you use a theme!
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. 22
Custom Master Pages Master Page vs. Theme
If you only have WSS – themes are a great option
If you just want to change colors, fonts, background images then go with a theme.
If you want to move elements around on the page you have to go Master Page.
If you are on the fence, go Master Page. It might be a little more work but it will give you more flexibility. Realistically you might need both a theme and a master page!!
Page Layouts
Think of it as a template for content
Two ways to display content
Field controls
Basically the same thing as entering content into a field on a list.
Content is saved to the content database.
Content can be versioned
Web Parts
Content is displayed by configuring the various web parts
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. 23
Anatomy of a page
Master Page
Page Layout
Anatomy of a page
Master Page
Web Part Zones
Web Part Zone
Field Control
Field Control
SharePoint Specific Elements Typical SharePoint Design Process
1)Create an HTML version of the site
2)Decide where the SharePoint elements need to go and wrap the HTML around them
3)Tweak
4)Take deep breaths (i.e. balance design with SharePoint’s capabilities)
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. 24
Common Design Hurdles
NavigationDrop shadows
Unique look per button
Other custom navigation behaviors
Designs not accounting for SharePoint functionality
Reliance on strict XHTML or CSS
Overly elaborate containers for contentCustom look and feel for certain containers
Too small
Key factors in estimation
Master page vs. theme
Skill level of designers
Deployment considerations
How much time is available
Complexity of the design
Number of elements to be styled
Flexibility of the client
Gotchas
Give enough time to test and review design…you will find things that need changed
Test and review with REAL content
Content authors will approach the site differently from the SP team
Page content design is different than branding the site – role of governance in branding
Think of SharePoint as a car – OOTB is stock
Two ways to change functionalityCustomization (putting better tires on the car)
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. 25
Customization
Customization – Any changes that can be made through the user interface or through the use of SharePoint Designer or InfoPath that does not require custom programming. This would include the use of the out of the box Web Parts, list and site templates, and all of the capabilities of SharePoint Designer and InfoPath.
SharePoint Designer Workflows
InfoPath Forms
Making changes to a master pageUsing SPD
Download/Upload through the UI
Examples of customization
Customization
ProsQuick to implement
Low risk
ConsLimited functionality
Limited code reuse
Lack of real source control
Difficult to move between sites/environments
Development
Development – Any changes that do not fit into the description of customization. Generally development is done with Visual Studio.
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. 26
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. 27
Site Design
Data View Web Part
Workflows
Create Page Layouts
Primary tool for SP customization
SharePoint Designer
Use to create dynamic forms
Forms can be web enabled
Workflows can be applied
InfoPath
A file where the source on the file system of the server and not in the content database.
Many copies of the same file point to the same source – like a template for a document
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. 28
Source of the file lives in the content database
A file becomes customized when it is modified via the SharePoint API
SharePoint UI
SharePoint Designer
Can revert customized files!!Could not easily revert customized files in SharePoint 2003
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. 29
Customization is a powerful way to quickly make changes or deliver functionality to users
But with great power comes great responsibility!!
And the point is…?
Delivers functionality or files to a site in uncustomized state
Feature.xml
Can be scoped at different levels
But…
Learning curve
Debugging not intuitive
Features
Modified CAB file with .WSP extension
Able to simultaneously deliver files to all servers in farm
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. 30
Automating Solution Package Creation for Windows SharePoint Services by Using MSBuildhttp://msdn.microsoft.com/en-us/library/cc441431.aspx
Features for SharePoint --Ted Pattisonhttp://msdn.microsoft.com/en-us/magazine/cc163428.aspx
Getting started with solutions/features
Single Server/Small FarmConsider available time and resources
Controlled customization poses minimal risk in most cases
Features/Solutions would be nice, but not critical
Recommendations for different environments
Medium FarmSolutions and features would be ideal if possible
Targeted customizations
Recommendations for different environments
Large Farm/Multiple FarmMicrosoft recommends use of solutions and features as best practice!!
Customizations still good – but requires strong governance
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. 31
Customization vs. Development
Compare OOTB functionality to requirementsIdentify the gaps
Can the client live with any gaps?Can the gaps be closed with customization?Can the gaps be closed with 3rd party solutions?Evaluate effort to develop ideal solutionWeigh pros/cons of each solution
Remember: Anything can be done given enough time and money – but is it worth it?
Both approaches play an important role
Just because a developer can write something doesn’t mean they should
Developers should learn how to use OOTB and customization techniques
Consider maintenance of the functionality
Strike a balance
Rollout Ideas
Soft Rollout
Pilot or Single Department
Non-Crucial but popular content site
Most Important thing is to have a plan and timeline for the rollout.
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. 32
End User Training
End User Training Kit
Computer Based TrainingNeed to be able to customize this to your environment to be relevant
Allow lab time for migrating their own content with an expert there
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. 33
Migration
Other content sources read only
Gravity slide
Manual
3rd party Products
What happens when someone from the SP team leaves the company?
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. 34
Customer Satisfaction
How do you determine if the implementation has been successful?
Search Reports
Usage Reports
Surveys• This will also help you determine additional functionality
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. 35
www.microsoft.com/teched
Sessions On-Demand & Community
http://microsoft.com/technet
Resources for IT Professionals
http://microsoft.com/msdn
Resources for Developers
www.microsoft.com/learningMicrosoft Certification and Training Resources
www.microsoft.com/learning
Microsoft Certification & Training Resources
Resources Related ContentSharePoint Admin Guide to not Screwing uphttp://go.microsoft.com/fwlink/?LinkId=139163&clcid=0x409TechNet SharePoint Governance Resource Centerhttp://technet.microsoft.com/en-us/office/sharepointserver/bb507202.aspxCodeplex SharePoint Governance Toolshttp://www.codeplex.com/governance
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.
