Управління міжнародним бізнесом: Agility Journey для високотехнологічних компаній

The purpose of the article is the development of recommendations for the business maturity determination and measurement in the implementation of the agile approach for high-tech companies. Methods of analysis of documents, observation, personal and in-depth interviews, case studies have been used in the research. The findings of the research: Business Agility Journey has been suggested for defining the state of the maturity of the company and conducting express diagnostics of agility. Agile Project Management Journey has been developed for the identification of weaknesses by the companies in the path to agility, as well as for the determination of events for the transition from the traditional to the agile approach. Personal Agility Checklist has been designed for testing the soft skills of employees for the presence of the agile mindset. Research limitations include the study of the maturity of companies in the IT industry. Practical implications are based on the use of suggested Agility Journeys in defining the state of maturity and main problems on the transition path. Also, Personal Agility Checklist will help to check the agility of the future employees. The originality of the article is based on the uniqueness of the Agility Journey that has been developed for the first time. Further research on this topic should be focused on the development of an agile mindset as a prerequisite for the provision of agility in the company.Метою статті є розробка рекомендацій щодо визначення та вимірювання зрілості бізнесу при впровадженні еджайл-підходу для високотехнологічних компаній. У дослідженні використовуються методи аналізу документів, спостереження, особистого та глибинного інтерв’ю та кейс-стаді. Розроблено Business Agility Journey для визначення стану зрілості компанії та проведення експрес-діагностики еджайльності. Agile Project Management Journey було розроблено для визначення компаніями своїх слабких сторін, а також заходів для переходу від традиційного до еджайльного підходу. Personal Agility Checklist був створений для перевірки «гнучких навичок» (soft skills) співробітників на наявність гнучкого мислення (agile mindset). Обмеження досліджень включають вивчення зрілості компаній ІТ-галузі. Практична значущість ґрунтується на використанні запропонованих Agility Journeys для визначення стану зрілості та основних проблем на шляху переходу. Також Personal Agility Checklist допоможе перевірити еджайльність майбутніх працівників. Оригінальність статті базується на унікальності Agility Journey, яка була розроблена вперше. Подальші дослідження на цю тему доцільно зосередити на розвитку гнучкого мислення як передумови забезпечення еджайльності в компанії

Addressing challenges to teach traditional and agile project management in academia

In order to prepare students for a professional IT career, most universities attempt to provide a current educational curriculum in the Project Management (PM) area to their students. This is usually based on the most promising methodologies used by the software industry. As instructors, we need to balance traditional methodologies focused on proven project planning and control processes leveraging widely accepted methods and tools along with the newer agile methodologies. Such new frameworks emphasize that software delivery should be done in a flexible and iterative manner and with significant collaboration with product owners and customers. In our experience agile methodologies have witnessed an exponential growth in many diverse software organizations, and the various agile PM tools and techniques will continue to see an increase in adoption in the software development sector. Reflecting on these changes, there is a critical need to accommodate best practices and current methodologies in our courses that deliver Project Management content. In this paper we analyse two of the most widely used methodologies for traditional and agile software development – the widely used ISO/PMBOK standard provided by the Project Management Institute and the well-accepted Scrum framework. We discuss how to overcome curriculum challenges and deliver a quality undergraduate PM course for a Computer Science and Information systems curricula. Based on our teaching experience in Europe and North America, we present a comprehensive comparison of the two approaches. Our research covers the main concepts, processes, and roles associated with the two PM frameworks and recommended learning outcomes. The paper should be of value to instructors who are keen to see their computing students graduate with a sound understanding of current PM methodologies and who can deliver real-world software products.Accepted manuscrip

Walking Through the Method Zoo: Does Higher Education Really Meet Software Industry Demands?

Software engineering educators are continually challenged by rapidly evolving concepts, technologies, and industry demands. Due to the omnipresence of software in a digitalized society, higher education institutions (HEIs) have to educate the students such that they learn how to learn, and that they are equipped with a profound basic knowledge and with latest knowledge about modern software and system development. Since industry demands change constantly, HEIs are challenged in meeting such current and future demands in a timely manner. This paper analyzes the current state of practice in software engineering education. Specifically, we want to compare contemporary education with industrial practice to understand if frameworks, methods and practices for software and system development taught at HEIs reflect industrial practice. For this, we conducted an online survey and collected information about 67 software engineering courses. Our findings show that development approaches taught at HEIs quite closely reflect industrial practice. We also found that the choice of what process to teach is sometimes driven by the wish to make a course successful. Especially when this happens for project courses, it could be beneficial to put more emphasis on building learning sequences with other courses

Cyber physical systems implementation for asset management improvement: A framework for the transition

