Software Development Using an Agile Approach for Satellite Camera Ground Support Equipment

2007 ◽  
pp. 71-76 ◽  
Author(s):  
D. dos Santos ◽  
I. N. da Silva ◽  
R. Modugno ◽  
H. Pazelli ◽  
A. Castellar
Keyword(s):  
Software Development ◽  
Ground Support ◽  
Agile Approach

scholarly journals SOME ASPECTS OF AGILE APPROACH IN PRAXIS

2015 ◽  
Vol 3 ◽  
pp. 348-355
Author(s):  
Jaroslava Kniežová
Keyword(s):  
Software Development ◽  
Development Process ◽  
Traditional Approach ◽  
High Quality ◽  
Modern Times ◽  
Effective System ◽  
Agile Approach ◽  
Traditional Process ◽  
Short Time

In modern times, competitiveness in the market depends on having a good information system. The companies developing and supplying information systems are in competition too, and having an effective system of delivery is critical for obtaining lucrative offers. Therefore, the software development companies continuously try to improve their development process to supply the product in a short time and with high quality. The agile approach potentially shortens this time and is very often used. This approach has almost replaced the traditional process. More and more companies implement agile approach in these times to be competitive in the software development market and hasten product delivering.The traditional and agile approaches differ in certain perspectives. Hence, the question arises as to whether the agile approach is the best for the software development company in every case. This article contains a comparison of these two approaches, as well as a case study relating to the agile approach in a real software development company, which had previously used the traditional approach. The article also describes situation where replacing the traditional approach with agile would improve results.

Learning Scrum

2021 ◽  
pp. 169-189
Author(s):  
Simon Bourdeau ◽  
Alejandro Romero-Torres ◽  
Marie-Claude Petit
Keyword(s):  
Data Collection ◽  
Software Development ◽  
Real World ◽  
Learning Experience ◽  
Project Managers ◽  
Development Projects ◽  
Simulation Based ◽  
Realistic Representation ◽  
Learn By Doing ◽  
Agile Approach

The LEGO®-Scrum simulation-based training (SBT) described here shows how LEGO® bricks can help professionals learn first-hand about Scrum methodology, an Agile approach to software development projects. The chapter's objectives are 1) to present the modalities of the LEGO®-Scrum SBT, 2) to demonstrate how LEGO® bricks can help professionals learn, first-hand, about Scrum, and 3) to illustrate how this learning can be relevant and impactful for participants. Based on observations, interviews, and a data collection by questionnaire carried out with 198 participants, the proposed SBT appears to provide a significant, relevant, and valuable learning experience. In addition, four experienced Scrum masters and IT project managers, who played key roles in the SBT, argued that the LEGO®-Scrum SBT provides a realistic representation of real-world Scrum projects; that it is dynamic, complex, challenging, and motivating; and that participants' learning is evocative and relevant, since they learn by doing.

scholarly journals Analysing the Obstacles in Agile Software Development Approach: A Review

2022 ◽  
Vol 5 (1) ◽  
pp. 1-6
Author(s):  
Amos O. Jarikre ◽  
Yogesh Kumar Sharma ◽  
Amoako Kani John ◽  
Stercy Kwasi Bailey
Keyword(s):  
Software Development ◽  
Database Search ◽  
Agile Development ◽  
Motivating Factors ◽  
Software Developers ◽  
Developmental Approach ◽  
Agile Approach ◽  
Development Approach ◽  
Agile Software ◽  
Extensible Software

The development of reusable and extensible software for business purposes has been the hallmark of the day. More developers are taking advantage of numerous approaches towards reaching their goals. One such approach is the agile approach in the development of extensible applications which has become so popular since its introduction over a decade ago. Using an agile approach that has a defined value in developing applications portray numerous benefits which have been identified by various scholars pointing out their outcomes as motivating factors of its adoption. With all such outline benefits, there exist some potential obstacles to agile developmental approach which has not been fully addressed. Hence, this article is aimed at analysing the obstacles which software developers face during agile development through a database search and also to guide them on ways to overcome such obstacles.

Reuse in Agile Development Process

