Agile, Web Engineering and Capability Maturity ModelI ntegration : A systematic literature review

Context Agile approaches are an alternative for organizations developing software, particularly for those who develop Web applications. Besides, CMMI (Capability Maturity Model Integration) models are well-established approaches focused on assessing the maturity of an organization that develops software. Web Engineering is the field of Software Engineering responsible for analyzing and studying the specific characteristics of the Web. The suitability of an Agile approach to help organizations reach a certain CMMI maturity level in Web environments will be very interesting, as they will be able to keep the ability to quickly react and adapt to changes as long as their development processes get mature. Objective This paper responds to whether it is feasible or not, for an organization developing Web systems, to achieve a certain maturity level of the CMMI-DEV model using Agile methods. Method The proposal is analyzed by means of a systematic literature review of the relevant approaches in the field, defining a characterization schema in order to compare them to introduce the current state-of-the-art. Results The results achieved after the systematic literature review are presented, analyzed and compared against the defined schema, extracting relevant conclusions for the different dimensions of the problem: compatibility, compliance, experience, maturity and Web. Conclusion It is concluded that although the definition of an Agile approach to meet the different CMMI maturity levels goals could be possible for an organization developing Web systems, there is still a lack of detailed studies and analysis on the field

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

Leadership in Agile Software Development: A Systematic Literature Review

Effective leadership is deemed essential for successful projects and teams. However, leadership in agile software development projects and teams is a challenge in practice, and the research literature provides no general agreement on what constitutes effective leadership in this environment. To address this issue and give the agile community a comprehensive overview of the research on agile leadership we report the results of a systematic literature review (SLR). The SLR identified 33 studies in the Scopus database published from 2000-2019 that contribute to agile leadership knowledge. The results indicate that whilst some studies apply leadership theories to explore and explain the role of agile leadership other studies propose alternative approaches to leadership within agile software teams and projects. The results suggest that agile leadership research needs further attention and that more empirical studies are needed to better understand agile leadership in general and in the various agile information systems development environments

PLOMO Associate Team Final Report

The goal of Plomo is to develop new meta tools to improve and bring synergy in the existing infrastructure of Pharo1 (for software development) and the Moose software analysis platform2 (for maintenance). PLOMO will (i) enhance the Opal open compiler infrastructure to support plugin definition, (ii) offer an infrastructure for change and event tracking as well as models to compose and manipulate them, (iii) work on a layered library of algorithms for the Mondrian visualization engine of Moose, (iv) work on new ways of profiling applications. All the efforts will be performed on Pharo and Moose, two platforms heavily used by the RMoD and Pleiad teams

From Offshore Operation to Onshore Simulator: Using Visualized Ethnographic Outcomes to Work with Systems Developers

This paper focuses on the process of translating insights from a Computer Supported Cooperative Work (CSCW)-based study, conducted on a vessel at sea, into a model that can assist systems developers working with simulators, which are used by vessel operators for training purposes on land. That is, the empirical study at sea brought about rich insights into cooperation, which is important for systems developers to know about and consider in their designs. In the paper, we establish a model that primarily consists of a ‘computational artifact’. The model is designed to support researchers working with systems developers. Drawing on marine examples, we focus on the translation process and investigate how the model serves to visualize work activities; how it addresses relations between technical and computational artifacts, as well as between functions in technical systems and functionalities in cooperative systems. In turn, we link design back to fieldwork studies

Facilitating Requirements Negotiation: Modelling Alternatives and Arguments

Co-development aims to ensure the alignment of business processes and support technical systems. During co-development stakeholders need an early understanding of the potential impact of different requirement choices on the enterprise. An early impact analysis understanding is more likely to actively engage stakeholders, highlight strategic options and deliver useful and sustainable systems. However, when multiple stakeholders are involved with differing backgrounds, experiences and frequently competing goals it is inevitable that conflicts occur during the early phases when requirements tend to be opaque. This paper puts forward a conceptual framework for co-development to support collaborative reasoning and decision-making through the modelling of requirements alternatives and arguments, promoting critical reflection, negotiation and discussion

Facilitating Requirements Negotiating: Modeling Alternatives and Arguments

Co-development aims to ensure the alignment of business processes and support technical systems. During co-development stakeholders need an early understanding of the potential impact of different requirement choices on the enterprise. An early impact analysis understanding is more likely to actively engage stakeholders, highlight strategic options and deliver useful and sustainable systems. However, when multiple stakeholders are involved with differing backgrounds, experiences and frequently competing goals it is inevitable that conflicts occur during the early phases when requirements tend to be opaque. This paper puts forward a conceptual framework for co-development to support collaborative reasoning and decision-making through the modelling of requirements alternatives and arguments, promoting critical reflection, negotiation and discussion

Report on the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3)

This report records and discusses the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3). The report includes a description of the keynote presentation of the workshop, which served as an overview of sustainable scientific software. It also summarizes a set of lightning talks in which speakers highlighted to-the-point lessons and challenges pertaining to sustaining scientific software. The final and main contribution of the report is a summary of the discussions, future steps, and future organization for a set of self-organized working groups on topics including developing pathways to funding scientific software; constructing useful common metrics for crediting software stakeholders; identifying principles for sustainable software engineering design; reaching out to research software organizations around the world; and building communities for software sustainability. For each group, we include a point of contact and a landing page that can be used by those who want to join that group's future activities. The main challenge left by the workshop is to see if the groups will execute these activities that they have scheduled, and how the WSSSPE community can encourage this to happen