Agile Software Development during the COVID-19 Pandemic: A Technology Company Survey

2022 | HICSS | Citations: 0

Authors: Schmidt, Peter; Gutfreund, Keith

Abstract: A common baseline is that Agile-based software development is conducted by co-lo ... Expand

Abstract: A common baseline is that Agile-based software development is conducted by co-located teams working in well-equipped office workspaces. The COVID-19 pandemic and subsequent lockdowns have cast new light on those assumptions. Suddenly, developers were no longer co-located with their teams and their well-equipped workspaces were vacant. How did the lockdowns, and the speed in which they were implemented, affect developers and development efforts? Did the lockdowns lead to diminished product quality? How was employee productivity impacted? A survey questionnaire was created to answer these questions. Collapse

Topics: productivity co-located work agile software development Scrum pandemic

Methods: survey design methodology Pearson's chi squared test of independence between categorical variables LexisNexis survey design

Conceptualizing Information Systems Development as an Organizational Routine: Implications and Avenues for Research

2022 | ACM SIGMIS Database | Citations: 0

Authors: Vial, Gregory; Rivard, Suzanne

Abstract: Research acknowledges that information systems development (ISD) teams experimen ... Expand

Abstract: Research acknowledges that information systems development (ISD) teams experiment with, overlook, or adapt the methods that they purportedly use. Given this, one stream of research adopts a perspective focused on prescriptions based on the idea of a method. Another stream of research adopts a perspective anchored in the view that human agency plays a critical role in the unfolding of ISD projects. We suggest that our understanding of ISD can be enriched by mobilizing both perspectives. Specifically, we propose a conceptualization of ISD as an organizational routine based on the ontology developed by Feldman and Pentland. We build on the elements of this ontology- (1) the idea of a routine (the ostensive aspect) and (2) its enactment (the performative aspect) as the two mutually constitutive aspects of organizational routines; and (3) the role of artifacts as mediators of the relationship between actors and the ostensive and performative aspects of organizational routines - to develop theoretical arguments explaining the benefits of applying this ontology to the ISD phenomenon. Extending the contextual boundaries of Feldman and Pentland's ontology, we propose research avenues that have the potential to contribute to our understanding of this core phenomenon of the IS discipline. Collapse

Topics: knowledge representation software process improvement affordance extreme programming organizational culture

Methods: ontological modelling design methodology case study

Theories: complex adaptive system co-evolution theory

How agile software development methods reduce work exhaustion: Insights on role perceptions and organizational skills

2020 | Information Systems Journal | Citations: 62

Authors: Venkatesh, Viswanath; Thong, James Y. L.; Chan, Frank K. Y.; Hoehle, Hartmut; Spohrer, Kai

Abstract: Agile methods are widely used in the software industry as a way to more rapidly ... Expand

Abstract: Agile methods are widely used in the software industry as a way to more rapidly develop and deliver new software. They define iterative work processes, advocate self-organization and openness for change, and prescribe how software developers interact with each other and external stakeholders. Despite their popularity, it is unclear how agile methods influence work exhaustion in software developers and how developer skills play into this effect. On the one hand, agile methods may reduce software developers' work exhaustion by levelling out their workload across the entire duration of a project. On the other hand, agile methods exert a high level of pressure on software developers to continuously deliver working software, create many intensive social interactions, and to frequently adapt to changes. In light of these effects, prior research could not explain why some software developers become less exhausted from using agile methods, whereas others perceive the exact opposite. Based on the job demand-control model, we develop a theoretical model connecting agile method use to individual developer skills and to two established determinants of employee exhaustion: role conflict and role ambiguity. We tested our research model in a field study among 1894 software developers in 217 project teams that used agile methods. The random coefficient modelling results show that agile method use facilitates the achievement of clear and unambiguous role perceptions and thereby reduces work exhaustion in developers, particularly if developers possess the organizational skills to effectively interact with others in their organization. We highlight implications for theory on the individual-level effects of software development methods and provide practical insights for software companies. Collapse

Topics: agile software development software developer system development method systems development project productivity

Methods: design methodology field study theory development mediation analysis instrumental variables estimation

Agile Development in Practice: Lessons from the Trenches

2019 | Information Systems Management | Citations: 9

Authors: Cram, W. Alec

Abstract: In the twenty years since the agile approach to systems development was introduc ... Expand

Abstract: In the twenty years since the agile approach to systems development was introduced, a wide range of organizations have adopted its principles. Despite numerous reports that highlight agile success stories, there are relatively few recent publications that provide practical guidance on the potential pitfalls and areas of risk related to agile. In response, this practice-oriented paper draws on 56 practitioner interviews to identify a series of “lessons learned” pertaining to agile adoption, tailoring, and use. Collapse

Topics: agile software development organizational culture system development method information system use problem solving

Methods: design methodology qualitative interview

Theories: work systems theory

Journey towards agility

2019 | HICSS | Citations: 0

Authors: Dreesen, Tim; Binzer, Björn; Diegmann, Phil; Rosenkranz, Christoph

Abstract: After more than 15 years since the Agile Manifesto and extensive research on agi ... Expand

Abstract: After more than 15 years since the Agile Manifesto and extensive research on agile software development (ASD) for nearly three decades, a comprehensive body of knowledge is available and is constantly growing. ASD is considered an effective way for managing software development projects in environments characterized by rapidly changing requirements. This study aims to shed light on the existing knowledge on ASD by applying a structured literature review and computer aided analysis consisting of distinct text mining techniques. We analyzed a sample of 1,376 papers and provide results from articles among relevant information systems research as well as computer science conferences and journals. Based on our approach, we are able to (1) evaluate key articles and journals, (2) analyze the development of ASD research in the last three decades and, most importantly, (3) identify research foci of the past as well as gaps in our knowledge on ASD. Collapse

