Skip to main content

2012 | Buch

Pro SharePoint 2010 Governance

insite
SUCHEN

Über dieses Buch

Pro SharePoint 2010 Governance is the first book on the market focusing exclusively on the essential guidance necessary for leveraging SharePoint 2010 within your organization's intranet, extranet or Internet environment for maximum business value. Effective governance allows your organization to promote the adoption of SharePoint’s productivity-enhancing features while maintaining security and control over your organization's most vital information.

Pro SharePoint 2010 Governance presents comprehensive guidance, from the basics of "What is governance?" to the detailed considerations of IT, information and application management. Using the conceptual framework promoted by Microsoft and augmented with detailed discussions, recommendations and checklists, you will have all the information you need to streamline the governance of your SharePoint sites.

Teaches the concepts and benefits of SharePoint site governance. Discusses advanced features and techniques for implementing governance in your organization. Provides detailed recommendations, templates and checklists for jump-starting your governance effort.

Inhaltsverzeichnis

Frontmatter
Chapter 1. A SharePoint Manifesto
Abstract
We the users, in order to form a more perfect collaboration, establish function, insure business utility, provide for the common security, promote the general usability, and secure the value of information for ourselves and our coworkers, do ordain and establish this governance plan for the portal of our organization.
Steve Wright, Corey Erkes
Chapter 2. SharePoint Governance Overview
Abstract
In this chapter, we will introduce the conceptual framework used throughout the book and define the terminology used to describe and govern SharePoint solutions. By the end of this chapter, you will understand the purpose and process of governance and, hopefully, where you fit in.
Steve Wright, Corey Erkes
Chapter 3. Governance Planning
Abstract
One of the hardest parts of performing effective governance is getting started. This chapter will describe the steps that need to occur to go from “We want a SharePoint Site” to “We have a Plan.” While the steps outlined are intended to be in chronological order, there are plenty of valid reasons to choose a different sequence for certain items. Specifically, consider the steps that happen before and after you establish the governance team. Do you establish your vision, goals, and scope before building the team or as part of forming the team? Questions like these can best be answered by considering the culture of your organization. Don’t assume that the process outlined in this chapter is the only process that can work.
Steve Wright, Corey Erkes
Chapter 4. Implementing Services
Abstract
In this chapter, we will discuss how to establish the controls needed to govern the portal. Controls include the automated and manual processes used to manage the portal. The strategy we will use is to divide the functionality of the portal into manageable components, called services, as described in Chapter 2. We will identify the services to be implemented and walk through the planning for the service’s lifecycle.
Steve Wright, Corey Erkes
Chapter 5. User Training and Adoption
Abstract
This chapter will examine how to get users actively involved in the portal, both as consumers of information (visitors) and as producers of content (contributors). Having a well-managed portal is only half the battle. The more important task is getting people to use it.
Steve Wright, Corey Erkes
Chapter 6. Managing Content
Abstract
This chapter will explore the roles and responsibilities usually assigned to the Information Technology (IT) department when governing a SharePoint environment and look at how an IT department can help users manage their content. This involves creating, organizing, and updating content. But just as important as creating content in SharePoint is managing the removal of old, obsolete data. Data that is no longer needed can cause resource and performance problems as well as exposing the organization to data consistency and compliance issues. This chapter will focus on the tools provided by SharePoint to manage the entire content lifecycle.
Steve Wright, Corey Erkes
Chapter 7. Managing the Server Farm
Abstract
In Chapter 6 you saw how the IT organization can help users manage their content. Setting standards and policies for managing the server farm’s configuration is just as important as it is for managing content, so in this chapter you will look behind the scenes at how the server farm itself is managed. We will show you the tools in SharePoint that allow you to control the configuration of the farm and all of its components. We will then show how a SharePoint farm can be monitored and maintained. This will lead us into Chapter 8 where we will discuss creating an operational plan for your SharePoint environment.
Steve Wright, Corey Erkes
Chapter 8. Managing Operations
Abstract
Depending on the size and complexity of the farm, managing the daily operations of a SharePoint farm can be a full time job. SharePoint 2010 introduced many new services and features that make monitoring operations of the farm and its users much easier than in previous versions. Monitoring the overall SharePoint farm health as well as how the users are interacting with SharePoint is critical to the overall success of the environment.
Steve Wright, Corey Erkes
Chapter 9. Information Architecture Overview
Abstract
Information architecture is the science of how to organize and categorize content. When we talk about information architecture content in terms of SharePoint, we are referring to sites, lists, document libraries, and metadata. Creating a logical order and structure of this content is critical for the success of any SharePoint implementation. It is crucial to understand this content before we can govern it. This includes the different types of information, how it is created, who owns it, and how it will be disposed of or archived. SharePoint provides many features to aid in this process, but working with the business to understand these pieces it critical.
Steve Wright, Corey Erkes
Chapter 10. Information Delivery
Abstract
In the previous chapter we talked about information architecture and how best to use metadata, content types, and taxonomy to create an environment in which it is easy to navigate and find information. In this chapter, we are going to focus on how best to deliver that information through Web Parts and search. With all the content stored in the environment, and with different users interested in different content, how do you drive individual users to their desired content or drive the desired content to them? Luckily SharePoint has some cool features that make this possible and easy. in this chapter we’ll investigate what those features are and how best to drive relevant information to the end user instead of having the end user navigate and search for content.
Steve Wright, Corey Erkes
Chapter 11. Branding the User Interface
Abstract
While it may not always be top of mind when deploying or administrating a SharePoint environment, branding and user interface design are key components. A brand is a powerful thing, and something most companies put a lot of time and effort into developing. Think of company logos, such as the swoosh for Nike, the golden arches for McDonald’s, or the red bull’s-eye for Target. These icons and company colors automatically get you thinking about the company and perhaps a product or service they provide. When working on a SharePoint user interface, keep in mind that the company brand needs to be displayed throughout this environment. Following company branding standards such as color palette, font type, and other general branding guidelines will help align the SharePoint environment with other company systems.
Steve Wright, Corey Erkes
Chapter 12. Customization and Tools
Abstract
In this chapter, we will introduce application management. An application in this context refers to any custom functionality created for deployment to a SharePoint site. This could include creating a custom user experience using themes, page layouts, and navigation controls (sometimes called skinning the site). It could also involve writing new source code modules that are deployed to the farm to run alongside the SharePoint server application.
Steve Wright, Corey Erkes
Chapter 13. Packaging Solutions
Abstract
Creating applications for deployment to a SharePoint environment is different from developing them for the desktop or a web site. This chapter will describe some of the technical details associated with creating, deploying, and maintaining solution packages in a production SharePoint environment. We will not attempt to provide all of the details a developer might need. This discussion is focused on the capabilities and limitations of solution packages in different environments. The goal is to provide the guidance needed to plan solutions and features so that they can be effectively managed.
Steve Wright, Corey Erkes
Chapter 14. Application Lifecycle Management
Abstract
Chapter 12 explored the components of a SharePoint application including Web Parts, workflows, master pages, and themes. In Chapter 13, you learned how to compile these disparate components into Share- Point features and solution packages that could be deployed to a server farm in a controlled, updatable way. In this chapter, we will look at the processes that need to be in place to manage the teams that create and maintain SharePoint solutions. These processes, taken as a whole, are known as Application Lifecycle Management (ALM).
Steve Wright, Corey Erkes
Backmatter
Metadaten
Titel
Pro SharePoint 2010 Governance
verfasst von
Steve Wright
Corey Erkes
Copyright-Jahr
2012
Verlag
Apress
Electronic ISBN
978-1-4302-4078-5
Print ISBN
978-1-4302-4077-8
DOI
https://doi.org/10.1007/978-1-4302-4078-5