Agile Software Development in Practice

Author(s):  
Matti Rossi ◽  
Hilkka Merisalo-Rantanen ◽  
Tuure Tuunanen

This chapter explores agile information practices of information systems development and argues that their history is much longer than what is generally believed today. We take an interpretive and critical view of the phenomenon. We made an empirical study of two companies that apply an XP-style development approach throughout the information systems development life cycle. The results of our research suggest that XP is a combination of best practices of traditional information systems development methods. It is hindered by its reliance on talented individuals, which makes its large-scale deployment as a general-purpose method difficult. We claim that XP can be useful for small colocated teams of skilled domain experts and implementers who are able to communicate well with the end users. However, these skilled and motivated individuals with high working morale can exhibit high productivity regardless of the methods used if they are not overly constrained by bureaucracy.

Author(s):  
E. Berki ◽  
K. Siakas ◽  
E. Georgiadou

This chapter provides a basis for discussion and analysis of the quality characteristics of the agile information systems development (AISD) process, and exposes concerns raised regarding the applicability and suitability of agile methods in different organisational and national cultures. The arguments are derived from recent literature reviews and reports on the state-of-the-art in agile methodologies. We also reflect on our own research and experience in three European countries with different academic and work values, and information systems development (ISD) industrial practices based on diverse principles. Examining the different perceptions of quality in the agile software development paradigm by comparing and contrasting them to the quality perceptions in the established ISD methodological paradigms, we aim at: (i) exploring the relationship of traditional, agile, managed, and measured ISD processes, (ii) making the human dynamics that bear on the success and consensus acceptance of IS more explicit, and (iii) establishing a critical framework/approach for reflecting on the suitability and applicability of agile methods in the development and management of quality software systems.


Author(s):  
G. Harindranath ◽  
John A. A. Sillince

This is a case study of a US$ 30 million project to establish a new form of rapid healthcare service delivery within the context of a highly politicised National Health Service Hospital (NHS) Trust in the United Kingdom (UK). This project involved large-scale redesign of long-established healthcare procedures and the development of sophisticated new information systems (IS) through a unique partnership between the public sector (the UKs NHS) and a number of private sector companies (a software developer, a facilities manager, a hardware vendor and a builder). The case study concentrates on, what is often, one of the more important determinants of the success or failure of such partnerships involved in information systems development, i.e. risk.


Author(s):  
Iris Reinhartz-Berger

Method Engineering (ME) and Situational Method Engineering (SME) aim at providing effective solutions for building and supporting evolution of software and information systems development methods. For this purpose, method components are specified and composed into general-purpose development methods or situational methods, i.e., development methods that best fit the characteristics of a given project and its environment. Recently ISO/IEC 24744 has emerged for defining a metamodel and a notation for development methods. However, this standard lacks a systematic support for situational classification and maintenance. In this work, the authors suggest incorporating ISO/IEC 24744 metamodel into a domain-based framework, called Application-based DOmain Modeling for Method Engineering (ADOM-ME), which supports specifying both general-purpose and situational methods in a single, simple, accessible, and scalable frame of reference. An exploratory study on the usability of ADOM-ME indicates that the approach can be utilized by information systems students that represent non-experienced method engineers and software developers.


Sign in / Sign up

Export Citation Format

Share Document