Planned and unplanned meetings in large-scale projects

To succeed with large-scale projects, teams need to coordinate ideas and efforts, which is a core purpose of meetings. We conducted a case study in a large software company where we observed meetings and surveyed 65 members working in large-scale agile projects in Poland, Norway and China. Our results show that employees in the large-scale projects spend, on average, a total of 13.5 hours per week in meetings. The employees spend somewhat more time in ad hoc conversations and unscheduled meetings than they do in scheduled meetings. The majority work in distributed teams, and the size of distributed teams is significantly larger than that of co-located teams. Successful meetings in large-scale projects are critical. We propose a theory of coordination by feedback, which can be used as a basis for future research on meetings in agile software development.

[1]  Viktoria Stray,et al.  Software Tester, We Want to Hire You! an Analysis of the Demand for Soft Skills , 2018, XP.

[2]  Karlos Artto,et al.  Inter-Team Coordination Patterns and Outcomes in Multi-Team Projects , 2013 .

[3]  M BassJulian Artefacts and agile method tailoring in large-scale offshore software development programmes , 2016 .

[4]  Torgeir Dingsøyr,et al.  What Is Large in Large-Scale? A Taxonomy of Scale for Agile Software Development , 2014, PROFES.

[5]  Boris Eisenbart,et al.  Does scheduling matter? When unscheduled decision making results in more effective meetings , 2016 .

[6]  Nils Brede Moe,et al.  Are Daily Stand-up Meetings Valuable? A Survey of Developers in Software Teams , 2017, XP.

[7]  A. V. D. Ven,et al.  Determinants of Coordination Modes within Organizations , 1976 .

[8]  Henry Mintzberg The Nature of Managerial Work , 1974, Operational Research Quarterly (1970-1977).

[9]  Julian M. Bass,et al.  Artefacts and agile method tailoring in large-scale offshore software development programmes , 2016, Inf. Softw. Technol..

[10]  James D. Thompson Organizations in Action: Social Science Bases of Administrative Theory , 1967 .

[11]  Marthe Berntzen,et al.  Coordination in Large-Scale Agile Software Development , 2019, XP Workshops.

[12]  S. Rogelberg,et al.  "Not another meeting!" Are meeting time demands related to employee well-being? , 2006, The Journal of applied psychology.

[13]  Hans-Jürgen Hippler,et al.  Response Alternatives: The Impact of Their Choice and Presentation Order , 2011 .

[14]  Alexander Scheerer,et al.  Coordination in Large-Scale Agile Software Development , 2017 .

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

[16]  Robert Smith,et al.  The Meeting. , 1981, Journal of the Mississippi State Medical Association.

[17]  L. Sproull,et al.  Coordinating Expertise in Software Development Teams , 2000 .

[18]  J. Hackman,et al.  A theory of team coaching , 2005, IEEE Engineering Management Review.

[19]  Ann M. Morrison,et al.  Studies of managerial work : results and methods , 1978 .

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

[21]  Yngve Lindsjørn,et al.  Obstacles to Efficient Daily Meetings in Agile Development Projects: A Case Study , 2013, 2013 ACM / IEEE International Symposium on Empirical Software Engineering and Measurement.