The COVID-19 pandemic has accelerated remote working and working at the office. This hybrid working is an indispensable part of today's life even within Agile Software Development (ASD) teams. Before COVID-19 ASD teams were working closely together in an Agile way at the office. The Agile Manifesto describes 12 principles to make agile working successful. These principles are about working closely together, face-to-face contact and continuously responding to changes. To what extent does hybrid working influence these agile principles that have been indispensable in today's software development since its creation in 2001? Based on a quantitative study within 22 Dutch financial institutions and 106 respondents, the relationship between hybrid working and ASD is investigated. The results of this research show that human factors, such as team spirit, feeling responsible and the ability to learn from each other, are the most decisive for the success of ASD. In addition, the research shows that hybrid working creates a distance between the business organization and the IT department. The findings are valuable for Managers, HR professionals and employees working in the field of ASD as emphasizing and fostering Team Spirit, Learning Ability, and a Sense of Responsibility among team members can bolster the Speed of ASD.
MULTIFILE
Agile software development has evolved into an increasingly mature software development approach and has been applied successfully in many software vendors’ development departments. In this position paper, we address the broader agile service development. Based on method engineering principles we define a framework that conceptualizes an operational way of working for the development of services, emphatically taking into account agility. As a first level of agility, the framework contains situational project factors that influence the choice of method fragments; secondly, increased agility is proposed by describing and operationalizing these method fragments not as imperative steps or activities, but instead by means of sets of minimally specified, declarative rules that determine the context and constraints within which goals are to be reached. This approach borrows concepts from rules management, organizational patterns, and game design theory. Keywordsmethod engineering–agile service development–business rules–business rules management–product management–game design
DOCUMENT
Although many pilots with new eHealth products have been developed, only very few of these products reach widespread adoption within healthcare organisations. The literature mentions a wide range of bottlenecks for the acceptance of new technology in the healthcare industry, among which insufficient attention for change management and acceptance by intended users. In this paper, we argue that agile software development, with its practices for user involvement and product visibility, can be used as a change management approach in healthcare innovation projects. We compare agile methods with the change approach of Kotter (1995). As an illustration of our theoretical findings, we describe a development project of an innovative eHealth application to support the care for persons with intellectual disability.
DOCUMENT
Sustainable and Agile manufacturing is expected of future generation manufacturing systems. The goal is to create scalable, reconfigurable and adaptable manufacturing systems which are able to produce a range of products without new investments into new manufacturing equipment. This requires a new approach with a combination of high performance software and intelligent systems. Other case studies have used hybrid and intelligent systems in software before. However, they were mainly used to improve the logistic processes and are not commonly used within the hardware control loop. This paper introduces a case study on flexible and hybrid software architecture, which uses prototype manufacturing machines called equiplets. These systems should be applicable for the industry and are able to dynamically adapt to changes in the product as well as changes in the manufacturing systems. This is done by creating self-configurable machines which use intelligent control software, based on agent technology and computer vision. The requirements and resulting technologies are discussed using simple reasoning and analysis, leading to a basic design of a software control system, which is based on a hybrid distributed control system
DOCUMENT
This paper describes an agent-based software infrastructure for agile industrial production. This production is done on special devices called equiplets. A grid of these equiplets connected by a fast network is capable of producing a variety of different products in parallel. The multi-agent-based underlying systems uses two kinds of agents: an agent representing the product and an agent representing the equiplet.
MULTIFILE
Past research on designing for behavioural change mostly concerned linear design processes, whereas in practice, Agile design methods are increasingly popular. This paper evaluates the possibilities and limitations of using Agile design methods in theory-driven design for behavioural change. We performed a design case study, consisting of a student design team working on improving waiting experiences at Schiphol Airport security and check-in. Our study showed that Agile design methods are usable when designing for behavioural change. Moreover, the Behavioural Lenses toolkit used in the design process is beneficial in facilitating theory-driven Agile design. The combination of an Agile design process and tools to evidentially inform the design enabled the design team to formulate viable and interesting concepts for improving waiting-line experiences. However, limitations also occurred: a mismatch between the rate at which the Scream method proceeded and the time and momentum needed to conduct in-depth research.
MULTIFILE
From the article: The ethics guidelines put forward by the AI High Level Expert Group (AI-HLEG) present a list of seven key requirements that Human-centered, trustworthy AI systems should meet. These guidelines are useful for the evaluation of AI systems, but can be complemented by applied methods and tools for the development of trustworthy AI systems in practice. In this position paper we propose a framework for translating the AI-HLEG ethics guidelines into the specific context within which an AI system operates. This approach aligns well with a set of Agile principles commonly employed in software engineering. http://ceur-ws.org/Vol-2659/
DOCUMENT
Both Software Engineering and Machine Learning have become recognized disciplines. In this article I analyse the combination of the two: engineering of machine learning applications. I believe the systematic way of working for machine learning applications is at certain points different from traditional (rule-based) software engineering. The question I set out to investigate is “How does software engineering change when we develop machine learning applications”?. This question is not an easy to answer and turns out to be a rather new, with few publications. This article collects what I have found until now.
LINK
Due to the changing technological possibilities of services, the demands that society places on the level of service provided by the Dutch Central Government (DCG) are changing rapidly. To accommodate this, the Dutch government is improving its processes in such a way that they become more agile and are continuously improved. However, the DCG struggles with the implementation of improvement tools that can support this. The research described in this paper aims to deliver key factors that influence the adoption of tools that improve the agile way of working and continuous improvement at the DCG. Therefore, a literature review has been conducted, from which 24 factors have been derived. Subsequently, 9 semi structured interviews have been conducted to emphasize the perspective of employees at the DCG. In total, 7 key factors have been derived from the interviews. The interviewees consisted of both employees from departments who already worked with tools to improve agile working and continuous improvement as well as employees from departments who haven’t used such tools yet. An important insight based on this research is that the aims, way of working and scope of the improvement tools must be clear for all the involved co-workers
MULTIFILE
Author supplied: The production system described in this paper in an implementation of an agile agent-based production system. This system is designed to meet the requirements of modern production, where short time to market, requirementdriven production and low cost small quantity production are important issues. The production is done on special devices called equiplets. A grid of these equiplets connected by a fast network is capable of producing a variety of different products in parallel. The multi-agent-based software infrastructure is responsible for the agile manufacturing. A product agent is responsible for the production of a single product and equiplet agents will perform the production steps to assemble the product. This paper describes this multiagent-based production system with the focus on the product agent. Presented at EUMAS 2013 ( 11th European Workshop on Multi-Agent Systems) , At Toulouse.
DOCUMENT
