Skip to main content

Save or Share this Report

For Application Development & Delivery Professionals

SharePoint And BPM — Finding The Sweet Spot

March 31, 2010

Primary author headshot


  • By Derek Miers
  • with John Rymer,
  • ,
  • Sander Rose,
  • Connie Moore,
  • David D'Silva

Why Read This Report

Despite Microsoft's best attempts to position the SharePoint platform for content and collaboration, many people still see it as a business process management (BPM) platform. The process management features of SharePoint 2010 are better than MOSS 2007, but they're more limited than most modern BPM suites. Why? SharePoint 2010 processes are constrained by Windows Workflow Foundation (WF). When developers build process-oriented applications that leverage WF, they often find themselves hard-coding static, brittle interfaces that add to the total cost of ownership (TCO). To use SharePoint 2010 as part of an enterprisewide BPM strategy, customers must add a comprehensive, SharePoint-oriented business process management suite (BPMS), which will raise vendor license costs, but lower overall TCO and risk. Vendors to consider include AgilePoint (was Ascentn), Global 360, K2, Metastorm, and Nintex.

Get Access

Already a Client?

Log in to read this document.

Become a Forrester Client

Customers are the new market-makers, reshaping industries and changing how businesses compete and win. Success depends on how well and how fast you respond. Forrester Research gives you insights and frameworks aligned to your role to shorten the time between a great idea and a great outcome, helping your teams win in the age of the customer. Contact us to learn more.

Purchase Report

This report is available for individual purchase ($2495 USD).


Table of Contents

  • Native SharePoint Is Good For Office Workflows But Not Enterprise BPM
  • Two Key Requirements Should Guide Your Use Of SharePoint For Process Apps

  • SharePoint Users Should Develop A Specific BPM Strategy
  • Related Research Documents