2,307 research outputs found

    Hybrid Software Development Approaches in Practice: A European Perspective

    Get PDF
    Agile and traditional development approaches are used in combination in todays software development. To improve the understanding and to provide better guidance for selecting appropriate development approaches, it is important to analyze such combinations in practice. Results obtained from an online survey strongly confirm that hybrid development approaches are widely used in industry. Our results show that hybrid development approaches: (i) have become reality for nearly all companies; (ii) are applied to specific projects even in the presence of company-wide policies for process usage; (iii) are neither planned nor designed but emerge from the evolution of different work practices; and, (iv) are consistently used regardless of company size or industry secto

    Roles and responsibilities in agile ICT for development

    Get PDF
    This paper examines the different roles in designing interactive software in a ICT for development context. Using experiences from a participatory action research project, in which we used agile methods to design and deploy an system to support ‘agricultural information flow’ for a co-operative of small farmers in rural India, we identify points of difference between the roles in standard descriptions of agile software methods and the roles as they emerged in our project. A key finding is the critical role played by a ‘Development Project Manager’ in facilitating dialogue, orchestrating the activities of other actors and in building the capabilities and confidence of all the participants in joint action

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

    Get PDF
    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

    Scaling agile using scaled agile framework

    Get PDF

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

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

    Uppskalning av agil systemutveckling: en flerfallstudie av ramverket Scaled Agile Framework

    Get PDF
    Agile software development methods have been extensively studied in the context for which they were originally developed: small, collocated and cross-functional teams. The proven benefits of agile methods have caused larger organizations and programs to take an interest in them, although adopting such methods at large is far more challenging. Several frameworks for adopting agile methods in a larger context exist but research surrounding them is scarce, consisting almost entirely of industry-produced experience reports. In this thesis we have studied the adoption of a popular scaling framework, the Scaled Agile Framework (SAFe), in two Finnish companies: Comptel, a telecom company; and NAPA, a company specialized in ship design and operation software. We sought to understand why these organizations chose to adopt SAFe, how they did it, what successes and challenges related to the adoptions the organizations encountered, and what effects the adoptions had. We reviewed existing literature in order to find out why and how other organizations had adopted SAFe. Using the results of the review we constructed a set of questions which we used in 16 interviews at the case organizations. The interviews spanned all organizational layers of SAFe: we interviewed people from leadership, middle management, and teams. The results of the interviews support many of the findings of the literature review, showing that planning the adoption in detail, training key personnel, and putting significant effort into the first planning session are key success factors in adopting SAFe. The interviews also showed that internal drivers of change are vital in establishing support for the adoption. Our results indicate that SAFe is a viable option for scaling agile software development, potentially improving visibility, collaboration and alignment.Agila systemutvecklingsmetoder blir allt vanligare och har studerats extensivt i den kontext för vilken de ursprungligen utformats: små självorganiserande och samordnade team. De påvisade fördelarna med agila metoder leder allt fler och större organisationer till att försöka implementera dem---dock växer svårighetsgraden i takt med organisationsstorleken. Ett flertal ramverk för uppskalning av agila metoder existerar, men akademisk forskning kring ämnet saknas nästan helt då majoriteten av litteraturen är fallstudier av varierande kvalité. I detta diplomarbete har vi studerat ibruktagningarna av det populära ramverket Scaled Agile Framework (SAFe) i två finska företag: Comptel, ett globalt telekommunikationsföretag; och NAPA, ett företag specialiserat på mjukvara för formgivning och anförande av fartyg. Vi ville förstå varför företagen valt att ibrukta SAFe, hur de gjort det, vilka problem och framgångsfaktorer de stötte på, samt vilka effekter ibruktaganden hade. Vi undersökte den existerande litteraturen för att få preliminära svar på de ovannämnda frågorna, och skapade en serie intervjufrågor på basis av resultaten. Dessa brukade vi i 16 intervjuer vid fallföretagen, där vi intervjuade ledare, mellanchefer samt medlemmar av team i ett försök att täcka alla de lager av organisationen som även SAFe täcker. Intervjuresultaten stöder många av litteraturstudiens resultat: noggrant planerande av ibruktagningen, utbildning av nyckelroller, samt en storsatsning på det första planeringstillfället är viktiga framgångsfaktorer för ibruktagandet. Intervjuerna visade också att interna pådrivare av förändringen är essentiella för att samla stöd för ibruktagandet. Våra resultat tyder på att SAFe är ett genomförbart alternativ för att uppskala agil systemutveckling, då det kan medföra ökad synlighet, ökat samarbete samt bättre anslutning mot ett gemensamt mål

    Large-Scale Agile Frameworks: A Comparative Review

    Get PDF
    This study aims to identify and systematically compare the main large-scale agile frameworks that companies can adopt to manage the work of large-scale and distributed teams. Through this, companies can more consciously perform a better-informed decision on the choice of the framework that best fits the practices and challenges of their organizations. This work employs a qualitative approach supported by an exploratory analysis that identifies and explores the processes of migration to a large-scale agile. In the first phase, fifteen assessment criteria for scaling agile are discussed. In a second phase, these criteria are used to perform a comparative analysis of six large-scale agile frameworks (i.e., DAD, LeSS, Nexus, SAFe, Scrum at Scale, and Spotify). The findings reveal there isn't a dominant large-scale agile framework in all dimensions. However, it is possible to identify frameworks like Nexus and Spotify that target smaller teams and offer low technical complexity. These frameworks easily accommodate changes, while there are other frameworks like SAFe and DAD that offer high levels of scalability but require more demanding and deep efforts in changing work processes in an organization
    corecore