Modelling Organisational Behavior with Process Reference Models

Process Reference Models are traditionally used to specify the "hard" or easily identifiable ICT components such as Databases, Applications, Systems and Infrastructure. More difficult to describe are the "softer" or more intangible aspects of a modern organization, for example leadership, innovation and competencies / capabilities. This paper proposes a new approach for defining and categorizing the activities of Leadership within the modern Organization. The approach emerges from the Process Reference Model that can be generalized across domains. This approach has the potential to extend and streamline the development of the process, strategy and management layers within the modern organisation. This new category of process model is termed a Reference Model of Organisational Behavior (RMOB). These are fully conformant with the requirements for Process Reference Models, as prescribed by ISO/IEC 244774 and ISO/IEC 15504. The RMOB has all the strength and flexibility of these robust Software Engineering tools, coupled with the ability to describe in process terms what was previously considered too difficult to describe. Furthermore a reliable assessment model can be derived that allows for objective capability assessments to be performed.

[1]  Linda M. Northrop,et al.  CMMI Distilled : A Practical Introduction to Integrated Process Improvement , 2022 .

[2]  Graham King,et al.  Software Engineering Processes: Principles and Applications , 2000 .

[3]  Vijay K. Vaishnavi,et al.  Design Science Research Methods and Patterns: Innovating Information and Communication Technology , 2007 .

[4]  David Tuffley,et al.  Applying Behavior Engineering to Process Modeling , 2009 .

[5]  Pasi Kuvaja Software Process Assessment and Improvement: The BOOTSTRAP Approach , 1994 .

[6]  Bill Curtis,et al.  Process modeling , 1992, CACM.

[7]  R. Geoff Dromey Climbing over the "No Silver Bullet" Brick Wall , 2006, IEEE Softw..

[8]  Anthony J. Kubica Managing in a Time of Great Change , 1997 .

[9]  Chrispen Chiome,et al.  Leadership in Organisations , 2011 .

[10]  Keith M. Heston,et al.  The multiple quality models paradox: how much 'best practice' is just enough? , 2011, J. Softw. Maintenance Res. Pract..

[11]  Victor R. Basili,et al.  The Experience Factory and its Relationship to Other Improvement Paradigms , 1993, ESEC.

[12]  Mark C. Paulk,et al.  Capability Maturity Model , 1991 .

[13]  Joseph Moses Juran Juran on planning for quality , 1988 .

[14]  N. Nayab Kaizen: The key to Japan‚s competitive success , 2009 .

[15]  Richard Turner,et al.  CMMI Distilled: A Practical Introduction to Integrated Process Improvement , 2001 .

[16]  B. Ramer,et al.  Becoming a leader. , 1993, Imprint.

[17]  Watts S. Humphrey,et al.  Characterizing the software process: a maturity framework , 1988, IEEE Software.

[18]  Paul Veerkamp,et al.  Modeling Design Process , 1990, AI Mag..

[19]  Dominick L. Flarey,et al.  Managing in a Time of Great Change , 1996 .

[20]  S. B. Kiselev,et al.  The capability maturity model: guidelines for improving the software process , 1995 .

[21]  Khaled El Emam,et al.  Spice: The Theory and Practice of Software Process Improvement and Capability Determination , 1997 .

[22]  Gerard O’Regan,et al.  The Capability Maturity Model , 2002 .

[23]  Nelson P. Repenning,et al.  Getting quality the old-fashioned way : self confirming attributions in the dynamics of process improvement , 1997 .

[24]  W. Edwards Deming,et al.  Out of the Crisis , 1982 .

[25]  J. Herbsleb,et al.  Global software development , 2001 .

[26]  Philip B. Crosby,et al.  Quality Is Free: The Art of Making Quality Certain , 1979 .

[27]  Alan R. Hevner,et al.  The Three Cycle View of Design Science , 2007, Scand. J. Inf. Syst..

[28]  David Tuffley Implementing Integrated Teaming According to ISO15504 , 2006 .

[29]  Nilson Arrais Quality control handbook , 1966 .