Libro en Open AccessThe transformation of the industry due to recent technologies introduction is an evolving process whose engines are competitiveness and sustainability, understood in its broadest sense (environmental, economic and social). This process is facing, due to the current state of scientific and technological development, a new challenge yet even more important: the transition from discrete technological solutions that respond to isolated problems, to a global conception where the assets, plant, processes and engineering systems are conceived, designed and operated as an integrated complex unit. This vision is evolving besides a set of concepts that are, in some way, to guide this development: Smart Factories, Cyber-Physical Systems, Factory of the Future or Industry 4.0, are examples. The full integration of the operation and maintenance (O&M) processes in the production systems is a key topic within this new paradigm. Not only that, this evolution necessarily results in the emergence of new processes and needs of O&M, i.e. also, the O&M will undergo a profound transformation. The transition from actual isolated production assets to such Industry 4.0 with CPS is far from easy. This document presents a proposal to develop such transition adapting one iteration of the Model of Maintenance Management (MMM) integrated into ISO 55000 to the complexity of incorporating “System of Systems” CPSs maintenance. It involves several stages: identification, prioritization, risk management, planning, scheduling, execution, control, and improvement supported by system engineering techniques and agile/concurrent project managemen

Designing a consulting services architecture model

textDuring my years of experience in the technology industry, it has become obvious that standard processes and methodologies within the engineering discipline are at a mature state. The realization though is that software engineering specifically lags behind. Most software engineering methodologies that I have studied focus on the mission of software development. It is this realization and the need for structure that led me to review existing methodologies used within my company's software services organization. The definition of what a successful software services methodology entails is rather limited. This report will provide a history of existing software engineering methodologies that I have studied, describe an initial services method that was being developed within my organization, develop a new model that addresses previous shortcomings and identify additional components required to further define a strong software services-oriented delivery methodology.Electrical and Computer Engineerin

Bridging the gap between research and agile practice: an evolutionary model

There is wide acceptance in the software engineering field that industry and research can gain significantly from each other and there have been several initiatives to encourage collaboration between the two. However there are some often-quoted challenges in this kind of collaboration. For example, that the timescales of research and practice are incompatible, that research is not seen as relevant for practice, and that research demands a different kind of rigour than practice supports. These are complex challenges that are not always easy to overcome. Since the beginning of 2013 we have been using an approach designed to address some of these challenges and to bridge the gap between research and practice, specifically in the agile software development arena. So far we have collaborated successfully with three partners and have investigated three practitioner-driven challenges with agile. The model of collaboration that we adopted has evolved with the lessons learned in the first two collaborations and been modified for the third. In this paper we introduce the collaboration model, discuss how it addresses the collaboration challenges between research and practice and how it has evolved, and describe the lessons learned from our experience

Scalable agile frameworks in large enterprise project portfolio management

Con un alcance de estudio exploratorio, debido a que se ha investigado poco y se encuentra en un estado emergente, el propósito de la investigación fue explorar la implementación de los marcos ágiles escalables en la gestión del portafolio de proyectos (PPM) de grandes empresas. Además, este estudio de caso cualitativo planteó la siguiente pregunta principal de investigación: ¿De qué manera los marcos ágiles escalables se implementan en la PPM de grandes empresas, y por qué? Este estudio recopiló información de 59 portafolios de proyectos en 22 empresas con implementaciones de métodos ágiles y marcos ágiles escalables de las industrias tecnologías de la información (IT- por sus siglas en inglés), financiera y telecomunicaciones, de México, Colombia, Perú, Ecuador, Costa Rica y Chile, mediante 43 entrevistas en profundidad semiestructuradas. Los hallazgos revelan que existen portafolios de proyectos con alta variabilidad en servicio, producto e innovación, y con implementaciones híbridas de Scaled Agile Framework (SAFe), Spotify Model y Scrum. Además, enfrentan diferentes desafíos relacionados con la implementación de los marcos ágiles escalables en la PPM, la cultura organizacional, resistencia al cambio y liderazgo estratégico. Del mismo modo, los hallazgos demuestran que los marcos ágiles son una opción viable para optimizar el time-to-market, aumentar la productividad de los equipos y mejorar la comunicación a nivel general. Este estudio es uno de los primeros en explorar cómo implementan las grandes empresas los marcos ágiles escalables en la PPM para llenar el vacío en la literatura relacionado con cómo y cuándo las empresas deben abordar un proceso de transformación ágil que funcione de manera exitosa en su PPM. Por lo tanto, este estudio proporciona evidencia empírica de seis países latinoamericanos como base potencial para futuras investigaciones y publicaciones.With an exploratory study scope, due to little research and in an emerging state, the purpose of the research was to explore the implementation of scalable agile frameworks in project portfolio management (PPM) of large enterprises. This qualitative case study posed as its primary research question: How and why are scalable agile frameworks implemented in the PPM of large companies? Further, this study used the purposive sampling method and the snowball technique. Data were collected from 59 project portfolios in 22 companies with agile and scalable agile framework implementations in the information technology (IT), financial and telecommunications industries in Mexico, Colombia, Peru, Ecuador, Costa Rica and Chile, through 43 semi-structured in-depth interviews. The findings reveal that there are project portfolios with high variability in service, product and innovation, and with hybrid implementations of Scaled Agile Framework (SAFe), Spotify Model and Scrum. In addition, they face different challenges related to the implementation of scalable agile frameworks in PPM, organizational culture, resistance to change, and strategic leadership. Similarly, the findings demonstrate that agile frameworks are a viable option to optimize time-to-market, increase team productivity and improve communication across the board. This study represents one of the first to explore how large companies implement scalable agile frameworks in PPM to fill the gap in the literature related to how and when companies should approach an agile transformation process working successfully in their PPM. Accordingly, this study provides empirical evidence from six Latin American countries as a potential basis for future research and publications