A Flipped Learning Agile Methodology for teaching in higher education levels

[EN] This paper presents the results of implementing the Flipped Learning Agile (FLA) methodology as a general framework to manage courses and to encourage proactive learning for students in higher education levels. Flipped Learning is used in combination with Information and Communication Technologies (ICTs) to encourage the student in the self-learning process. It is proposed the integration of an Agile Methodology that includes the use of Scrum and Kanban methodologies, by means of sprints for task scheduling and using a board for activities status, into a Flipped Learning (FL) environment. The proposed FL environment is composed of applications such as YouTube, Google Classroom, and Google Drive. The Scrum methodology was designed for 4 sprints, each one for a week-long. Before applying the FLA methodology, a Motivated Strategies for Learning Questionnaire (MSLQ) was applied in a group of Electrical Circuits students at the University of Guadalajara. To examine the self-regulated learning process, the performance of the students was analysed before applying the FLA methodology; the same MSLQ was carried out after implementing the FLA methodology. The analyses of the last MSLQ show that the implementation of the FLA methodology, by means of the integration of the Agile methodologies of Scrum and Kanban into a flipped learning environment, encourage the self-learning strategy for higher education level students.Águila-León, J.; Vargas Salgado, CA.; Ribó Pérez, DG.; Bastida Molina, P. (2020). A Flipped Learning Agile Methodology for teaching in higher education levels. Editorial Universitat Politècnica de València. 199-207. https://doi.org/10.4995/INN2019.2019.10121OCS19920

Project Success in Agile Development Projects

The paper explains and clarifies the differences between Waterfall and Agile development methodologies, establishes what criteria could be taken into account to properly define project success within the scope of software development projects, and finally tries to clarify if project success is the reason why many organizations are moving to Agile methodologies from other ones such as Waterfall. In the form of a literature review, it analyses several, publications, investigations and case studies that point out the motives why companies moved to Agile, as well as the results they observed afterward. It also analyses overall statistics of project outcomes after companies evolved from traditional methodologies such as Waterfall to Agile development approaches

Iterative criteria-based approach to engineering the requirements of software development methodologies

Software engineering endeavours are typically based on and governed by the requirements of the target software; requirements identification is therefore an integral part of software development methodologies. Similarly, engineering a software development methodology (SDM) involves the identification of the requirements of the target methodology. Methodology engineering approaches pay special attention to this issue; however, they make little use of existing methodologies as sources of insight into methodology requirements. The authors propose an iterative method for eliciting and specifying the requirements of a SDM using existing methodologies as supplementary resources. The method is performed as the analysis phase of a methodology engineering process aimed at the ultimate design and implementation of a target methodology. An initial set of requirements is first identified through analysing the characteristics of the development situation at hand and/or via delineating the general features desirable in the target methodology. These initial requirements are used as evaluation criteria; refined through iterative application to a select set of relevant methodologies. The finalised criteria highlight the qualities that the target methodology is expected to possess, and are therefore used as a basis for de. ning the final set of requirements. In an example, the authors demonstrate how the proposed elicitation process can be used for identifying the requirements of a general object-oriented SDM. Owing to its basis in knowledge gained from existing methodologies and practices, the proposed method can help methodology engineers produce a set of requirements that is not only more complete in span, but also more concrete and rigorous

A Framework for Agile Development of Component-Based Applications

Agile development processes and component-based software architectures are two software engineering approaches that contribute to enable the rapid building and evolution of applications. Nevertheless, few approaches have proposed a framework to combine agile and component-based development, allowing an application to be tested throughout the entire development cycle. To address this problematic, we have built CALICO, a model-based framework that allows applications to be safely developed in an iterative and incremental manner. The CALICO approach relies on the synchronization of a model view, which specifies the application properties, and a runtime view, which contains the application in its execution context. Tests on the application specifications that require values only known at runtime, are automatically integrated by CALICO into the running application, and the captured needed values are reified at execution time to resume the tests and inform the architect of potential problems. Any modification at the model level that does not introduce new errors is automatically propagated to the running system, allowing the safe evolution of the application. In this paper, we illustrate the CALICO development process with a concrete example and provide information on the current implementation of our framework

Harnessing agile concepts for the development of intelligent systems

Traditional and current approaches to intelligent systems design, have led to the creation of sophisticated and computationally-intensive packages and environments, for a wide range of applications. This paper proposes methods with which to extend the functionality of such systems, borrowing knowledge management concepts from the field of Agile Manufacturing. As such, this paper proposes that the future of intelligent systems design should be based not only upon the continuing development of artificial intelligence techniques, but also effective methods for harnessing human skills and core competencies to achieve these aims

COMPANIES ECONOMY IN CONTEXT OF THE ECONOMIC CRISIS

In this article I try to express components of the market economy which may affect an organization of the companies into a period whith decline and resignation reign in human activities. The economic crisis that is the a current world is the climax of financial turmoil which make integral part a normal legislative and the economic calculation which configures a demand and supply of goods.organizational arrangements; company; contracts; legislation; demand; supply; Microeconomics; economic calculation

Shipbuilding 4.0 Index Approaching Supply Chain

The shipbuilding industry shows a special interest in adapting to the changes proposed by the industry 4.0. This article bets on the development of an index that indicates the current situation considering that supply chain is a key factor in any type of change, and at the same time it serves as a control tool in the implementation of improvements. The proposed indices provide a first definition of the paradigm or paradigms that best fit the supply chain in order to improve its sustainability and a second definition, regarding the key enabling technologies for Industry 4.0. The values obtained put shipbuilding on the road to industry 4.0 while suggesting categorized planning of technologies

Crafting A Human Resource Strategy To Foster Organizational Agility: A Case Study

A decade ago, the CEO of Albert Einstein Healthcare Network (AEHN), anticipating a tumultuous and largely unpredictable period in its industry, undertook to convert this organization from one that was basically stable and complacent to one that was agile, “nimble, and change-hardy”. This case study briefly addresses AEHN’s approaches to business strategy and organization design, but focuses primarily on the human resource strategy that emerged over time to foster the successful attainment of organizational agility. Although exploratory, the study suggests a number of lessons for those who are, or will be, studying or trying to create and sustain this promising new organizational paradigm