Customized agile development process for embedded software development

Agile software development has grown in popularity starting from the agile manifesto declared in 2001. However there is a strong belief that the agile methods are not suitable for embedded, critical or real-time software development, even though multiple studies and cases show differently. This thesis will present a custom agile process that can be used in embedded software development. The reasons for presumed unfitness of agile methods in embedded software development have mainly based on the feeling of these methods providing no real control, no strict discipline and less rigor engineering practices. One starting point is to provide a light process with disciplined approach to the embedded software development. Agile software development has gained popularity due to the fact that there are still big issues in software development as a whole. Projects fail due to schedule slips, budget surpassing or failing to meet the business needs. This does not change when talking about embedded software development. These issues are still valid, with multiple new ones rising from the quite complex and hard domain the embedded software developers work in. These issues are another starting point for this thesis. The thesis is based heavily on Feature Driven Development, a software development methodology that can be seen as a runner up to the most popular agile methodologies. The FDD as such is quite process oriented and is lacking few practices considered commonly as extremely important in agile development methodologies. In order for FDD to gain acceptance in the software development community it needs to be modified and enhanced. This thesis presents an improved custom agile process that can be used in embedded software development projects with size varying from 10 to 500 persons. This process is based on Feature Driven Development and by suitable parts to Extreme Programming, Scrum and Agile Modeling. Finally this thesis will present how the new process responds to the common issues in the embedded software development. The process of creating the new process is evaluated at the retrospective and guidelines for such process creation work are introduced. These emphasize the agility also in the process development through early and frequent deliveries and the team work needed to create suitable process.Siirretty Doriast

Project Management Tools in Agile Embedded Systems Development

Agile methods have become increasingly popular in the field of software engineering. While agile methods are now generally considered applicable to software projects of many different kinds, they have not been widely adopted in embedded systems development. This is partly due to the natural constraints that are present in embedded systems development (e.g. hardware–software interdependencies) that challenge the utilization of agile values, principles and practices. The research in agile embedded systems development has been very limited, and this thesis tackles an even less researched theme related to it: the suitability of different project management tools in agile embedded systems development. The thesis covers the basic aspects of many different agile tool types from physical tools, such as task boards and cards, to web-based agile tools that offer all-round solutions for application lifecycle management. In addition to these two extremities, there is also a wide range of lighter agile tools that focus on the core agile practices, such as backlog management. Also other non-agile tools, such as bug trackers, can be used to support agile development, for instance, with plug-ins. To investigate the special tool requirements in agile embedded development, the author observed tool related issues and solutions in a case study involving three different companies operating in the field of embedded systems development. All three companies had a distinct situation in the beginning of the case and thus the tool solutions varied from a backlog spreadsheet built from scratch to plug-in development for an already existing agile software tool. Detailed reports are presented of all three tool cases. Based on the knowledge gathered from agile tools and the case study experiences, it is concluded that there are tool related issues in the pilot phase, such as backlog management and user motivation. These can be overcome in various ways epending on the type of a team in question. Finally, five principles are formed to give guidelines for tool selection and usage in agile embedded systems development.Siirretty Doriast

Integrating agile software development into stage-gate managed product development

Agile methods have evolved as a bottom-up approach to software development. However, as the software in embedded products is only one part of development projects, agile methods must coexist with project management models typically of the stage-gate type. This paper presents a qualitative case study of two large independent software system projects that have used eXtreme Programming (XP) for software development within contexts of stage-gate project management models. The study is comprised of open ended interviews with managers as well as practitioners, followed by a structured, fully traceable, qualitative analysis. We conclude that it is possible to integrate XP in a gate model context. Key issues for success are the interfaces towards the agile subproject and management attitudes towards the agile approach

AM-OER: An Agile Method for the Development of Open Educational Resources

Open Educational Resources have emerged as important elements of education in the contemporary society, promoting life-long and personalized learning that transcends social, eco- nomic and geographical barriers. To achieve the potential of OERs and bring impact on education, it is necessary to increase their development and supply. However, one of the current challenges is how to produce quality and relevant OERs to be reused and adapted to different contexts and learning situations. In this paper we proposed an agile method for the development of OERs – AM-OER, grounded on agile practices from Software Engineering. Learning Design practices from the OULDI project (UK Open University) are also embedded into the AM-OER aiming at improving quality and facilitating reuse and adaptation of OERs. In order to validate AM-OER, an experiment was conducted by applying it in the development of an OER on software testing. The results showed preliminary evidences on the applicability, effectiveness and ef ciency of the method in the development of OERs

