The retrospective is a crucial component of the agile software development process. In previous studies of retrospectives in undergraduate team software development projects, students exhibited limited and shallow reflection. We speculate that this is due to students' limited experience with reflection and the absence of clear guidance for engaging in deep reflection during agile retrospectives. To explore the potential for a pedagogical intervention to foster deeper reflection in retrospectives, we present an empirical comparison of a standard retrospective model against an enhanced retrospective model that scaffolds deeper levels of reflection by prompting students to justify and critique their practices and weigh alternative approaches. Through a systematic classification of the reflection level of statements made during individual brainstorming and team discussion phases of retrospectives, our study found that the enhanced model led to individuals and teams engaging in significantly higher levels of reflection. Our findings contribute to improving software engineering education by demonstrating the efficacy of an enhanced pedagogical model for team retrospectives.
more »
« less
Introducing Agility into Research Teams
In this paper, we propose an innovative practice based on agile software development methods. This research approach introduces agility into learning of research in an academic environment, resulting in an Agile Research Team. Such a research team follows an agile approach, based on modifications to the Scrum approach, to collaboratively learn about research, and to manage research projects and the researchers involved. Success in research requires self-motivation, collaboration, and knowledge exchange. Traditional research occurs in top-down research groups that are led by a leading researcher, who oversees postdoctoral researchers and Ph.D. students, who in turn manage graduate and undergraduate level students. It is up to individual researchers to stay motivated, to acquire the necessary skills to conduct research, and, oftentimes, to decide what the following steps are. Much like effective research groups, agile software development approaches rely on individuals to form self-organizing and motivated teams to deliver technical excellence. Agile software development teams also require an environment of sharing knowledge between senior and junior developers. Agile approaches can facilitate the efficient exchange of knowledge due to a strong dependency on face-to-face communication and teamwork. With the emerging adoption of agile methods for software development in industry and its ability to expedite projects’ delivery, we argue that such approaches can potentially provide similar benefits for researchers and students in academia. The advantages that agile methods provide are twofold: the ability to respond faster to change, and a shorter feedback loop, which facilitates the learning of how to conduct research. This paper explores the impactful benefits of using an agile approach to manage research team projects to keep researchers motivated, enhance the learning of knowledge and research skills, increase scalability, and foster inclusivity. This paper will also present the roles, responsibilities, and processes defined for managing an Agile Research Team to support adoption of the approach with other research teams. In addition, results and lessons learned are presented following our experience with using the approach as described in this work.
more »
« less
- Award ID(s):
- 1920780
- PAR ID:
- 10466136
- Date Published:
- Journal Name:
- 2022 IEEE Frontiers in Education Conference (FIE)
- Page Range / eLocation ID:
- 1 to 8
- Format(s):
- Medium: X
- Sponsoring Org:
- National Science Foundation
More Like this
-
-
Metacognition is widely acknowledged as a key soft skill in collaborative software development. The ability to plan, monitor, and reflect on cognitive and team processes is crucial to the efficient and effective functioning of a software team. To explore students' use of reflection--one aspect of metacognition--in undergraduate team software projects, we analyzed the online chat channels of teams participating in agile software development projects in two undergraduate courses that took place exclusively online (n = 23 teams, 117 students, and 4,915 chat messages). Teams' online chats were dominated by discussions of work completed and to be done; just two percent of all chat messages showed evidence of reflection. A follow-up analysis of chat vignettes centered around reflection messages (n = 63) indicates that three-fourths of the those messages were prompted by a course requirement; just 14\% arose organically within the context of teams' ongoing project work. Based on our findings, we identify opportunities for computing educators to increase, through pedagogical and technological interventions, teams' use of reflection in team software projects.more » « less
-
null (Ed.)What might it mean to be an agile academic department? An agile college? An agile university? “Agile”, as used here, refers to practices and frameworks in software development and deployment, such as Scrum, Extreme Programming, and Crystal Clear. The Agile movement’s founding documents, the Agile Manifesto and its accompanying Agile Principles [https://agilemanifesto.org/], were published by leading software engineering researchers in February of 2001. The Manifesto staked out distinction with the prevailing software development approach at the time, called planned development and otherwise known as waterfall. The Agile Manifesto states, "We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: "Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan "That is, while there is value in the items on the right, we value the items on the left more.” Since the Manifesto’s publication, Agile use has expanded from its then primarily application in software development into a wide range of activities, from rocket motors (Space X), to race car development (Wikispeed), to finance (World Bank), to human resources (ING). Denning postulates Three Laws of the Agile Mindset: (1) The Law of the Small Team, in which small cross-functions teams work in short iterations receiving regular customer feedback; (2) The Law of the Customer, in which delighting the customer is taken as the ultimate purpose for any enterprise; and (3) The Law of the Network, in which networks of small teams act, having trust in the competency of each other, act like small teams in themselves [The Age of Agile: How Smart Companies Are Transforming the Way Work Gets Done. AMACOM, 2018]. Academic enterprises have unique attributes — recurring, months long, instructional terms; “customers” (students) whose short-term dissatisfaction can be part of the path to long-term success; industrial stakeholders who influence program direction and focus to satisfy hiring needs; generation of new knowledge, often with financial support from government agencies and industry; service to the profession and to our institutions. Using Denning’s Laws as a framing, we present possible approaches to employing agile within an academic department and discuss potential expansion of such to the level of a college and even an entire university.more » « less
-
The retrospective, or retro, is a fundamental component of the Agile process, widely used in both software engineering courses and industry. In a retro, teams come together at the end of a sprint to reflect on their team's performance. We conducted an empirical study to explore three research questions concerning retros in undergraduate team projects: (1) What do students reflect on? (2) What is the quality of their reflections? (3) How do teams' retros vary in terms of content and quality? Our study analyzed a corpus of 963 statements documented in the retros of 32 undergraduate software teams (n = 182 students) enrolled in four software engineering courses at two North American universities. A content analysis revealed that teams reflected most often on their work, communication, and collaboration practices. Nearly a third of teams' reflections focused on their general work practices, while nearly half focused on specific areas of the software development lifecycle---most prominently, pull requests, issues, and coding/testing/debugging. An analysis of the quality of teams' retro reflections showed that only 13% provided justification for a strategy to be stopped, continued, or started. An analysis of team-by-team results indicated significant differences in teams' retro content and quality. We compare these results to previous studies of retros in academia and industry, and consider their implications for software engineering education.more » « less
-
more » « less
Abstract Interdisciplinary teams are on the rise as scientists attempt to address complex environmental issues. While the benefits of team science approaches are clear, researchers often struggle with its implementation, particularly for new team members. The challenges of large projects often weigh on the most vulnerable members of a team: trainees, including undergraduate students, graduate students, and post‐doctoral researchers. Trainees on big projects have to navigate their role on the team, with learning project policies, procedures, and goals, all while also training in key scientific tasks such as co‐authoring papers. To address these challenges, we created and participated in a project‐specific, graduate‐level team science course. The purposes of this course were to: (1) introduce students to the goals of the project, (2) build trainees' understanding of how big projects operate, and (3) allow trainees to explore how their research interests dovetailed with the overall project. Additionally, trainees received training regarding: (1) diversity, equity & inclusion, (2) giving and receiving feedback, and (3) effective communication. Onboarding through the team science course cultivated psychological safety and a collaborative student community across disciplines and institutions. Thus, we recommend a team science course for onboarding students to big projects to help students establish the skills necessary for collaborative research. Project‐based team science classes can benefit student advancement, enhance the productivity of the project, and accelerate the discovery of solutions to ecological issues by building community, establishing a shared project vocabulary, and building a workforce with collaborative skills to better answer ecological research questions.
- Free Publicly Accessible Full Text
-
Accepted Manuscript1.0
- Conference Paper:
- https://doi.org/10.1109/FIE56618.2022.9962665
