A Compliance Analysis of Agile Methodologies with the ISO/IEC 29110 Project Management Process

Software process standards (e.g. ISO/IEC 12207, ISO/IEC 15504) and models (e.g. CMMI) provide a set of best practices and guidelines for improving the quality of the software process and products resulting from that process. However, they do not prescribe a particular software development methodology (i.e. RUP, MSF), and thus software development teams face a compliance problem between the selected development methodology and a pursued particular standard or model. In this research, the particular issue of compliance of Agile Software Development Methodologies (SCRUM, XP, and UPEDU) and the new ISO/IEC 29110 standard is studied. Because the new standard is focused on the software process in very small software development companies or small software project teams in the range from 1 to 25 people, and the Agile Software Development Methodologies (ASDMs) are primarily for same targets, this study is important. The ISO/IEC 29110 standard contains two processes: Project Management and Software Implementation. This study is focused on the first process. The main findings indicate that the UPEDU and SCRUM methodologies present and high compliance level with the ISO/IEC 29110 Project Management process, while XP has a moderate level. Thus, software developer teams interested in achieving compliance with the ISO/IEC 29110 Project Management process can count with two ASDMs. However, a full compliance study (with both Project Management and Software Implementation) is still missing.

[1]  Claude Y. Laporte,et al.  Systems and Software Engineering Standards for Very Small Entities: Implementation and Initial Results , 2014, 2014 9th International Conference on the Quality of Information and Communications Technology.

[2]  Brian Gallagher,et al.  The Rational Unified Process and the Capability Maturity Model - Integrated Systems/Software Engineering , 2001 .

[3]  Paula Monteiro,et al.  Tailoring CMMI-DEV and RUP frameworks for ML2/3-compliance analysis , 2014 .

[4]  William J. Kettinger,et al.  Business Process Change: A Study of Methodologies, Techniques, and Tools , 1997, MIS Q..

[5]  Rory V. O'Connor,et al.  The influence of SPI on business success in software SMEs: An empirical study , 2012, J. Syst. Softw..

[6]  David A. Marca,et al.  A software engineering approach and tool set for developing Internet applications , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[7]  Donald H. Liles,et al.  Use of IDEF0 for the design and specification of methodologies , 1995 .

[8]  Rory V. O'Connor,et al.  An Innovative Approach to the Development of an International Software Process Lifecycle Standard for Very Small Entities , 2014, Int. J. Inf. Technol. Syst. Approach.

[9]  Claude Y. Laporte,et al.  Software project management with ISO/IEC 29110 , 2012 .

[10]  Tsun Chow,et al.  A survey study of critical success factors in agile software projects , 2008, J. Syst. Softw..

[11]  Giancarlo Succi,et al.  Compatibility, standards, and software production , 1998, STAN.

[12]  Venkataraman Ramesh,et al.  An analysis of research in computing disciplines , 2004, CACM.

[13]  Claude Y. Laporte,et al.  A Software Engineering Lifecycle Standard for Very Small Enterprises , 2008, EuroSPI.

[14]  Roberto Tom Price,et al.  Identifying Extensions Required by RUP (Rational Unified Process) to Comply with CMM (Capability Maturity Model) Levels 2 and 3 , 2003, IEEE Trans. Software Eng..

[15]  Ovsei Gelman,et al.  The Case for Conceptual Research in Information Systems , 2008 .

[16]  Claude Y. Laporte,et al.  Towards the provision of assistance for very small entities in deploying software lifecycle standards , 2010, PROFES '10.

[17]  Seiko Shirasaka,et al.  Report on an assessment experience based on ISO/IEC 29110 , 2014, J. Softw. Evol. Process..

[18]  James H. Lambert,et al.  Integration of risk identification with business process models , 2006, Syst. Eng..

[19]  Diane L. Gibson,et al.  Demonstrating the Impact and Benefits of CMMI ® : An Update and Preliminary Results , 2003 .

[20]  Carla Alessandra Lima Reis,et al.  Systematic Literature Review on the Characteristics of Agile Project Management in the Context of Maturity Models , 2014, SPICE.

[21]  Philippe Kruchten,et al.  Yoopeedoo (UPEDU): a process for teaching software process , 2001, Proceedings 14th Conference on Software Engineering Education and Training. 'In search of a software engineering profession' (Cat. No.PR01059).

[22]  Li Zheng,et al.  Re-engineering of the design process for concurrent engineering , 2000 .

[23]  Ovsei Gelman,et al.  CMMI ( SW , DEV , SVC ) Compliance of SDLCs : a Service System View , 2017 .

[24]  Juan Garbajosa Sopeña,et al.  Mapping CMMI Level 2 to Scrum Practices: An Experience Report , 2009 .

[25]  Kent L. Beck,et al.  Embracing Change with Extreme Programming , 1999, Computer.

[26]  Claude Y. Laporte,et al.  A Systems Process Lifecycle Standard for Very Small Entities: Development and Pilot Trials , 2014, EuroSPI.

[27]  E. Gaygısız,et al.  The Organisation for Economic Co-operation and Development (OECD) , 2022 .

[28]  Javier Garzás,et al.  Applying ISO/IEC 12207: 2008 with SCRUM and Agile Methods , 2011, SPICE.