For Business Process Professionals

Primary Analyst Photo	Document Information	Rate this Document
	March 31, 2010 SharePoint And BPM — Finding The Sweet Spot by Derek Miers with Connie Moore, John R. Rymer, Charles Coit, Sander Rose, David D'Silva	Average: 10  (4 ratings)

This is an excerpt

Executive Summary

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.

Keywords

• business process management
• BPM

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

RECOMMENDATIONS

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

This is an excerpt

Buy Risk-Free

Price: US $2495

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.