My presentation at Software2010 in Oslo, Norway. This is an updated version of the presentation that I gave in November at Business Rules Forum; with the changes in industry, this is constantly changing.

1. Business Process Management Meets Enterprise 2.0 Sandy Kemsley Kemsley Design Ltd. www.column2.com

2. Agenda Defining BPM and social software BPM and Enterprise 2.0 Collaborative process modeling Runtime process collaboration Online BPM communities Software as a service Impacts and future directions

3. What Is BPM? A management discipline for improving cross-functional business processes. The methods and technology tools used to manage and optimize business processes. Model Automate Optimize Monitor

4. What’s In A BPMS? Process modeler Repository Execution engine System integration (web services) Work-in-progress management Monitoring and analysis Simulation and optimization

5. What Is Web 2.0? Consumer-facing social software Software as a service User-created content Lightweight development models for mashups Image copyright The Economist, 2010

6. Web 2.0 Examples Gmail: rich interface,constantly upgraded Wikipedia: content frommany authors Google Maps: open APIadds to other apps

7. What Is Enterprise 2.0? Enterprise-facing social software Business purpose, not purely social: Social interaction to strengthen weak ties Social production to collaboratively produce content SaaS or on-premise

8. Enterprise 2.0 Examples Beehive, IBM’s internal social network Intellipedia, US intelligence community’s wiki

9. Collaboration, Social Networking and BPM

10. Drivers For BPM And Enterprise 2.0 Changing user expectations Trends towards greater collaboration Lack of agility in many current BPMS implementations

11. Collaborative Process Modeling Multiple people participate in process discovery, modeling and documentation Captures “tribal knowledge” Internal and external participants Technical and non-technical participants

12. Collaborative Process Modeling: Examples Lombardi Blueprint SAP NetWeaver BPM with Google Wave

13. Runtime Process Collaboration: Dynamic BPM User can “step outside” structured process + create ad hoc collaboration Audit trail and artifacts captured within BPMS audit log Eliminates uncontrolled(unaudited) email processes

14. Runtime process collaboration examples HandySoft Fujitsu

15. Online BPM Communities External communities of practice Provide idea exchange, tools Augment or replace internal BPM center of excellence May be vendor specific/sponsored Internal center of excellence Discussion forums Collaboration linked to process models Collaboration linked to process instances

16. Online BPM Communities: Examples External communities of practice IBM BlueWorks Appian Forum Software AG ARISalign (AlignSpace) Internal center of excellence Appian Global 360 Fujitsu

17. BPM Software As A Service Reduce capital costs Full capabilities of on-premise version Design and run from anywhere Key targets: Business process outsourcers Small and medium business Business-to-business processes

18. BPM Software As A Service: Examples Appian Anywhere Fujitsu InterstageBPM Cordys Process Factory ...more emerging

19. Impacts Of Enterprise 2.0 And BPM

20. The Analysts Agree...

21. Social/Cultural Impacts Participatory culture for collaborative modeling Business must commit resources IT must allow business to participate Comfort level for collaborative execution Users must feel comfortable deviating from predefined structured process Management must allow sufficient autonomy

22. Technological Impacts Standardized RSS/Atom feeds for repurposing data and user-created dashboards IM/SMS/microblogging for process alerts Rich user interfaces (AJAX) eliminate desktop installation User-created mashups

23. Economic Impacts RIA and lightweight development models lower development costs Fast graphical development End-user composition Software as a service BPMS lowers capital costs Runtime collaboration lowers cost and latency of process modeling

24. Barriers To Adoption Perceived loss of management control over processes Lack of understanding/trust in lightweight development models/tools Risk of data loss or security breach with SaaS BPMS

25. The (Enterprise 2.0) Future Is Already Here BPMS vendors incorporating Enterprise 2.0 functionality RIA configurable user interfaces Lightweight integration RSS/event feeds Design collaboration Runtime collaboration SaaS These are facilitating change in BPM

26. What To Expect In The Future User tagging of process instances Dynamic subprocess definition Integrated IM and other synchronous communication Goal-oriented shift of process responsibility from management to knowledge workers

27. Questions? Sandy Kemsley Kemsley Design Ltd. www.column2.com sandy@column2.com