The Product Owner in Large-Scale Agile: An Empirical Study Through the Lens of Relational Coordination Theory

In agile software development, a core responsibility of the product owner (PO) is to communicate business needs to the development team. In large-scale agile software development projects, many teams work toward an overall outcome, but they also need to manage interdependencies and coordinate efficiently. In such settings, POs need to coordinate knowledge about project status and goal attainment both within and across the development teams. Previous research has shown that the PO assumes a wide set of roles. Still, our knowledge about how POs coordinate amongst themselves and with their teams in large-scale agile is limited. In this case study, we explore PO coordination in a large-scale development program through the theoretical lens of Relational Coordination Theory. Our findings suggest that (1) coordination varies depending on the context of each PO, (2) a focus on achieving high-quality communication changes coordination over time, and (3) unscheduled coordination enables of high-quality communication.

[1]  Torgeir Dingsøyr,et al.  A decade of agile methodologies: Towards explaining agile software development , 2012, J. Syst. Softw..

[2]  Viktoria Stray,et al.  Dependency Management in Large-Scale Agile: A Case Study of DevOps Teams , 2019, HICSS.

[3]  R. Saavedra,et al.  Complex interdependence in task-performing groups , 1993 .

[4]  Jody Hoffer Gittell,et al.  Relational Coordination: Coordinating Work through Relationships of Shared Goals, Shared Knowledge and Mutual Respect , 2006 .

[5]  Julian M. Bass,et al.  How product owner teams scale agile methods to large distributed enterprises , 2014, Empirical Software Engineering.

[6]  Casper Lassenius,et al.  Challenges and success factors for large-scale agile transformations: A systematic literature review , 2016, J. Syst. Softw..

[7]  Torgeir Dingsøyr,et al.  Exploring software development at the very large-scale: a revelatory case study and research agenda for agile method adaptation , 2017, Empirical Software Engineering.

[8]  R. Yin.  Case Study Research: Design and Methods , 1984 .

[9]  James Noble,et al.  An Ideal Customer: A Grounded Theory of Requirements Elicitation, Communication and Acceptance on Agile Projects , 2010, Agile Software Development.

[10]  Jody Hoffer Gittell,et al.  Coordinating Mechanisms in Care Provider Groups: Relational Coordination as a Mediator and Input Uncertainty as a Moderator of Performance Effects , 2002 .

[11]  J. H. Gittell.  Relationships between Service Providers and Their Impact on Customers , 2002 .

[12]  Casper Lassenius,et al.  Inter-team coordination in large-scale globally distributed scrum: Do Scrum-of-Scrums really work? , 2012, Proceedings of the 2012 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement.

[13]  Viktoria Stray,et al.  Team Autonomy in Large-Scale Agile , 2019, HICSS.

[14]  R. Wageman.  Interdependence and Group Effectiveness , 1995 .

[15]  Torgeir Dingsøyr,et al.  Coordinating Knowledge Work in Multi-Team Programs: Findings from a Large-Scale Agile Development Program , 2018, ArXiv.

[16]  T. Diefenbach.  Are case studies more than sophisticated storytelling?: Methodological problems of qualitative empirical research mainly based on semi-structured interviews , 2009 .

[17]  Henry Mintzberg.  Mintzberg on management : inside our strange world of organizations , 1991 .

[18]  Jody Hoffer Gittell,et al.  Relational Bureaucracy: Structuring Reciprocal Relationships into Roles , 2012 .

[19]  Lucas Layman,et al.  Coordination in large-scale software teams , 2009, 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering.

[20]  Jody Hoffer Gittell,et al.  New Directions for Relational Coordination Theory , 2011 .

[21]  Claes Wohlin,et al.  Software teams and their knowledge networks in large-scale software development , 2017, Inf. Softw. Technol..

[22]  Torgeir Dingsøyr,et al.  To schedule or not to schedule? An investigation of meetings as an inter-team coordination mechanism in largescale agile software development , 2022, International Journal of Information Systems and Project Management.

[23]  R. Moreland,et al.  Group Versus Individual Training and Group Performance: The Mediating Role of Transactive Memory , 1995 .

[24]  Martha S. Feldman,et al.  Toward a Theory of Coordinating: Creating Coordinating Mechanisms in Practice , 2012, Organ. Sci..

[25]  Torgeir Dingsøyr,et al.  Towards Principles of Large-Scale Agile Development - A Summary of the Workshop at XP2014 and a Revised Research Agenda , 2014, XP Workshops.

[26]  K. Weick.  The Collapse of Sensemaking in Organizations: The Mann Gulch Disaster , 1993 .

[27]  Viktoria Stray,et al.  A Taxonomy of Inter-Team Coordination Mechanisms in Large-Scale Agile , 2017, IEEE Transactions on Software Engineering.

[28]  D. Dougherty.  Interpretive Barriers to Successful Product Innovation in Large Firms , 1992 .

[29]  Nils Brede Moe,et al.  Exploring Norms in Agile Software Teams , 2016, PROFES.