The daily stand-up meeting: A grounded theory study
Introduction
Common to all agile methods is an emphasis on communication and the human side of software development (Merisalo-Rantanen et al., 2005). Conducting a daily stand-up meeting (DSM) is an important practice in the agile methods Scrum and Extreme Programming (XP) to improve communication in software projects. The DSM is often conducted as a 15-min morning meeting to share information that is supposed to be relevant to the teams’ progress. The term DSM used in this article originates from XP. Other names of the practice are frequent, short meetings (Rising, 2002), morning roll call (Anderson, 2003), daily huddle meeting (Paez et al., 2005), daily meeting (Pikkarainen et al., 2008), and daily Scrum meeting (Sutherland and Schwaber, 2013a).
The software development industry has extensively adopted agile practices, many of which have been thoroughly investigated (Dingsøyr et al., 2012). However, little research has been conducted on the DSM, which may be surprising given that the DSM is the most used agile practice according to a 2014 survey (VersionOne, 2015). In that survey, the DSM was used by 85% of the organizations that employed agile development. The global cost of conducting the DSM is immense if one supposes that the majority of the software development teams in the world daily interrupt their development tasks to spend 15 min on the DSM.
In this article, we report a study on how DSMs are conducted and what affects the attitude towards them. We propose a theory of DSMs that includes propositions among DSM constructs, with explanations grounded in data. The data was generated from 79 observations of DSMs of eight software teams in three companies and 60 interviews with team members, Scrum Masters and product owners that worked in these teams and an additional set of four teams.
A few studies have investigated the DSM as one of several agile practices. Pikkarainen et al. (2008) studied the impact of agile practices on communication and found that DSMs kept developers, project leaders and customers aware of the project status and helped the developers resolve design issues faster. Paasivaara et al. (2008) examined agile practices in global software development and found that DSMs helped reveal problems early and improved transparency between sites. Moe et al. (2010) studied the nature of self-managing agile teams and found that DSMs were mostly used by a Scrum Master to obtain an overview of the progress and ongoing project activities. McHugh et al. (2012) examined how agile practices impact trust and found that DSMs helped the teams function more cohesively. Dorairaj et al. (2012) studied dynamics in distributed teams and found that the practice promoted team interaction and the building of a “one team” mindset. Yu and Petter (2014) argue that the DSM may contribute to build shared mental models within a team. The results of an experiment conducted by Hasnain et al. (2013) suggest that introducing DSMs may be a powerful way to improve trust in agile software teams.
The DSM was the primary study topic in some of our earlier research. In a longitudinal study, DSMs led to a greater commitment to a failing course of action (Stray et al., 2012b). In another study, we investigated the proportion of time spent on different topics. The largest topic category was discussing problems and possible solutions (Stray et al., 2012a). In yet another study, we identified thirteen obstacles to efficient DSMs and suggested ways to overcome them (Stray et al., 2013).
Much can be learned from case studies by doing a secondary grounded theory analysis (Glaser, 2001, p. 97). This study builds on our previous research. Among the 60 interviews of this study, 7 were reused from the study reported in (Stray et al., 2011), 17 were reused from the study reported in (Stray et al., 2012b) and 9 were reused from the study reported in (Stray et al., 2013). The remaining 27 were new interviews for this study. We reanalyzed the case study material and iteratively compared it with newly collected material. This study also contributes to increasing the understanding of the costs and benefits of DSMs, which is important for improving agile software development. Finally, our work answers a call for more empirically based theories in software engineering (Herbsleb and Mockus, 2003, Hannay et al., 2007, Sjøberg and Dybå, 2007).
The remainder of this paper is organized as follows. Section 2 outlines relevant background literature. Section 3 describes the research methods used. Section 4 reports our results. Section 5 discusses the results, limitations of the study and future work. Section 6 concludes.
Section snippets
Background
This section gives a brief introduction to the field of meetings in general, the DSM in agile development and daily meetings in other disciplines.
Research method
The motivation for our research was to increase the understanding of which factors contribute to effective teamwork because teams are the fundamental organizational unit through which agile software projects are executed. We chose grounded theory as our research method because it is considered suitable for pursuing a general understanding of a phenomenon; that is, when a researcher asks “What is going on here?” (Glaser, 1978).
Results: an initial theory of DSM
This section describes the principal results of the study in the form of an initial theory of DSMs, shown in Fig. 5. The theory is summarized in Table 7 using the four-component structure outlined in Sjøberg et al. (2008). The constructs are the basic elements of the theory, the propositions are the interactions among the constructs, the explanations describe why the propositions are as specified and the scope of the theory describes the universe of discourse in which the theory is applicable.
Discussion
On the basis of our findings, this section provides a normative definition of what we now will denote a stand-up meeting and a set of guidelines for how to conduct such a meeting. This section also discusses limitations of our study and issues for future research.
Conclusion
Most views and claims about DSMs reported in the literature are based on anecdotal evidence. In contrast, we conducted a grounded theory study of 12 agile teams in three companies. An initial theory of DSM was proposed that consists of seven constructs and six propositions.
We identified factors that affected the DSM attitude positively and negatively. Considering the popularity of DSMs, it is surprising that we found participants to be almost neutral about DSMs on average, although slightly
Acknowledgments
We are grateful to Yngve Lindsjørn, Nils Brede Moe and Øystein Ingebrigtsen for assisting with data collection and to the many participants who shared their experiences with us and generously welcomed us for observations. We thank the anonymous referees for valuable comments. This work was supported by the TeamIT project funded by the Research Council of Norway through Grant no. 193236/I40.
Viktoria Stray received the MSc degree in computer science from the Norwegian University of Science and Technology (NTNU) in 2007 and the PhD degree in software engineering from the University of Oslo in 2014. She has three years industry experience from working as a consultant at Accenture and is a certified NLP Master Business Coach from the Norwegian Coaching and NLP Academy. Currently she is a postdoctoral fellow at the University of Oslo. Her research interests include software development
References (91)
- et al.
Virtual team meetings: an analysis of communication and context
Comput. Hum. Behav.
(2007) - et al.
Collaboration at work: An integrative multilevel conceptualization
Hum. Resour. Manag. Rev.
(2012) - et al.
What makes teams work: group effectiveness research from the shop floor to the executive suite
J. Manag.
(1997) - et al.
A decade of agile methodologies: towards explaining agile software development
J. Syst. Softw.
(2012) - et al.
Obstacles to decision making in Agile software development teams
J. Syst. Softw.
(2012) - et al.
A teamwork model for understanding an agile team: a case study of a Scrum project
Inf. Softw. Technol.
(2010) - et al.
Understanding agile software development practices using shared mental models theory
Inf. Softw. Technol.
(2014) - et al.
Employees' feelings about more meetings: an overt analysis and recommendations for improving meetings
Manag. Res. Rev.
(2012) - et al.
Morning report: focus and methods over the past three decades
Acad. Med.
(2000) Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results
(2003)
Qualitative evaluation of regular morning meetings aimed at improving interdisciplinary communication and patient outcomes
Int. J. Nurs. Pract.
Lean IT: Enabling and Sustaining Your Lean Transformation
The effects of stand-up and sit-down meeting formats on meeting outcomes
J. Appl. Psychol.
The Business of Talk: Organizations in Action
Verifying and validating software requirements and design specifications
IEEE Softw.
Tactical approaches for alleviating distance in global software development
IEEE Softw.
Meeting design characteristics and attendee perceptions of staff/team meeting quality
Group Dynamics: Theory, Research, and Practice
Capturing the complexity in advanced technology use: adaptive structuration theory
Organ. Sci.
A conceptual framework of teamwork measurement
Are case studies more than sophisticated storytelling? Methodological problems of qualitative empirical research mainly based on semi-structured interviews
Qual. Quant.
Understanding team dynamics in distributed agile software development
Awareness and coordination in shared workspaces
How to Make Meetings Work: The New Interaction Method
What works for whom, where, when, and why? on the role of context in empirical software engineering
Why is a third of your time wasted in meetings?
J. Manag. Dev.
Toward a theory of situation awareness in dynamic systems
Hum. Factors
The Discovery of Grounded Theory: Strategies for Qualitative Research
Theoretical Sensitivity: Advances in the Methodology of Grounded Theory
Basics of Grounded Theory Analysis: Emergence vs Forcing
Doing Grounded Theory: Issues and Discussions
The Grounded Theory Perspective: Conceptualization Contrasted with Description
The Grounded Theory Perspective III: Theoretical Coding
Getting Out of the Data: Grounded Theory Conceptualization
Grounded theory: the missing methodology on the interpretivist agenda
Qual. Mark. Res
A systematic review of theory use in software engineering experiments
IEEE Trans. Softw. Eng.
A study of interaction and consensus in different sized groups
American Sociological Review
Using experimental games to understand communication and trust in Agile software teams
Coop. Hum. Asp. Softw. Eng.
Formulation and preliminary test of an empirical theory of coordination in software engineering,
Global software engineering: the future of socio-technical coordination
Theoretical coding in grounded theory methodology
Ground. Theory Rev.
The influence of culture, community, and the nested‐self in the stress process: advancing conservation of resources theory
Appl. Psychol.: Int. Rev.
Teamwork quality and the success of innovative projects: a theoretical concept and empirical evidence
Organ. Sci.
Work interrupted: a closer look at the role of interruptions in organizational life
Acad. Manag. Rev.
Meetings matter: effects of team meetings on team and organizational success
Small Group Res.
Cited by (91)
Theories in Agile Software Development: Past, Present, and Future Introduction to the XP 2020 Special Section
2022, Information and Software TechnologyContinuous software security through security prioritisation meetings
2022, Journal of Systems and SoftwareCitation Excerpt :This is in line with experiences from similar techniques (Fig. 2). The effect was however linked to documentation; there was a need to ensure key discussion points were documented (and not lost Cruzes et al., 2018; Tøndel et al., 2019b), and visible documentation supported the discussions (Stray et al., 2016). This study is not conclusive on how to structure the discussions and the documentation.
A software-based cost estimation technique in scrum using a developer's expertise
2022, Advances in Engineering SoftwareCitation Excerpt :This feedback consists of some values that will give development experience and categorization of project type (easy/ complex). In this review session, [53–55] team members like project managers, developers, and team leaders will communicate with each other and update which modules have been completed and which ones are new for the development team. Fig. 3 shows the solution scenario:
Analysing outsourced and insourced public infrastructure projects’ performance in a provincial department of public works: a grounded theory approach
2024, Journal of Engineering, Design and TechnologyCharacterizing Software Maintenance Meetings: Information Shared, Discussion Outcomes, and Information Captured
2024, Proceedings - International Conference on Software EngineeringAgile work practices: opportunities and risks for occupational well-being
2023, Gruppe. Interaktion. Organisation. Zeitschrift fur Angewandte Organisationspsychologie
Viktoria Stray received the MSc degree in computer science from the Norwegian University of Science and Technology (NTNU) in 2007 and the PhD degree in software engineering from the University of Oslo in 2014. She has three years industry experience from working as a consultant at Accenture and is a certified NLP Master Business Coach from the Norwegian Coaching and NLP Academy. Currently she is a postdoctoral fellow at the University of Oslo. Her research interests include software development methods and socio-technical factors influencing software project success.
Dag I.K. Sjøberg received the MSc degree in computer science from the University of Oslo in 1987 and the PhD degree in computing science from the University of Glasgow in 1993. He has five years of industry experience as a developer and group leader. In 2001, he formed the Software Engineering Department at Simula Research Laboratory and was its leader until 2008, when it was number 1 in a ranking by the Journal of Systems and Software. Since 1999 he has been a full professor of software engineering at the University of Oslo. Sjøberg was an Associate Editor of Empirical Software Engineering from 2002 to 2009 and an Associate Editor of IEEE Transactions on Software Engineering from 2010 to 2014. His main research interests are the software life cycle, including agile and lean development processes, skill assessment, and empirical research methods in software engineering. Sjøberg is a member of IEEE and ACM.
Tore Dybå received the MSc degree in electrical engineering and computer science from the Norwegian Institute of Technology in 1986, and the Dr. Ing. degree in computer and information science from the Norwegian University of Science and Technology in 2001. He has eight years of industry experience from Norway and Saudi Arabia. He is a chief scientist and research manager at SINTEF ICT and a professor at the University of Oslo. For the period 2001–2012, he was ranked as the top scholar worldwide in agile software development by the Journal of Systems and Software. He was on the editorial board of Empirical Software Engineering from 2007 to 2013. Since 2011 he has beeneditor of the Voice of Evidence column in IEEE Software, and since 2013 he has been on the editorial board of Information and Software Technology. His research interests include evidence-based software engineering, software process improvement, and agile software development.