Phase 3-Prop
Prog. PhD STI
Adm. - Grad. 2017 - 
Dir.; Codir. Stéphane Gagnon; Raul Valverde

Hybrid Development Lifecycles for Open-Source Standards Development: Integrating Disciplined and Agile Methods in the Business Technology Management Body of Knowledge

Torres, Beatriz

The development of IT management standards typically follows a very disciplined lifecycle with a highly proprietary and closed copyright. Standards development with an Open-Source license tends to follow more agile methods but lack the rigor and validation of proprietary standards. We propose to overcome these deficiencies by developing and testing a new standards development lifecycle that integrate both disciplined and agile methods. The target references for these 2 methods are: Eclipse Process Framework, based on the OMG Software Process Engineering Metamodel or SPEM (v2.0, 2018); and the OMG Essence Kernel (v1.2, 2018), developed in 2014 by Ivar Jacobson (inventor of UML and RUP) and his team. We apply the qualitative methods prescribed in Empirical Software Engineering, namely for data collection by Lethbridge, et al. (2005), and for case study reporting by Runeson et Höst (2009). The study context is the Business Technology Management Body of Knowledge (BTM BOK), a standards development initiative integrating 60+ existing open-source specifications in IT management. We follow an action research process, accompanying the BOK development team for a year, working collaboratively with a community of 100+ contributors developing standards assets. The effectiveness of the 3 methods (disciplined, agile, hybrid) are tested iteratively through the integration of specific subsets of open-source standards within the BTM BOK. Both GitLab repo analysis & surveys measure improvements of methods. References: Lethbridge, T. C., Sim, S. E., & Singer, J. (2005). Studying software engineers: Data collection techniques for software field studies. Empirical software engineering, 10(3), 311-341.; Runeson, P., & Höst, M. (2009). Guidelines for conducting and reporting case study research in software engineering. Empirical software engineering, 14(2), 131-164.




Go to top