Call for papers pdf

As strategic and operating conditions become increasingly turbulent due to factors such as hyper-competition, regulatory changes from market and customers, and technological advancements, the ability to sense relevant change and respond appropriately becomes an important determinant of enterprise success. Enterprise systems play an important role in enabling such agility of enterprise business. An enterprise system provides a technical platform that enables organisations to run their business more effectively. Modern enterprise systems are usually an integration of information systems of many departments which are running in variable environment and contexts. Both the development and the evolution of an enterprise system require a lightweight approach to interoperability and the capability to actively react to changing requirements and failures. It is natural to relate such requirement of a lightweight approach to Agile Manifesto and agile software development, which are the reflection of agility on software development. In general, agility is a concept that incorporates the ideas of flexibility, balance, adaptability, and coordination under one umbrella. The agility of an enterprise system typically refers to the ability of an organization and the information system supporting its business processes to rapidly adapt to market and environmental changes in productive and cost-effective ways.

The AgilES workshop aims to be a major presentation and networking opportunity for researchers and practitioners so that they can exchange the results of rigorous scientific research, experience of industrial practices, or novel ideas on enterprise systems, especially about modelling, measuring, and enhancing agility of enterprise systems. To achieve this objective, we invite contributions critically reflecting on the current status of research and practice in enterprise systems on following topics, but not limited.


Types of contributions

We invite four types of original and scientific papers:
  • Research and/or technical papers, which describe original solutions (theoretical, methodological or conceptual) in the field of enterprise systems. A technical paper should clearly describe the situation or research problem, the relevant state of the art, the position or solution suggested and the potential or, even better, the evaluated benefits of the contribution.
  • Empirical evaluation papers, which evaluate existing problem situations or validate proposed solutions with scientific means, i.e. by empirical studies, experiments, case studies, etc. Scientific reflection on problems and practices in industry also falls into this category. The topic of the evaluation presented in the paper as well as its causal or logical properties must be clearly stated. The research method should be sound and appropriate.
  • Experience papers, which present problems or challenges encountered in practice, relate success and failure stories, or report on industrial practice. The focus is about "what" and on lessons learned, not on an in-depth analysis of "why". The practice must be clearly described and its context must be given. Readers should be able to draw conclusions for their own practice.
  • Exploratory Papers, which can describe completely new research positions or approaches, in order to face to a generic situation arising because of new techniques, environments, or challenges, such as cloud computing. They must describe precisely the situation and demonstrate how current methods, or tools are inadequate. They must rigorously present their approach and demonstrate its pertinence and correctness to addressing the identified situation.

Papers should be submitted in PDF format. The results described must be unpublished and must not be under review elsewhere.
  • Regular papers must not exceed 12 pages in this format, including all text, references, appendices, and figures.
  • Short papers are limited to 6 pages.
  • Extended abstract/position paper, 2 pages
  • Submissions must conform to Springer's LNBIP formatting rules. Further authoring instructions are available at here. Three to five keywords characterizing the paper should be indicated at the end of the abstract. It is expected that at least one author of each accepted paper will register for and attend the workshop.