Obstacles to Efficient Daily Meetings in Agile Development Projects: A Case Study

Context: Most of the software organizations that use agile methods organize daily team meetings. Aim: Our aim was to understand how daily meetings are conducted and identify obstacles that reduce their efficiency. Method: We observed 56 daily meetings and conducted 21 interviews in three different teams in two countries. We used the repertory grid technique in the interviews and to analyze the results. Results: We identified thirteen obstacles. The four most prominent ones were: (1) The daily meetings lasted too long (on average, 22 minutes instead of the scheduled 15 minutes). (2) In the meetings that were not self-organized, team members reported to the Scrum Master instead of sharing information among all team members. (3) The interruption caused by daily meetings required substantially more time than the actual meeting time due to overhead before and after the meetings. (4) Several team members had negative attitudes towards the daily meetings. Conclusion: Organizers of daily meetings should evaluate whether the obstacles we have identified are present in their organization and consider our suggestions to remove or reduce these obstacles.

[1]  Beverley G. Hope,et al.  Author's Personal Copy the Journal of Systems and Software Coordination in Co-located Agile Software Development Projects , 2022 .

[2]  Joseph A. Allen,et al.  Meeting Design Characteristics and Att endee Perceptions of Staff/T eam Meeting Quality , 2011 .

[3]  Jay F. Nunamaker,et al.  Meeting analysis: findings from research and practice , 2001, Proceedings of the 34th Annual Hawaii International Conference on System Sciences.

[4]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[5]  Stephanie D. Teasley,et al.  Rapid Software Development through Team Collocation , 2002, IEEE Trans. Software Eng..

[6]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[7]  Pekka Abrahamsson,et al.  The impact of agile practices on communication in software development , 2008, Empirical Software Engineering.

[8]  Jan Pries-Heje,et al.  Why Scrum Works: A Case Study from an Agile Distributed Project in Denmark and India , 2011, 2011 AGILE Conference.

[9]  Richard Bell,et al.  A manual for repertory grid technique , 1977 .

[10]  Thomas A. O'Neill,et al.  Team Meeting Attitudes , 2012 .

[11]  Steven G. Rogelberg,et al.  The Science and Fiction of Meetings , 2007 .

[12]  Matthew B. Miles,et al.  Qualitative Data Analysis: An Expanded Sourcebook , 1994 .

[13]  Aybüke Aurum,et al.  Investigating Daily Team Meetings in Agile Software Projects , 2012, 2012 38th Euromicro Conference on Software Engineering and Advanced Applications.

[14]  Steven G. Rogelberg,et al.  Perceived Meeting Effectiveness: The Role of Design Characteristics , 2009 .

[15]  Tore Dybå,et al.  Escalation of Commitment: A Longitudinal Case Study of Daily Meetings , 2012, XP.

[16]  Bent Jensen,et al.  Cross-Continent Development Using Scrum and XP , 2003, XP.

[17]  Mira Kajko-Mattsson,et al.  Historical Perspective of Two Process Transitions , 2009, 2009 Fourth International Conference on Software Engineering Advances.

[18]  Kirsimarja Blomqvist,et al.  Managing distance in a global virtual team: the evolution of trust through technology‐mediated relational communication , 2005 .

[19]  Steven G. Rogelberg,et al.  Wasted Time and Money in Meetings , 2012 .

[20]  Andraž Cej,et al.  Agile software development with Scrum , 2010 .

[21]  Joseph A. Allen,et al.  Employees' feelings about more meetings: An overt analysis and recommendations for improving meetings , 2012 .

[22]  Peter Middleton,et al.  Lean Software Management: BBC Worldwide Case Study , 2012, IEEE Transactions on Engineering Management.

[23]  Helen Sharp,et al.  XP culture: why the twelve practices both are and are not the most significant thing , 2003, Proceedings of the Agile Development Conference, 2003. ADC 2003.

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

[25]  Marissa L. Shuffler,et al.  Employee satisfaction with meetings: A contemporary facet of job satisfaction , 2010 .

[26]  Henning Bang,et al.  Effectiveness in top management group meetings: the role of goal clarity, focused communication, and learning behavior. , 2010, Scandinavian journal of psychology.

[27]  Kieran Conboy,et al.  Using Agile Practices to Build Trust in an Agile Team: A Case Study , 2010, ISD.

[28]  M. Hoegl,et al.  Teamwork Quality and the Success of Innovative Projects , 2001 .

[29]  Pamela Jordan Basics of qualitative research: Grounded theory procedures and techniques , 1994 .

[30]  Allen C. Bluedorn,et al.  The effects of stand-up and sit-down meeting formats on meeting outcomes , 1999 .

[31]  Andrew Begel,et al.  Coordination in Large-Scale Software Development: Helpful and Unhelpful Behaviors , 2009 .

[32]  Ch. Srikanth,et al.  Coordination in Large-Scale Software Development : Helpful and Unhelpful Behaviors , 2013 .