This post was mentioned on Twitter by bp3bpm: Blog Post: Is the Shakeup Continuing? http://bit.ly/4HbRro...

First, how actionbase + sharepoint covers all the bases: http://blog.actionbase.com/actionbase-sharepoint-covering-all-the-bases-of-project-oriented-communications

Second, why sharepoint needs actionBase: http://blog.actionbase.com/why-sharepoint-needs-collaborative-task-tracking-and-management

Third, getting a system of record for meetings out of sharepoint: http://blog.actionbase.com/making-the-most-of-sharepoint-a-meeting-system-of-record

Fourth: Combining Email and Wiki, using Wave and Sharepoint+ActionBase as examples: http://blog.actionbase.com/combining-wiki-and-email-collaboration

Definitely they are getting solidly behind this positioning. Although I think ActionBase’s product is equally complementary to traditional pureplay BPMS offerings.

First, how actionbase + sharepoint covers all the bases: http://blog.actionbase.com/actionbase-sharepoint-covering-all-the-bases-of-project-oriented-communications

Second, why sharepoint needs actionBase: http://blog.actionbase.com/why-sharepoint-needs-collaborative-task-tracking-and-management

Third, getting a system of record for meetings out of sharepoint: http://blog.actionbase.com/making-the-most-of-sharepoint-a-meeting-system-of-record

Fourth: Combining Email and Wiki, using Wave and Sharepoint+ActionBase as examples: http://blog.actionbase.com/combining-wiki-and-email-collaboration

Definitely they are getting solidly behind this positioning. Although I think ActionBase’s product is equally complementary to traditional pureplay BPMS offerings.

But as I point out in my recent white paper (available free on BPM Focus web site) the real problem that MS face is not the prettiness of their tooling, it is the underlying Windows Workflow Foundation which is the route cause of all the issues with SharePoint. For Shpt to really kick ass, it needs to start using a robust process engine that can handle the heat – dealing with issues such as in-flight selective process migration, processes that span SharePoint Site Collections. WWF doesnt deliver on that front, and as far as I can tell, Shpt 2010 will be similarly afflicted.

But as I point out in my recent white paper (available free on BPM Focus web site) the real problem that MS face is not the prettiness of their tooling, it is the underlying Windows Workflow Foundation which is the route cause of all the issues with SharePoint. For Shpt to really kick ass, it needs to start using a robust process engine that can handle the heat – dealing with issues such as in-flight selective process migration, processes that span SharePoint Site Collections. WWF doesnt deliver on that front, and as far as I can tell, Shpt 2010 will be similarly afflicted.

Assuming IBM makes the best of the deal soon, the other vendors will want to reposition themselves in the market. I am sure many from their teams are already taking walks to the vending machine filling papercups with coffee over the weekend.

Some would directly address the same market segment that finds appeal in the new IBM BPM stack. Others would try to take up niche slots and assume specialist positions there. Those that want to keep their appeal up to suitors will try hard, and those that are happy to take the journey on by themselves will try equally hard if not harder. I think overall we can expect to see some re-alignment with vendors re-writing their market positions. More noisy market communications, events, et all. A real shakeup like you term it!