Deploying Builds from Team Foundation Server 2010 to SharePoint

Share:

This two-part series focuses on the challenges associated with SharePoint and Team Foundation Server 2010. Read the second post below to review a set of questions that can help IT teams evaluate the best strategy for deploying builds from Team Foundation Server 2010 to SharePoint

This two-part series focuses on the challenges associated with SharePoint and Team Foundation Server 2010. Read the second post below to review a set of questions that can help IT teams evaluate the best strategy for deploying builds from Team Foundation Server 2010 to SharePoint.

What’s Your Strategy?

There is a wide variety of methods that organizations can use to move builds from Team Foundation Server 2010 to SharePoint. Although there is no single approach that is “the best,” it’s a good idea for companies to engage in information gathering and analysis before committing to a deployment strategy. Here are a few questions that may help shape your evaluation:

– Human Resource Considerations

  • For a given deployment strategy, what type of IT resources will be needed to support it?
  • How will the strategy affect existing IT resources? Will new resources need to be hired? Does the current team have the necessary skills?

– Operational Considerations

  • How short is the shortest release cycle likely to be in the organization?
  • What degree of visibility into the lifecycle and deployment processes is necessary?
  • Given the various environments, what is the value of business continuity in each?
  • How well will the strategy support Agile development and continuous integration methodologies?
  • Does the strategy meet compliance requirements related to change control and auditing?

– Measurement Considerations

  • Once a deployment strategy has been selected, how will the team evaluate whether it is successful or not? What metrics will be used to evaluate success?

Different options for deployment from Team Foundation Server 2010 to SharePoint include manual processes, PowerShell scripting and STSADM, custom workflow actions using Team Build, and third party applications, such as Attunity’s RepliWeb for SharePoint (ROSS). Since each option has pros and cons, teams must decide which best suits their implementation, skill set, and budget.

Want more information? 

Download this whitepaper: “Team Foundation Server 2010: Deploying Builds to SharePoint”

Download this customer success story: “Baptist Health Accelerates SharePoint Site Deployment”

Read Part 1 of this 2-part series: EVALUATING SHAREPOINT CONTENT MANAGEMENT & ALM PROCESSES-PART 1 of 2

Dev Tool:

Request: blog/deploying-builds-from-team-foundation-server-2010-to-sharepoint
Matched Rewrite Rule: blog/([^/]+)(?:/([0-9]+))?/?$
Matched Rewrite Query: name=deploying-builds-from-team-foundation-server-2010-to-sharepoint&page=
Loaded Template: single.php