SharePoint Secrets

Managing SharePoint Projects Part 1 - Requirements Gathering and Analysis , talks about the art of gathering & analyzing requirements for SharePoint projects. In this post, I share my industry experience in handling customers, gathering requirements, setting expectations right and documenting requirements, so as to do things right the first time. 1. Project Roles/Structure: The Business Development officer/Sales rep gets the project for the organization, he knows "What SharePoint can do and how it fits in the client requirements", he bids and gets the contract for the company, then interacts with the Delivery Manager to get the project done. The Delivery manager has many projects to deliver under his department/region umbrella, so he passes it on to the Project Manager and gives him full authority and control over the project. The Project manager has a SharePoint team in place to implement SharePoint projects. the team structure for a medium to large project implementatio

PerformancePoint Services topology The following is a farm topology that uses three servers for implementing PerformancePoint Services in Microsoft SharePoint Server 2010. The front-end Web server runs on Internet Information Services (IIS) and hosts the PerformancePoint Services Web Parts, Web services, and proxy that are required for communication between the client and the PerformancePoint Services service application. The service application is a wrapper for the middle-tier business logic for an instance of PerformancePoint Services. PerformancePoint Services as a service application In SharePoint Server 2010 services are no longer contained within a Shared Service Provider (SSP). Instead, the infrastructure for hosting services becomes part of SharePoint Server 2010, and the configuration of service offerings is more flexible. The service applications framework is a common service model that provides the following benefits. A consistent management experience and shared infrastruct