Its time to act:understanding and assessing agility in information systems development

This paper focuses on addressing the question of how agile are agile methods. To do this I synthesize seven general features of agility, drawing on management and sociology disciplines, into a framework, to act as a ‘gold standard’ by which to compare agile methods. I found that agile methods did not entirely measure up to this framework and that they were lacking in terms of (i) survival, (ii) prospering or thriving on change, and (iii) being able to regulate and leverage emotions in action responses to change. This paper offers: (i) a framework for assessing agility in software development, (ii) the elucidation of a knowledge gap in agile methods with respect to emotion, and, (iii) a conceptualization that reveals the need to incorporate emotional regulation and leverage into assessments of agility

The Impact of Group Cohesiveness on Decision-Making Outcomes under Conditions of Challenging and Hindrance Time Pressure

Group decision making is increasingly important for the successful completion of software development projects. Group oriented development approaches such as agile methods, which emphasize a sense-and-respond approach are becoming an integral part of software development. These methods are being used by an increasing number of organizations as a means of improving the agility and quality of the development process, and within these processes groups are increasingly involved in critical decision making. Groups are required to make regular group decisions and group members work closely with each other to develop software in time-boxed iterations. However, the literature lacks a clear understanding about how varying degrees of time pressure affects the decision outcomes of the development groups. As group cohesion is viewed as the most fundamental issue facing group decision-making processes, in this research-in-progress paper we develop a research instrument to measure the impact of time pressure and group cohesion on decision-making outcomes

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

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