2022 ◽  
pp. 1511-1534
Author(s):  
Chung-Yeung Pang
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Development ◽  
Reusable Software ◽  
Model Driven ◽  
Development Processes ◽  
Agile Approach ◽  
Similar Solutions ◽  
Agile Software ◽  
Model Driven Approach

Reusability is a clear principle in software development. However, systematic reuse of software elements is not common in most organizations. Application programmers rarely design and create software elements for possible future reuse. In many agile software development processes, the project teams believe that the development of reusable software elements can slow down the project. This can be a misconception. This chapter examines various ways to reuse software. Three approaches to developing reusable software artifacts from 15 years of experience in the agile development process are presented. The first approach is to create generic programs or configurable frameworks that support similar solutions for a variety of use cases and environments. The reuse of patterns is the second approach presented. Another effective way is to use a model-driven approach with model patterns. These approaches help to speed deployment software. The final product is flexible and can easily be adapted to changes. This is one of the main goals of an agile approach.

Agile at IBM: software developers teach a new dance step to management

2014 ◽  
Vol 42 (2) ◽  
pp. 26-29 ◽  
Author(s):  
Robert M. Randall
Keyword(s):  
Software Development ◽  
Traditional Approach ◽  
Agile Software Development ◽  
Software Systems ◽  
Content Type ◽  
The Future ◽  
Agile Approach ◽  
Development Approach ◽  
Agile Software ◽  
Marketing Teams

Purpose – Explains how companies that are seeking to implement rapid innovation can adopt the Agile software development approach. In Agile, self-organizing teams work in short cycles called “sprints” and develop the features to enable the product to continuously evolve in the light of the experience they gain and through customer feedback. Design/methodology/approach – For insight into how Agile is being implemented at a leading software services firm with clients in hundreds of industries, Strategy & Leadership asked Rob Purdie, Agile Practice Lead for the IBM Design Lab, how Agile software development methods were contributing to the success of IBM's key digital marketing initiatives. Findings – The traditional approach to software development is to define, design, develop and test everything – before delivering anything. With Agile, managers can reduce waste by prioritizing features based on relative business value, evaluating and re-designing as the project proceeds. Practical implications – Agile requires leaders and teams to work and learn through problems, designs and options in an open and transparent environment. It places new demands on technical leaders in terms of negotiation and planning skills. Originality/value – Managers outside the software industry should note that Agile/Scrum is likely to be increasingly essential to the future of product development and manufacturing. Nowadays many products for consumers and businesses include embedded software systems, so developing products in the future will require deeper collaboration across multiple engineering disciplines and marketing teams and familiarity with the Agile approach.

scholarly journals Involving Collection Staff in the DINA Software Development – An Agile Approach

2018 ◽  
Vol 2 ◽  
pp. e25580
Author(s):  
Markus Englund ◽  
Mikko Heikkinen ◽  
Lisa Sundström
Keyword(s):  
Software Development ◽  
Management System ◽  
Current System ◽  
Agile Software Development ◽  
Structured Data ◽  
Data Migration ◽  
Collection Management ◽  
Collection Management System ◽  
Agile Approach ◽  
Agile Software

