%0 Journal Article %1 BDJK11 %A Bruno, Giorgio %A Dengler, Frank %A Jennings, Ben %A Khalaf, Rania %A Nurcan, Selmin %A Prilla, Michael %A Sarini, Marcello %A Schmidt, Rainer %A Silva, Rito %D 2011 %J Journal of Software Maintenance and Evolution: Research and Practice, incorporating Software Process: Improvement and Practice %K BPM BPM2009 DISS bpms knowledgemanagement model modelling myown ownstuff process %N 4 %P 297-326 %T Key challenges for enabling agile BPM with social software %V 23 %X Business Process Management is called agile when it is able to react quickly and adequately to internal and external events. Agile Business Process Management requires putting the life cycle of business processes on a new paradigm. It is advocated in this paper that social software allows us to satisfy the key requirements for enabling agile BPM by applying the four features of social software: weak ties, social production, egalitarianism and mutual service provision. Organizational and semantic integration and responsiveness (of the business processes engineering, execution and management activities) have been identified as the main requirements for implementing an agile BPM life cycle. Social software may be used in the BPM life cycle in several manners and using numerous approaches. This paper presents seven among them and then analyzes the ‘support’ effects between those approaches and the underlying social software features, and the three requirements for Agile BPM

@article{BDJK11, abstract = {Business Process Management is called agile when it is able to react quickly and adequately to internal and external events. Agile Business Process Management requires putting the life cycle of business processes on a new paradigm. It is advocated in this paper that social software allows us to satisfy the key requirements for enabling agile BPM by applying the four features of social software: weak ties, social production, egalitarianism and mutual service provision. Organizational and semantic integration and responsiveness (of the business processes engineering, execution and management activities) have been identified as the main requirements for implementing an agile BPM life cycle. Social software may be used in the BPM life cycle in several manners and using numerous approaches. This paper presents seven among them and then analyzes the ‘support’ effects between those approaches and the underlying social software features, and the three requirements for Agile BPM}, added-at = {2011-02-17T10:25:47.000+0100}, author = {Bruno, Giorgio and Dengler, Frank and Jennings, Ben and Khalaf, Rania and Nurcan, Selmin and Prilla, Michael and Sarini, Marcello and Schmidt, Rainer and Silva, Rito}, biburl = {https://www.bibsonomy.org/bibtex/2608585bebd94d1da02df92d1bbd66cfa/michael}, interhash = {858bb0779b539be0ffeb33f2d243d90c}, intrahash = {608585bebd94d1da02df92d1bbd66cfa}, journal = {Journal of Software Maintenance and Evolution: Research and Practice, incorporating Software Process: Improvement and Practice}, keywords = {BPM BPM2009 DISS bpms knowledgemanagement model modelling myown ownstuff process}, month = {June}, number = 4, owner = {prilla}, pages = {297-326}, timestamp = {2011-06-07T11:19:45.000+0200}, title = {Key challenges for enabling agile BPM with social software}, volume = 23, year = 2011 }