Agile Case Study Evaluation In Middle Size Project

In the last few years Agile methodologies appeared as a reaction to traditional ways of developing software and acknowledge the need for an alternative to documentation driven, heavyweight software development processes. This paper shortly presents a combination between Rational Uni ed Process and an agile approach for software development of e-business applications. The resulting approach is described stressing on the strong aspects of both combined methodologies. The article provides a case study of the proposed methodology which was developed and executed in a successful e-project in the area of the embedded systems

The Vortex of Continuous Development of Embedded Systems: An Inquiry into Agility Orchestration

Agile methodologies have become a popular and widely accepted method for managing software development. Since the inception of the Agile Manifesto over ten years ago, agile development techniques have superseded waterfall methods in many, if not most, software development organizations. Despite its apparent success, many companies have struggled with the adoption and implementation of agile, and exactly what level of adoption provides optimum agility. Agility is commonly held in the literature to be constructed of elements external to a company or project but may in fact be composed of both external and internal elements. The exact relationship of the adoption of agile development techniques and their relationship to the actual agility of a business remain unclear. A primary contributor to this uncertainty is the somewhat amorphous definition of agile itself. In academic literature, the concept is still relatively young and loosely defined. In practice, organizations have largely opted for a hybrid approach to agile, mixing its concepts and methods with existing Stage Gate or waterfall methodologies. This has made the management of agile even more complex. Crucially, there is no definition or criterion available to determine the appropriate mix of agile and waterfall processes in an embedded software development context nor is there a method to determine the impact of one against the other. These issues beg the question: how do organizations manage agility? This interpretive case study provides an empirical account of how stakeholders manage both market and process agility in an embedded systems context via a hybrid agility implementation and product genesis. As a result, we provide the notion of agile vorticity, as the point at which market and process agility collide to produce business momentum at a specific point of innovation within the agile business vortex

Work-in-Progress - AgiES: Agile Methods for Embedded System Development

AgiES project aims to develop and utilize agile methods for the development of embedded systems covering all of its parts such as electronic hardware, hardware dependent software, and digital integrated circuit design. Agile philosophy is famous in the field of software engineering but rarely used in the development of embedded systems due to the more rigid nature of it. Our goal is to gather a toolbox of agile practices which may be adopted by teams developing embedded systems. These practices originate from principles presented in Agile Manifesto and they are said to improve development team productivity and well-being at work. Attention will be also paid into collaboration between agile and traditionally working teams as well as intointeraction between developers and customers

Sustaining Agile Beyond Adoption

Agile approaches are adopted in industry to improve outcomes from software development, and are increasingly the subject of research studies. However, adoption is not the end of the story. Agile requires on-going change and commitment in order to become sustainable and embedded within teams and organisations. This study explores current perceptions of post-adoptive agility. We asked 50 practitioners ‘what does agile sustainability mean to you?’. Analysis of practitioner comments identified four themes: being completely agile, independent, focused on business value and need, and consistent across time. Post-adoptive agile is an under-researched area, there is inconsistent use of terminology, and there is a gap between practitioners’ and researchers’ perceptions about what is important for sustaining agile

The Sync-Up Process to Improve the Multiple Stakeholder Communication of Requirements Analysis in Embedded Medical Software Development

The development of embedded medical software is different from ordinary software development as it needs to be coordinated with the hardware development. A typical embedded system project involves multiple stakeholders such as the business unit, software developers, hardware engineers and firmware developers. Agile methods have been successfully adopted in generic software engineering, and more recently in embedded medical software development. In this research, a systematic review has been performed to identify the challenges of embedded medical and safety-critical software development domains. From the challenges identified, this research focuses on the challenge of multiple stakeholder communication in embedded medical software development. Additionally, agile practices which have been successfully adopted in the embedded safety-critical domains have been investigated. This thesis describes the development and evaluation of a process (Sync-Up) to improve multiple stakeholder communication for embedded medical software development during requirement analysis. Through this research, the following contribution to knowledge has been made in the area of embedded medical domain. The development of the Sync-Up process to assist multiple stakeholder communication of embedded medical software development. The Sync-Up process is evaluated through both expert review by leading experts, and a case study conducted in an embedded company. Findings from the evaluations undertaken show a positive outcome during the requirement analysis phase of the Sync-Up process