Topics: agile software development information technology capability requirements analysis pair programming problem solving

Methods: topic model design methodology literature study literature sample structured literature research

Successful Mobile Application Development: Towards a Taxonomy of Domain-Specific Process Models and Methodologies

2019 | HICSS | Citations: 0

Authors: Werth, Oliver; Guhr, Nadine; Breitner, Michael H

Abstract: Mobile applications and mobile application development issues receive an increas ... Expand

Abstract: Mobile applications and mobile application development issues receive an increasing attention for practitioners and academics. The development of mobile applications is connected with a number of domain-specific issues and challenges (e.g., fulfilment of customer requirements or the prevention of high development costs). Consequently, the decision of the most effective process model to develop a mobile application plays a crucial role for software and mobile application development teams. With the help of a structured taxonomy-building methodology, we contribute to the extant literature by creating and presenting a taxonomy for process models and methodologies in software engineering and the mobile application development domain. The taxonomy enrich the existing knowledge base and can help mobile application developers to choose the most suitable process model or methodology. Based on our examination, our results indicate new directions for mobile application research and implications for mobile application development. Collapse

Topics: systems development mobile application system development method user requirement knowledge base

Methods: business process modeling design methodology design artifact design science theoretical contribution

Have your cake and eat it too? Simultaneously pursuing the knowledge-sharing benefits of agile and traditional development approaches

2018 | Information & Management | Citations: 0

Authors: Cram, W. Alec; Marabelli, Marco

Abstract: This research examines how organizations manage knowledge-sharing processes in s ... Expand

Abstract: This research examines how organizations manage knowledge-sharing processes in systems development projects that employ both agile and traditional development techniques. Using a longitudinal case study, we draw on one company’s experience with a system implementation that employed a traditional approach during its first phase and then a hybrid, agile-traditional approach in its second phase. By applying an ambidexterity theory lens, we find that the adoption of a hybrid approach allowed the project to continue to exploit the traditional techniques that were working well, abandon techniques that were underperforming, and explore the use of agile techniques in selected areas. Collapse

Topics: knowledge sharing agile software development Scrum systems development knowledge management system

Methods: qualitative interview design methodology theoretical contribution longitudinal research company material

Theories: ambidexterity theory

Journey Towards Agility: Three Decades of Research on Agile Information Systems Development

2018 | International Conference on Information Systems | Citations: 6

Authors: Diegmann, Phil; Dreesen, Tim

Abstract: After more than 15 years since the Agile Manifesto and extensive research on agi ... Expand

Abstract: After more than 15 years since the Agile Manifesto and extensive research on agile information systems development for nearly three decades, a comprehensive body of knowledge is available and is constantly growing. Agile information systems development is considered an effective way for managing information systems development projects in environments characterized by rapidly changing requirements. This study aims to shed light on the existing knowledge on agile information systems development by applying a structured literature review and computer aided analysis consisting of distinct text mining techniques. We analyzed a sample of 775 papers and provide results from articles among the Senior Scholars’ Basket, selected information systems conferences, and selected journals from management and computer science. Based on our approach, we are able to (1) evaluate key articles and journals, (2) analyze the development of agile information systems development research in the last three decades and, most importantly, (3) identify research foci of the past as well as gaps in our knowledge on agile information systems development for further research. Collapse

Topics: agile software development pair programming requirements analysis extreme programming problem solving

Methods: design methodology topic model literature study literature sample structured literature research

Scaling for agility: A reference model for hybrid traditional-agile software development methodologies

2018 | Information Systems Frontiers | Citations: 0

Authors: Gill, Asif Qumer; Henderson-Sellers, Brian; Niazi, Mahmood

Abstract: The adoption of agility at a large scale often requires the integration of agile ... Expand

Abstract: The adoption of agility at a large scale often requires the integration of agile and non-agile development elements for architecting a hybrid adaptive methodology. The challenge is ”which elements or components (agile or non-agile) are relevant to develop the context-aware hybrid adaptive methodology reference architecture?” This paper addresses this important challenge and develops a hybrid adaptive methodology reference architecture model using a qualitative constructive empirical research approach. In this way, we have uncovered the agility, abstraction, business value, business policy, rules, legal, context and facility elements or components that have not been explicitly modelled or discussed in International Standards (IS) such as the ISO/IEC 24744 metamodel. It is anticipated that a context-aware hybrid adaptive methodology can be architected by using the proposed context-aware hybrid adaptive methodology reference architecture elements for a particular situation when using a situational method engineering approach. Collapse

Topics: agile software development organizational value Scrum electronic health IT project

Methods: case study design methodology literature study cross sectional research business process modeling

Agile Methods as a Risk Management Strategy Tool–A FinTech Case Study

2018 | Americas Conference on Information Systems | Citations: 0

Authors: Zaitsev, Anna

Abstract: FinTech companies are subjected to same regulations than traditional financial o ... Expand

Abstract: FinTech companies are subjected to same regulations than traditional financial organisations but due to their novelty, these organisations can experiment with unorthodox ways to strategically manage software development risk and ensure compliance with the regulations of the financial industry. Our case study presents an example of an Australian FinTech organisation, which has successfully applied Extreme Programming method as their company-wide risk management strategy tool. The Agile methods application encompasses the different layers of risk management; method, people and process. This study discusses how Agile development method practices are utilised to respond to risks and to ensure compliance. The case organisation is shown to address both the regulatory requirements as well as fulfil the bases for risk management approach and tailoring frameworks proposed in the literature. Finally, we present a theory of strategic risk management via Agile methods. This theory illustrates how method application influences other aspects of strategic risk management. Collapse

Topics: agile software development electronic finance risk management system development method strategic management

Methods: design methodology case study qualitative interview qualitative coding single case study