Team Red: Experiences of an agile task force supporting multiple software products

Controlling CERN’s accelerator complex requires a significant number of domain specific applications. Typically these are developed by small teams comprised of a staff member with essential domain knowledge, and 1 or 2 students or graduates staying for 1-to-3 years. Developments may span over months or even years, according to the complexity and requirements, which may evolve significantly over time to follow the accelerator programme. After some years, applications need to be consolidated or re-written to follow the inevitable technology evolution and remain secure, hardware compatible, and based on technologies for which skills exist in the marketplace. This development approach has produced results, but is inefficient due to the isolated developments sometimes leading to black-box solutions that eventually need reverse-engineering. Furthermore, long-term staff members can become siloed within specific domains, increasing the risk of single points of failure. This paper shares the results and experience gained over 18 months in applying a more agile, task-force team-based approach to address the aforementioned limitations and inefficiencies. Together with the application of micro-frontend architectures, the team has been able to develop and maintain multiple applications with enhanced distribution of both domain and technical knowledge, as well as predictable delivery times. The team’s workflows will be described, together with challenges faced and lessons learned.

Publication Details

Journal
JACOW
Published
2025-12-05
DOI
https://doi.org/10.18429/jacow-icalepcs2025-tubg005
Primary Topic
Scientific Computing and Data Management
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

Team Red: Experiences of an agile task force supporting multiple software products

JACOW
Scientific Computing and Data Management
article

Team Red: Experiences of an agile task force supporting multiple software products

article en

Abstract

Controlling CERN’s accelerator complex requires a significant number of domain specific applications. Typically these are developed by small teams comprised of a staff member with essential domain knowledge, and 1 or 2 students or graduates staying for 1-to-3 years. Developments may span over months or even years, according to the complexity and requirements, which may evolve significantly over time to follow the accelerator programme. After some years, applications need to be consolidated or re-written to follow the inevitable technology evolution and remain secure, hardware compatible, and based on technologies for which skills exist in the marketplace. This development approach has produced results, but is inefficient due to the isolated developments sometimes leading to black-box solutions that eventually need reverse-engineering. Furthermore, long-term staff members can become siloed within specific domains, increasing the risk of single points of failure. This paper shares the results and experience gained over 18 months in applying a more agile, task-force team-based approach to address the aforementioned limitations and inefficiencies. Together with the application of micro-frontend architectures, the team has been able to develop and maintain multiple applications with enhanced distribution of both domain and technical knowledge, as well as predictable delivery times. The team’s workflows will be described, together with challenges faced and lessons learned.

JACOW
Openalex Percentile: Top 20%
Scientific Computing and Data Management
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.