Agile methods in biomedical software development: a multi-site experience report

BACKGROUND: Agile is an iterative approach to software development that relies on strong collaboration and automation to keep pace with dynamic environments. We have successfully used agile development approaches to create and maintain biomedical software, including software for bioinformatics. This paper reports on a qualitative study of our experiences using these methods. RESULTS: We have found that agile methods are well suited to the exploratory and iterative nature of scientific inquiry. They provide a robust framework for reproducing scientific results and for developing clinical support systems. The agile development approach also provides a model for collaboration between software engineers and researchers. We present our experience using agile methodologies in projects at six different biomedical software development organizations. The organizations include academic, commercial and government development teams, and included both bioinformatics and clinical support applications. We found that agile practices were a match for the needs of our biomedical projects and contributed to the success of our organizations. CONCLUSION: We found that the agile development approach was a good fit for our organizations, and that these practices should be applicable and valuable to other biomedical software development efforts. Although we found differences in how agile methods were used, we were also able to identify a set of core practices that were common to all of the groups, and that could be a focus for others seeking to adopt these methods

Public Bikesharing in North America During a Period of Rapid Expansion: Understanding Business Models, Industry Trends & User Impacts, MTI Report 12-29

Public bikesharing—the shared use of a bicycle fleet—is an innovative transportation strategy that has recently emerged in major cities around the world, including North America. Information technology (IT)-based bikesharing systems typically position bicycles throughout an urban environment, among a network of docking stations, for immediate access. Trips can be one-way, round-trip, or both, depending on the operator. Bikesharing can serve as a first-and-last mile connector to other modes, as well as for both short and long distance destinations. In 2012, 22 IT-based public bikesharing systems were operating in the United States, with a total of 884,442 users and 7,549 bicycles. Four IT-based programs in Canada had a total of 197,419 users and 6,115 bicycles. Two IT-based programs in Mexico had a total of 71,611 users and 3,680 bicycles. (Membership numbers reflect the total number of short- and long-term users.) This study evaluates public bikesharing in North America, reviewing the change in travel behavior exhibited by members of different programs in the context of their business models and operational environment. This Phase II research builds on data collected during our Phase I research conducted in 2012. During the 2012 research (Phase I), researchers conducted 14 expert interviews with industry experts and public officials in the United States and Canada, as well as 19 interviews with the manager and/or key staff of IT-based bikesharing organizations. For more information on the Phase I research, please see the Shaheen et al., 2012 report Public Bikesharing in North America: Early Operator and User Understanding. For this Phase II study, an additional 23 interviews were conducted with IT-based bikesharing organizations in the United States, Canada, and Mexico in Spring 2013. Notable developments during this period include the ongoing expansion of public bikesharing in North America, including the recent launches of multiple large bikesharing programs in the United States (i.e., Citi Bike in New York City, Divvy in Chicago, and Bay Area Bike Share in the San Francisco Bay Area). In addition to expert interviews, the authors conducted two kinds of surveys with bikesharing users. One was the online member survey. This survey was sent to all people for whom the operator had an email address.The population of this survey was mainly annual members of the bikesharing system, and the members took the survey via a URL link sent to them from the operator. The second survey was an on-street survey. This survey was designed for anyone, including casual users (i.e., those who are not members of the system and use it on a short-term basis), to take “on-street” via a smartphone. The member survey was deployed in five cities: Montreal, Toronto, Salt Lake City, Minneapolis-Saint Paul, and Mexico City. The on-street survey was implemented in three cities: Boston, Salt Lake City, and San Antonio

A state of the art review on software project performance management

Several domain experts in the field of software development and project management have commented on the high failure rate of software engineering and project management. A lot of money has been wasted on failed software projects. Additionally, software quality is not improving. Thusthe successful management of software projects is critical. It is vital to understand what is important to complete software project on time within budget, and meet user requirements. Many literatures present project failure causes. However, project failure still persists. In this paper we outline softwaredevelopment failure. Then we present two key variables in software project performance management i.e. trust and knowledge sharing

Development of a Wireless Environmental Data Acquisition Prototype Adopting Agile Practices: An Experience Report

The traditional software development model commonly named “waterfall” is unable to cope with the increasing functionality and complexity of modern embedded systems. In addition, it is unable to support the ability for businesses to quickly respond to new market opportunities due to changing requirements. As a response, the software development community developed the Agile Methodologies (e.g., extreme Programming, Scrum) which were also adopted by the Embedded System community. However, failures and bad experiences in applying Agile Methodologies to the development of embedded systems have not been reported in the literature. Therefore, this paper contributes a detailed account of our first-time experiences adopting an agile approach in the prototype development of a wireless environment data acquisition system in an academic environment. We successfully applied a subset of the extreme Programming (XP) methodology to our software development using the Python programming language, an experience that demonstrated its benefits in shaping the design of the software and also increasing productivity. We used an incremental development approach for the hardware components and adopted a “cumulative testing” approach. For the overall development process management, however, we concluded that the Promise/Commitment-Based Project Management (PBPM/ CBPM) was better suited. We discovered that software and hardware components of embedded systems are best developed in parallel or near-parallel. We learned that software components that pass automated tests may not survive in the tests against the hardware. Throughout this rapid prototyping effort, factors like team size and our availability as graduate students were major obstacles to fully apply the XP methodology

Agile User Experience Design: A Design Science Enquiry

This paper presents a qualitative analysis of an information systems design study within the context of agile software development based on conceptually different two design approaches: Current Agile Process (CAP) and Enhanced Agile Process (EAP). Eight agile software professionals and one user experience designer were recruited from the industry to form two small agile teams, where one agile software professional shared the product owner role in both teams. Each team undertook agile software product development based on exclusively one of the two conceptually different design approaches, CAP and EAP. Both teams used the same suite of user stories presented by the product owner. The progress of product development was assessed using four evaluation approaches: observation data comparison, debrief data comparison, individual system evaluation and comparative system evaluation. This paper presents the results of observation data comparison only. The results suggest that agile software development team that followed the enhanced agile process had more user experience focus in the design and the outcome of the product delivery proved to be somewhat richer in user experience. The paper also explores the research design, research process, developer perceptions as well as areas of shortcomings where further understanding and modelling effort is needed