Управління міжнародним бізнесом: 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, яка була розроблена вперше. Подальші дослідження на цю тему доцільно зосередити на розвитку гнучкого мислення як передумови забезпечення еджайльності в компанії

Bringing templates to life: overcoming obstacles to the organizational implementation of Agile methods

Agile software development methods have become accepted as a template for organizations to create new products. Though generally viewed as an aid to productivity, there are a number of barriers to experiencing their full benefit. One such barrier pertains to the implementation of agile methods across the range of organizational levels from the use of tools to culture, norms, and policies creating the context within which projects are performed. This essay examines in detail the experiences of one expert at integrating agile technique, approach, and philosophy into the broader organizational setting. Numerous particular lessons and prescriptions result from this discussion. Turning around the grounded theory approach where numerous individuals are interrogated mildly in regard to a particular phenomenon, the discussion surfaced in this paper results from repeated interviews with one domain expert. Lessons and comments are organized into four sections: individual team member, organization, transitioning, and tools and techniques

Agile challenges in practice: a thematic analysis

As agile is maturing and becoming more widely adopted, it is important that researchers are aware of the real-world challenges faced by practitioners and organisations. We undertook a thematic analysis of 193 agile challenges collected at a series of agile conferences and events during 2013 and 2014. Participants were mainly practitioners and business representatives along with some academics. The challenges were thematically analysed by separate authors, synthesised, and a list of seven themes and twenty-seven sub-themes was agreed. Themes were Organisation, Sustainability, Culture, Teams, Scale, Value and Misconceptions and shortcomings. We compare our findings against previous attempts to identify and categorise agile challenges. While most themes have persisted we found a shift of focus towards issues related to sustainability, business engagement and transformation, as well as misconceptions and shortcomings. We identify areas for further research and a need for more innovative methods of conveying academic research to industry and industrial problems to academi

Overcoming Language Dichotomies: Toward Effective Program Comprehension for Mobile App Development

Mobile devices and platforms have become an established target for modern software developers due to performant hardware and a large and growing user base numbering in the billions. Despite their popularity, the software development process for mobile apps comes with a set of unique, domain-specific challenges rooted in program comprehension. Many of these challenges stem from developer difficulties in reasoning about different representations of a program, a phenomenon we define as a "language dichotomy". In this paper, we reflect upon the various language dichotomies that contribute to open problems in program comprehension and development for mobile apps. Furthermore, to help guide the research community towards effective solutions for these problems, we provide a roadmap of directions for future work.Comment: Invited Keynote Paper for the 26th IEEE/ACM International Conference on Program Comprehension (ICPC'18

Lessons Learned from Distributed Agile Software Projects: A Case-Based Analysis

Agile software development in a distributed setting is challenging. The teams involved in the process face difficulties in communication, personnel selection, work culture, and knowledge management. The shortcomings associated with working in different time zones and the inabilities to develop trusting relationships between developers are well known. Companies often take recourse to agile software development methods in a distributed environment in search of reduced cost, higher efficiency, increased flexibility, and good customization. However, it is not clear whether agile methods can be successfully followed and their benefits realized in a distributed setting. This paper revisits and synthesizes the lessons learnt from twelve case studies detailing successful implementation of distributed agile software projects. The cases are analyzed from the perspective of the agile manifesto to determine how closely they follow its values and principles and to what extent they realize the benefits of the agile methodology. The cases lead to the discovery of disparate and innovative solutions adopted by different companies for overcoming the challenges of distributed agile software development. Some solutions are commonplace and others are unique and their combination in the context of the challenges is enlightening. The list of solutions can suitably guide companies that plan to adopt the agile methodology in distributed software development environments in future

An Exploratory Study of Automated Tools to Support SCRUM-Based Project Management in Agile Software Development Teams

The growing use of Agile Methodologies for project management has led many organizations to utilize agile-based project management tools. This thesis explores areas for improvement in project management tools for software development teams using the Scrum methodology. A qualitative research method was used to gain insight on the users\u27 satisfaction and possible new utilities to create that would complement the OnTime Scrum project management tool. This paper further describes the methods and experiences encountered in the designing and implementation of a Work Breakdown Structure website tool that was selected as a utility to support project management

CHARTING PROGRESS IN THE SOFTWARE ACQUISITION PATHWAY

The Department of the Navy (DON) recently implemented the Department of Defense (DOD) Software Acquisition Pathway (SWP), a software acquisition strategy for custom application and embedded software. The purpose of the SWP is to enable rapid and iterative delivery of high-priority software capability to the intended user. But while the SWP uses an agile software development approach, neither the DOD nor the DON have yet provided comprehensive governance tools and methods for SWP programs to iteratively plan, track, and assess acquisition outcomes in agile environments. To close this gap, the author systematically researched commercial software engineering management and digital product development practices as well as prior DOD software acquisition reform studies. Based on the results, the author showed that Earned Value Management is incompatible with the SWP and recommended alternative techniques to measure cost and schedule performance. Additionally, the author recommended a phased approach to manage DON SWP custom application programs, whereby a minimal, unitless work breakdown structure is used to track progress until demonstrating the minimum viable product to the user in a testing environment; product-based metrics are then tracked until initial release of the custom application software; and then outcome-based goals are iteratively set, tracked, and assessed using the Objectives and Key Results framework for as long as the custom application software is in use.Captain, United States Air ForceApproved for public release. Distribution is unlimited