Demo Data from EDBT 2026 / reviewers in the wild / expert
Saskia Bick
dblp:147/4764
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 2018
0000-0002-0189-1285ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Empirical software engineering · 50% Requirements engineering and software design · 50% | |
| Human-computer interaction and pervasive computing
1 paper |
Collaborative and social computing · 100% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering
developer studies |
0.3 | 1 | 2018 | Coordination Challenges in Large-Scale Software Development: A Case Study of Planning Misalignment in Hybrid Settings · IEEE Trans. Software Eng. 2018 |
Requirements engineering and software design › software process
project planning |
0.3 | 1 | 2018 | Coordination Challenges in Large-Scale Software Development: A Case Study of Planning Misalignment in Hybrid Settings · IEEE Trans. Software Eng. 2018 |
Methods — techniques the papers use, named apart from their topics
interviews · 0.7grounded theory · 0.7case study · 0.7
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2018 | Coordination Challenges in Large-Scale Software Development: A Case Study of Planning Misalignment in Hybrid SettingsabstractAchieving effective inter-team coordination is one of the most pressing challenges in large-scale software development. Hybrid approaches of traditional and agile development promise combining the overview and predictability of long-term planning on an inter-team level with the flexibility and adaptability of agile development on a team level. It is currently unclear, however, why such hybrids often fail. Our case study within a large software development unit of 13 teams at a global enterprise software company explores how and why a combination of traditional planning on an inter-team level and agile development on a team level can result in ineffective coordination. Based on a variety of data, including interviews with scrum masters, product owners, architects and senior management, and using Grounded Theory data analysis procedures, we identify a lack of dependency awareness across development teams as a key explanation of ineffective coordination. Our findings show how a lack of dependency awareness emerges from misaligned planning activities of specification, prioritization, estimation and allocation between agile team and traditional inter-team levels and ultimately prevents effective coordination. Knowing about these issues, large-scale hybrid projects in similar contexts can try to better align their planning activities across levels to improve dependency awareness and in turn achieve more effective coordination. Saskia Bick, Kai Spohrer, Rashina Hoda, Alexander Scheerer, Armin Heinzl |
IEEE Trans. Software Eng. | 1 |