Search

Prior work on leadership in information systems development (ISD) teams has assumed that all developers are treated equally by their team leader and ignored the possibility that differentiated leader-member exchange (LMX) may be an important instrument for team leaders to influence self-organizing, agile ISD teams. We conducted a concurrent mixed methods inquiry to understand how LMX differentiation is associated with developer satisfaction in agile ISD teams and through which team processes agile ISD teams address LMX differentiation. We ran a multilevel, multistage survey of 1,894 software developers in 217 teams and an embedded case study of five ISD teams drawing on qualitative data from 40 interviews of developers and team leaders. Two focus groups (one with 10 developers and one with 10 team leaders) helped to substantiate the meta-inferences from the quantitative and qualitative studies. The results showed that LMX differentiation was positively associated with developer satisfaction, especially in teams with high-quality team-member exchange (TMX). We identify three team processes (i.e., collectivization of resources, visible appreciation of privileges, and freeing up leader capacities) that are enacted through agile ISD practices and allow ISD teams to leverage benefits from LMX differentiation for all their members. [ABSTRACT FROM AUTHOR]

Nowadays modern information systems (emerging technologies) are increasingly becoming an integral part of our daily lives and has begun to pose a serious challenge for human-computer interaction (HCI) professionals, as emerging technologies in the area of mobile and cloud computing, and internet of things (IoT), are calling for more devotion from HCI experts in terms of systems interface design. As the number of mobile platforms users, nowadays comprises of children's, elderly people, and people with disabilities or disorders, all demanding for an effective user interface that can meet their diverse needs, even on the move, at anytime and anywhere. This paper, review current articles (43) related to HCI interface design approaches to modern information systems design with the aim of identifying and determining the effectiveness of these methods. The study found that the current HCI design approaches were based on desktop paradigm which falls short of providing location-based services to mobile platforms users. The study also discovered that almost all the current interface design standard used by HCI experts for the design of user's interface were not effective & supportive of emerging technologies due to the flexibility nature of these technologies. Based on the review findings, the study suggested the combination of Human-centred design with agile methodologies for interface design, and call on future works to use qualitative or quantitative approach to further investigate HCI methods of interface design with much emphasis on cloud-based technologies and other organizational information systems. [ABSTRACT FROM AUTHOR]

The integration of user-centered design (UCD) activities into agile information systems development has become more popular recently. Despite the fact that there are many ways the merging of UCD activities into agile development can be carried out, it has been widely recognized that coordinating design activities with development activities is one of the most common problems, especially in distributed environments where designers, developers and users are spread over several sites. The main approach to coordinate UCD activities with distributed agile development is the use of informal methods (e.g. communication through using video conference tools). In addition to the temporal, geographical and socio-cultural barriers associated with this type of methods, a major limitation is a lack of awareness of how UCD activities and development activities affect each other. Furthermore, some agile project management tools are integrated with design platforms but fail to provide the necessary coordination that helps team members understand how the design and development activities affect their daily work. This research aims to support the effective management of integrating UCD activities into distributed agile development by (i) identifying the key activity dependencies between UX design teams and development teams during distributed UCD/agile development and (ii) designing a computer-based system to provide coordination support through managing these activity dependencies. In order to achieve these objectives, two case studies are carried out. Our findings revealed 10 main dependencies between UCD design teams and development teams as shown by six types of activity. In addition, the participatory design approach shows that developing a computer-based system to manage seven of these selected dependencies is achievable. [ABSTRACT FROM AUTHOR]

This article provides insights into the current state of developmental testing (DT) and requirements management in Department of Defense information systems employing Agile development. The authors describe the study methodology and provide an overview of Agile development and testing. Insights are described for requirements, detailed planning, test execution, and reporting. This work articulates best practices related to DT and requirements management strategies for programs employing modernized Software Development Life Cycle practices. [ABSTRACT FROM AUTHOR]

The adoption of Agile Software Development in large companies is a recent phenomenon of great interest both for researchers and practitioners. Although intra-team interaction is well supported by established agile practices, the critical interaction between the agile team and other parts of the organization is still unexplored in literature. Such interactions slow down the development, hindering the achievement of business goals based on speed: short time to market, quick replication of products of a product-line, and reaction time for product evolution. We have employed a two-year long multiple-case case-study, collecting data through interviews and a survey in three large companies developing embedded software. Through a combination of qualitative and quantitative analysis, we have found strong evidence that interaction challenges between the development team and other groups in the organization hinder speed and are widespread in the organizations. This paper also identifies current practices in use at the studied companies and provides detailed guidelines for novel solutions in the investigated domain. Such practices are called boundary-spanning activities in information system research and coordination theory. We present a comparison between large embedded software companies employing agile and developing a line of products based on reused assets and agile companies developing pure software. We highlight specific contextual factors and areas where novel spanning activities are needed for mitigating the interaction challenges hindering speed. Copyright © 2015 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

The global Business Intelligence (BI) market grew by 10% in 2013 according to the Gartner Report. Today organizations require better use of data and analytics to support their business decisions. Internet power and business trend changes have provided a broad term for data analytics -- Big Data. To be able to handle it and leverage a value of having access to Big Data, organizations have no other choice than to get proper systems implemented and working. However traditional methods are not efficient for changing business needs. The long time between project start and go-live causes a gap between initial solution blueprint and actual user requirements in the end of the project. This article presents the latest market trends in BI systems implementation by comparing Agile with traditional methods. It presents a case study provided in a large telecommunications company (20K employees) and the results of a pilot research provided in the three large companies: telecommunications, digital, and insurance. Both studies prove that Agile methods might be more effective in BI projects from an end-user perspective and give first results and added value in a much shorter time compared to a traditional approach. [ABSTRACT FROM AUTHOR]

Several approaches that could be implemented on any platform via any methodology would greatly increase the odds of the successful deployment of a working information system. [ABSTRACT FROM PUBLISHER]

The specification for an information system can be clear from the beginning: it must acquire, display, query and modify data, using a database. The main issue is to decide which information to manage. In the case originating this work, information was always evolving, even up to the end of the project. This implies the construction of a new system each time the information is redefined. This article presents Genesis, an agile development infrastructure, and proposes an approach for the immediate construction of required information systems. Experts describe their information needs and queries, and genesis generates the corresponding application, with the appropriate graphical interfaces and database. [ABSTRACT FROM AUTHOR]