Self-Adaptability of Agile Software Processes: A Case Study on Post-iteration Workshops

2004 ◽  
pp. 184-193 ◽  
Author(s):  
Outi Salo ◽  
Kari Kolehmainen ◽  
Pekka Kyllönen ◽  
Jani Löthman ◽  
Sanna Salmijärvi ◽  
...  
Keyword(s):  
Software Processes ◽  
Agile Software

scholarly journals Digital Transformation of Forest Services in Finland—A Case Study for Improving Business Processes

Forests ◽  
2021 ◽  
Vol 12 (6) ◽  
pp. 781
Author(s):  
Ville Kankaanhuhta ◽  
Tuula Packalen ◽  
Kari Väätäinen
Keyword(s):  
Business Processes ◽  
Innovation Process ◽  
Single Type ◽  
Stand Management ◽  
Young Stand ◽  
Commercial Viability ◽  
Soil Preparation ◽  
Knowledge Intensive ◽  
Agile Software

This case study introduces an innovation and development concept for agile software tools for the improvement of the productivity and customer experience of forest services. This need was recognized in the context of the opening of forest data and the development of service platforms for a forest-based bioeconomy in Finland. The forest services that were studied covered a continuum from a single type of work, e.g., soil preparation and young stand management through timber procurement, to comprehensive forest property management services. The study concentrated on the needs of micro-, small, and medium-sized enterprises (SMEs), which provide either retail- or business to business (B2B) services as sub-contractors. In addition, the challenges and bottlenecks in service processes detected by other stakeholders were considered. The prevailing service processes were conceptually modelled in order to search for opportunities for improvements in business and ecosystem services, i.e., agile software concepts. For example, we examined whether it would be possible to create opportunities for flexible operational models for precision, resilience, and protection of valuable microsites in forests. These software concepts were developed and evaluated in co-operation with the stakeholders in a co-creative workshop. The technological feasibility and commercial viability of the concepts, as well as the desirability for the customer were considered. The results of this business development process—i.e., agile software concepts and their anticipated benefits—were provided for further evaluation. In addition to the practical implications of this kind of innovation process tested, the potential of these kinds of agile tools for the further development of knowledge-intensive service processes was further discussed.

scholarly journals Towards Regulatory-Compliant MLOps: Orazivio’s Journey from a Machine Learning Experiment to a Deployed Certified Medical Product

2021 ◽  
Vol 2 (5) ◽  
Author(s):  
Tuomas Granlund ◽  
Vlad Stirbu ◽  
Tommi Mikkonen
Keyword(s):  
Machine Learning ◽  
Joint Replacement ◽  
Medical Product ◽  
Medical Software ◽  
Continuous Delivery ◽  
Development Approach ◽  
Responding To Change ◽  
Agile Software ◽  
Engineering Practices

AbstractAgile software development embraces change and manifests working software over comprehensive documentation and responding to change over following a plan. The ability to continuously release software has enabled a development approach where experimental features are put to use, and, if they stand the test of real use, they remain in production. Examples of such features include machine learning (ML) models, which are usually pre-trained, but can still evolve in production. However, many domains require more plan-driven approach to avoid hazard to environment and humans, and to mitigate risks in the process. In this paper, we start by presenting continuous software engineering practices in a regulated context, and then apply the results to the emerging practice of MLOps, or continuous delivery of ML features. Furthermore, as a practical contribution, we present a case study regarding Oravizio, first CE-certified medical software for assessing the risks of joint replacement surgeries. Towards the end of the paper, we also reflect the Oravizio experiences to MLOps in regulatory context.

Agile Software Development Process Applied to the Serious Games Development for Children from 7 to 10 Years Old

2015 ◽  
Vol 8 (2) ◽  
pp. 64-79 ◽  
Author(s):  
Sandra P. Cano ◽  
Carina S. González ◽  
César A. Collazos ◽  
Jaime Muñoz Arteaga ◽  
Sergio Zapata
Keyword(s):  
Serious Games ◽  
User Profile ◽  
Extreme Programming ◽  
Agile Development ◽  
User Centered Design ◽  
Medium Development ◽  
Development Methodology ◽  
Agile Software ◽  
The City

The development of video games is a complex, multidisciplinary process, which involves different areas as well as a greater number of roles than for traditional software. Serious games face process constraints that concern a number of interactive, educational and psychological factors designed to lead to the fulfillment of educational objectives within a specific context. Based on a case study in the city Cali, Colombia, an iterative and incremental process is proposed, focusing on small and medium development for educational serious games and basing itself on two lines of research: agile development methodology and user-centered design (UCD) for children from 7 to 10 years. The agile methodology eXtreme Programming (XP) offers a useful option for the development of serious games as it establishes a continuous communication with all project stakeholders - including the end user - throughout the project, while UCD allows the user profile to be known and identified so that the game will meet the needs and match the capabilities, expectations and motivations of the child.

Case study on risk management practice in large offshore‐outsourced Agile software projects

IET Software ◽  
2014 ◽  
Vol 8 (6) ◽  
pp. 245-257 ◽  
Author(s):  
Srikrishnan Sundararajan ◽  
Marath Bhasi ◽  
Pramod K. Vijayaraghavan
Keyword(s):  
Risk Management ◽  
Management Practice ◽  
Software Projects ◽  
Agile Software

Agile Software Development

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

Fixed Priced Projects in Agile

2016 ◽  
pp. 222-236
Author(s):  
Anuradha Chaminda Gajanayaka
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Model ◽  
Software Development Model ◽  
Responding To Change ◽  
The One ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Agile software development has established as a reliable alternative to waterfall software development model. Unfortunately the use of agile software development has been limited to time based contracts and not for time limited contracts. The main reason for this limitation is the “Agile manifesto” itself. The forth value of the manifesto states that agile believers find more value in “Responding to change over following a plan”. This is the one of the main reasons why agile software development methods are not preferred for a fixed priced contract or time limited contract. The following case study provides an example on how the agile software development can be used for fixed priced software development contracts even when operating in offshore context. The agile software development concepts were used throughout to plan, execute, monitor, report, etc. for the project documented in this case study.

How the Design of a 3D Printer Bridged Engineering Design Processes and the Agile Software Manifesto

2019 ◽  
Author(s):  
Steven Lindberg ◽  
Matthew I. Campbell
Keyword(s):  
Engineering Design ◽  
Design Process ◽  
Limited Resources ◽  
Small Scale ◽  
Design Processes ◽  
The Past ◽  
Engineering Design Process ◽  
Agile Software ◽  
Scale Design

Abstract Individual engineering design projects face different challenges depending on their scale. Instead of dealing with problems of complex multidisciplinary systems, small scale design must overcome issues of limited resources. The philosophy of agile software development has been highly successful in addressing similar issues in the software engineering realm over the past two decades. Through the design and prototyping of a low-budget desktop stereolithography printer, the application of agile principles to engineering design process is explored. The printer’s design is discussed in detail to provide examples of successes and failures when these agile principles are put into practice. The paper concludes with a discussion of how agile principles could be leveraged in engineering design. The approach taken in this paper is more of a longitudinal study of a single design process over a twelve-month period as opposed to rigorous experiments that engage multiple users in short design scenarios. Nonetheless, this case study demonstrates how the application of agile principles can inform, improve, and complement traditional engineering design processes.

Sign in / Sign up

Export Citation Format

Share Document