Toward Proprietary Software Ecosystem Governance Strategies Based on Health Metrics

Investigating Change and Incident Management in a Proprietary Software Ecosystem - Survival Mode On

“…The goal is to understand the behavior of development teams from the perspective of changes and incidents in the PSECO of a large international insurance organization, based on the study of Costa et al (2021) that the development teams present homogeneous behavior in relation to the proportion among changes and incidents, since these teams should be under the same governance guidelines in PSECO. The research question for our study is: "How do PSECO software development teams behave in relation to their interactions (e.g., incidents and changes) in the productive environment?…”

“…According to ITIL, a change is the addition, modification, or removal of anything that could have an effect on services, and an incident is an unplanned interruption of an IT service. Costa et al (2021) propose an approach to measuring the health of a PSECO and discuss governance strategies that can be implemented based on metrics. Jafari et al (2020) addressed the effective communication between several project actors to control delays and costs in change management.…”

“…According to Jansen et al (2009), SECO is a set of actors functioning as a unit and interacting in a shared market for software and services, centered on a common technological platform. A proprietary SECO (PSECO) can be characterized by the contributions of several products, technologies, and architectures protected by intellectual property and confidence agreement (e.g., SAP) [Costa et al 2021]. The central organization in PSECO is called a keystone.…”