In order to ensure long-term commitment to the DINA project (“DIgital information system for NAtural history data”, https://dina-project.net), it is essential to continuously deliver features of high value to the user community. This is also what agile software development methods try to achieve by emphasizing early delivery, rapid response to changes and close collaboration with users (see for example the Manifesto for Agile Software Development at http://agilemanifesto.org). We will give a brief overview on how current development of the DINA collection management system core is guided by agile principles. The mammal collection at the Swedish Museum of Natural History will be used as an example. Developing a cross-disciplinary collection management system is a complex task that poses many challenges: Which features should we focus on? What kinds of data should the system ultimately support? How can the system be flexible but still easy to use? Since we cannot do everything at once, we work towards a minimum viable product (MVP) that contains just enough features at a time to bring value for selected target users. In the mammal collection case, the MVP is the simplest product that is able to replace the functions of the current system used for managing the collection. As we begin to work with other collections, new MVPs are defined and used to guide further development. Thus, the set of features available will increase with each MVP, benefiting both new and current users. Another big challenge is migration of legacy data, which is labor intensive and involves standardizing data that are not compatible with the new system. To address these issues, we aim to build a flexible data model that allows less structured data to coexist with more complex, highly structured data. Migration should thus not require extensive data standardization, transformation and cleaning. The plan is to instead offer tools for transforming and cleaning the data after they have been imported. With the data in place, it will be easier for the user to provide feedback and suggest new features.

Systematic literature review – improving business processes by implementing agile

2021 ◽  
Vol ahead-of-print (ahead-of-print) ◽  
Author(s):  
Anna Schmitt ◽  
Sabrina Hörner
Keyword(s):  
Literature Review ◽  
Software Development ◽  
Systematic Literature Review ◽  
Business Processes ◽  
Business Environment ◽  
Primary Sources ◽  
Content Type ◽  
Agile Practices ◽  
Development Processes ◽  
Agile Approach

PurposeNumerous approaches from the field of economics already exist for the improvement of business processes. In the field of software development, work has been done on improving development processes. For years, the focus here has been on agile approaches. Although various approaches for improving business processes exist, it is becoming increasingly difficult to adapt business processes to the fast-moving conditions of the market and the business environment. Agile approaches address this issue. Thus, not only software development processes, but also business processes should benefit from agile approaches.Design/methodology/approachTo this end, values and principles of the Agile Manifesto, agile methods such as Scrum, and various agile practices such as the Kanban board should be applied in business processes. This paper examines the work already done on this topic. With the help of a systematic literature review (SLR), literature studies dealing with the implementation of the agile approach in business processes are identified.FindingsThis paper presents, investigates and contrasts 12 primary sources dealing with agile and business processes and shows how they are different/ equal regarding three research questions.Originality/valueWe provide an overview of existing approaches handling the combination of agile and business processes to improve business processes.

Agile Software Development for Customizing ERPs

2010 ◽  
pp. 20-39 ◽  
Author(s):  
Rogério Atem de Carvalho ◽  
Prof. Björn Johansson ◽  
Rodrigo Soares Manhães
Keyword(s):  
Software Development ◽  
Great Part ◽  
Fast Response ◽  
The Other ◽  
Agile Methods ◽  
Complex Task ◽  
Agile Practices ◽  
Agile Approach ◽  
Agile Software ◽  
Business Requirements

Customization of ERP systems is a complex task, and great part of this complexity is directly related to requirements management. In this context, a well-known problem is the misfit between the ERP functionalities and the business requirements. This problem comprises communication bottlenecks and difficulties on responding to changes. The proposals for minimizing these misfits are mostly focused on traditional, heavyweight waterfall-like approaches for software development. On the other side, the last decade has witnessed the rise and growth of Agile methods, which have both close communication and fast response to changes among their main values. This chapter maps some of the main agile practices to ERP customization processes, using, where applicable, practices from a real-world ERP project. Moreover, some limitations on the agile approach to ERP customization are presented and discussed.

Swimming Upstream in Turbulent Waters

2017 ◽  
pp. 268-300
Author(s):  
Priyadarsini Kannan Krishnamachariar ◽  
Manish Gupta
Keyword(s):  
Software Development ◽  
Risk Identification ◽  
Experimental Project ◽  
Agile Approach ◽  
Audit Approach ◽  
It Audit

Agile approach is a pragmatic fashion of software development, wherein the requirements are flexible to the changing needs of the customers, fast paced markets and the iterations of software are implemented and delivered based on business priorities. A risky or experimental project where the project requirements are not clear/not defined well in advance, are the most suitable candidates for adopting agile approach, as agile enables us to work with calculated risks during development, aiming to reduce the risks. The value of any implementation is realized only if it delivers benefits to organization and users, which could be assured by effective auditing of the implementation by understanding the implications of agile approach and figuring out right audit techniques and processes. Many organizations already have well established audit functions and matured IT Audit procedures for auditing traditional SDLC waterfall processes. Yet the methods for auditing software development based on agile approach requires a different attitude and audit techniques that goes well with the proactive nature of agile approach. This paper aims to present risk based audit approach on the agile implementation of software development, how risk identification and assessment can be merged along with the phases of software development and the ways by which agile techniques can be effectively utilized as tools for audit.

Sign in / Sign up

Export Citation Format

Share Document