Journal of Systems and Software· 2026Q1
Large-scale agile software development and coordination: A teaching case
- 1citations
- Q1SCImago
- 2026year
Short summary
A teaching case study details coordination challenges in a large Nordic public tech company scaling agile development from a few to twenty teams, highlighting issues with inter-team dependencies, varied work methods, and stakeholder pressure.
AI-generated from the title and abstract; the full text is not read.
Key points
- The case study focuses on Norda, a Nordic public tech company that scaled its agile development from a handful of teams to approximately twenty.
- Scaling led to coordination challenges due to inter-team dependencies, uneven ways of working, and stakeholder pressure.
- Students must address three core dilemmas: formalization vs. self-organization, managing dependencies vs. reducing them, and co-located vs. digital-first collaboration.
- The case aims to help students analyze coordination needs, evaluate trade-offs, and develop recommendations for complex multi-team environments.
AI-generated from the title and abstract; the full text is not read.
Abstract
This teaching case examines coordination in large-scale agile development through a case based on a Nordic public technology company that provides national digital infrastructure for travel planning and ticketing. The case company, Norda, began with a handful of cross-functional teams and one main client, then expanded to roughly twenty teams as new clients joined and platform complexity increased. The case traces how inter-team dependencies, uneven ways of working, and stakeholder pressure created coordination challenges and delays for a national platform with public visibility. Students engage with three interconnected dilemmas that frequently arise when scaling agile. The first concerns whether to formalize coordination through stronger program governance and shared routines or mycolorminor to maintain a high degree of team-level self-organization. The second asks whether to improve daily coordination of existing dependencies or reorganize teams and architecture to reduce dependencies at the source. The third focuses on whether to emphasize co-located collaboration or adopt a digital-first approach suited to hybrid and distributed work. Grounded in multiple empirical studies of coordination in large-scale agile development, the case challenges students to propose coherent choices across the three dilemmas and to justify expected effects on predictability, quality, and motivation. The case offers two alternative tracks depending on student experience level and is designed to support learning outcomes related to analyzing coordination needs in large-scale agile development, evaluating strategic trade-offs, and creating actionable recommendations for a complex multi-team setting.
The authors' abstract, as published at the source. Journal of Systems and Software, 2026 · DOI ↗
The rest is in the Pofolia app
Takeaways and questions to the paper; new summaries every day for your field. Free.
Sign in on the web to openField: Information Systems
Information SystemsComputer Science