Abstract
AbstractLarge-scale systems development commonly faces the challenge of managing relevant knowledge between different organizational groups, particularly in increasingly agile contexts. Here, there is a conflict between coordination and group autonomy, and it is challenging to determine what necessary coordination information must be shared by what teams or groups, and what can be left to local team management. We introduce a way to manage this complexity using a modeling framework based on two core concepts: methodological islands (i.e., groups using different development methods than the surrounding organization) and boundary objects (i.e., artifacts that create a common understanding across team borders). However, we found that companies often lack a systematic way of assessing coordination issues and the use of boundary objects between methodological islands. As part of an iterative design science study, we have addressed this gap by producing a modeling framework (BOMI: Boundary Objects and Methodological Islands) to better capture and analyze coordination and knowledge management in practice. This framework includes a metamodel, as well as a list of bad smells over this metamodel that can be leveraged to detect inter-team coordination issues. The framework also includes a methodology to suggest concrete modeling steps and broader guidelines to help apply the approach successfully in practice. We have developed Eclipse-based tool support for the BOMI method, allowing for both graphical and textual model creation, and including an implementation of views over BOMI instance models in order to manage model complexity. We have evaluated these artifacts iteratively together with five large-scale companies developing complex systems. In this work, we describe the BOMI framework and its iterative evaluation in several real cases, reporting on lessons learned and identifying future work. We have produced a matured and stable modeling framework which facilitates understanding and reflection over complex organizational configurations, communication, governance, and coordination of knowledge artifacts in large-scale agile system development.
Publisher
Springer Science and Business Media LLC
Reference61 articles.
1. Ale, M.A., Toledo, C.M., Chiotti, O., Galli, M.R.: A conceptual model and technological support for organizational knowledge management. Sci. Comput. Program. 95, 73–92 (2014). https://doi.org/10.1016/j.scico.2013.12.012
2. Alfraihi, H., Lano, K.: The integration of agile development and model driven development—a systematic literature review. In: International Conference on Model-Driven Engineering and Software Development (MODELSWARD), vol. 2, pp. 451–458. SciTePress (2017). https://doi.org/10.5220/0006207004510458
3. Arendt, T., Taentzer, G.: UML model smells and model refactorings in early software development phases. Results of the SPES 2020 Project, AP4, Universität Marburg (2010)
4. Bjarnason, E., Sharp, H.: The role of distances in requirements communication: a case study. Requir. Eng. 22(1), 1–26 (2017). https://doi.org/10.1007/s00766-015-0233-3
5. Boucharas, V., Jansen, S., Brinkkemper, S.: Formalizing software ecosystem modeling. In: 1st International Workshop on Open Component Ecosystems, pp. 41–50 (2009). https://doi.org/10.1145/1595800.1595807