ABSTRACT Researchers, organizations, and professionals have a great interest in defining sustainability indicators within the framework of Green Business Process Management (Green BPM), together with business process models that allow the impact of those indicators to be assessed in organizations. However, there is a lack of procedures that help organizations to incorporate indicators in Green BPM. For this reason, the so‐called Gaia method has been developed based on the Green BPM lifecycle. This method allows the implementation, monitoring, and continuous improvement of sustainability in business processes based on sustainability indicators. This paper presents an empirical validation of Gaia through a case study carried out in a higher education institution, emphasizing the definition and evaluation of sustainability indicators in business processes. The evaluation of sustainability indicators into the BPM lifecycle allowed sustainability indices to be obtained for each process, leading to the calculation of an organization's sustainability coefficient. The proposal has been applied to a higher education organization, which obtained a sustainability coefficient , corresponding to the medium sustainability level (). The case study has been the basis for the re‐elaboration of objectives, lines of action, and the redesign of business processes that contribute to evaluating and improving the levels of sustainability desired by the organization under study. The main limitation of our study is that the Gaia method has been applied on one organization only. A tool that automates the method to assess the sustainability of business processes is being developed.

Abstract Attention is currently being focused on DevOps, which aims to reduce software development time by means of close collaboration between the development and operations areas. However, little effort has been made to determine the role of requirements management in DevOps. The objective of this study is to help both researchers and practitioners by providing an overview of the best practices regarding requirements engineering in DevOps and identifying which areas still need to be investigated. A multivocal mapping study has, therefore, been carried out in order to study which methodologies, techniques and tools are used to support requirements management in DevOps environments. After applying the review protocol, 37 papers from formal literature and 14 references from grey literature were selected for analysis. The general conclusions obtained after analysing these papers were that, within DevOps, more attention should be paid to: (1) the reuse of requirements in order to identify systems and software artefacts that can serve as a basis for the specification of new projects; (2) the communication of requirements between the different areas of an organisation and the stakeholders of a project; (3) the traceability of requirements in order to identify the relationship with other requirements, artefacts, tasks and processes; (4) non-functional requirements in order to identify the requirements of the operations area in the early phases of a project; and finally (5) specific requirements tools that should be seamlessly integrated into the DevOps toolchain. All these issues must be considered without ignoring the agile and continuous practices of development, operations and business teams. More effort must also be made to validate new methodologies in industry so as to assess and determine their strengths and weaknesses.