Knowledge repository to improve agile development processes learning

IET Software ◽  
2010 ◽  
Vol 4 (6) ◽  
pp. 434 ◽  
Author(s):  
A. Amescua ◽  
L. Bermón ◽  
J. García ◽  
M.-I. Sánchez-Segura
Keyword(s):  
Agile Development ◽  
Knowledge Repository ◽  
Development Processes

Measuring Software Development Project Performance

2019 ◽  
pp. 315-345
Author(s):  
Nihan Yildirim ◽  
Semih Ersöz ◽  
Bilal Altun
Keyword(s):  
Data Collection ◽  
Software Development ◽  
Measurement Model ◽  
Development Project ◽  
Agile Development ◽  
High Tech ◽  
Software Development Project ◽  
Software Companies ◽  
Expert Opinions ◽  
Development Processes

Adopting agile methodologies to software development processes helps software companies to sustain their growth through efficiency for long term. In the digital transformation era, Industry 4.0 as part of High-Tech Strategy 2020 for Germany involves agile principles and brings the latest technological trends in production process. The purpose of this chapter is to design a proper agile project management performance measurement model for start-up software companies. First, all key performance indicators related to agile development in the literature have been listed. Then KPIs that are provided from literature review with content analysis have been reviewed and categorized by expert opinions that were collected through in-depth interviews. Seven strategic KPIs and their data collection systems are defined and designed. Lastly, process and data collection improvements are recommended in order to sustain agile development measurement model.

scholarly journals ReSySTER: A hybrid recommender system for Scrum team roles based on fuzzy and rough sets

2012 ◽  
Vol 22 (4) ◽  
pp. 801-816 ◽  
Author(s):  
Ricardo Colomo-Palacios ◽  
Israel González-Carrasco ◽  
José Luis López-Cuadrado ◽  
Ángel García-Crespo
Keyword(s):  
Software Development ◽  
Recommender System ◽  
Rough Set Theory ◽  
Project Managers ◽  
Agile Development ◽  
Project Leader ◽  
Development Processes ◽  
Hybrid Recommender System ◽  
Real Scenario ◽  
Hybrid Recommender

Agile development is a crucial issue within software engineering because one of the goals of any project leader is to increase the speed and flexibility in the development of new commercial products. In this sense, project managers must find the best resource configuration for each of the work packages necessary for the management of software development processes in order to keep the team motivated and committed to the project and to improve productivity and quality. This paper presents ReSySTER, a hybrid recommender system based on fuzzy logic, rough set theory and semantic technologies, aimed at helping project leaders to manage software development projects. The proposed system provides a powerful tool for project managers supporting the development process in Scrum environments and helping to form the most suitable team for different work packages. The system has been evaluated in a real scenario of development with the Scrum framework obtaining promising results.

Case Study of Agile Security Engineering

2017 ◽  
Vol 8 (1) ◽  
pp. 43-57 ◽  
Author(s):  
Kalle Rindell ◽  
Sami Hyrynsalmi ◽  
Ville Leppänen
Keyword(s):  
Identity Management ◽  
Critical Role ◽  
Agile Development ◽  
Security Engineering ◽  
Development Processes ◽  
Identity Management System ◽  
Ict Service ◽  
Security Regulations ◽  
Development Methods

Security concerns are increasingly guiding both the design and processes of software-intensive product development. In certain environments, the development of the product requires special security arrangements for development processes, product release, maintenance and hosting, and specific security-oriented processes and governance. Integrating the security engineering processes into agile development methods can have the effect of mitigating the agile methods' intended benefits. This article describes a case of a large ICT service provider building a secure identity management system for a sizable government agency. The project was a subject to strict security regulations due to the end product's critical role. The project was a multi-team, multi-site, standard-regulated security engineering and development work executed following the Scrum framework. The study reports the difficulties in combining security engineering with agile development, provides propositions to enhance Scrum for security engineering activities. Also, an evaluation of the effects of the security work on project cost presented.

scholarly journals Traditionalisation of agile processes: Architectural aspects

2018 ◽  
Vol 15 (1) ◽  
pp. 79-109 ◽  
Author(s):  
Predrag Matkovic ◽  
Mirjana Maric ◽  
Pere Tumbas ◽  
Marton Sakal
Keyword(s):  
Mixed Method ◽  
Cost Reduction ◽  
Agile Development ◽  
Software Systems ◽  
Mixed Method Research ◽  
Agile Processes ◽  
Development Processes ◽  
Qualitative Component ◽  
Architecture Modeling ◽  
Sensitive Issues

Mechanisms of agile processes, suited for cost reduction and timely reaction to dynamic market changes, have also been recognized as useful in the development of complex software solutions. Recent studies focused on expansion of agile processes point to a viable possibility for coexistence and integration of complementary elements of agile and traditional development. Within the scope of this paper, this phenomenon is referred to as traditionalisation of agile processes. Software architecture modeling is one of the most sensitive issues associated with incorporation of elements of traditional development into agile processes. The goal of this paper was to determine how suitable particular explicit architectural practices are for incorporation into agile development processes. A mixed method research was carried out for this purpose. Qualitative component of the research resulted in identification of explicit architectural practices suitable for application in agile development processes. Their significances were determined by means of the quantitative component, realized in the form of an empirical research. The research confirmed that emergent architecture in agile processes is not sufficient for the development of complex software solutions, and that agile processes need to incorporate certain explicit architecture practices. Research results revealed that the agile community has an affirmative attitude towards the idea of incorporating explicit architectural practices into agile development processes, with overall agreement on the significances of particular explicit architectural practices for the development of architecture of complex software systems.

scholarly journals AWOSE - A Process Model for Incorporating Ethical Analyses in Agile Systems Engineering

2019 ◽  
Vol 26 (2) ◽  
pp. 851-870 ◽  
Author(s):  
Benjamin Strenge ◽  
Thomas Schack
Keyword(s):  
Systems Engineering ◽  
Process Model ◽  
Ethical Issues ◽  
System Development ◽  
Extreme Programming ◽  
Agile Development ◽  
Ethical Implications ◽  
Technological Developments ◽  
Information And Communication ◽  
Development Processes

Abstract Ethical, legal and social implications are widely regarded as important considerations with respect to technological developments. Agile Worth-Oriented Systems Engineering (AWOSE) is an innovative approach to incorporating ethically relevant criteria during agile development processes through a flexibly applicable methodology. First, a predefined model for the ethical evaluation of socio-technical systems is used to assess ethical issues according to different dimensions. The second part of AWOSE ensures that ethical issues are not only identified, but also systematically considered during the design of systems based on information and communication technology. For this purpose, the findings from the first step are integrated with approaches from worth-centered development into a process model that, unlike previous approaches to ethical system development, is thoroughly compatible with agile methodologies like Scrum or Extreme Programming. Artifacts of worth-centered development called Worth Maps have been improved to guide the prioritization of development tasks as well as choices among design alternatives with respect to ethical implications. Furthermore, the improved Worth Maps facilitate the identification of suitable criteria for system evaluations in association to ethical concerns and desired positive outcomes of system usage. The potential of the AWOSE methodology has been demonstrated in the context of a technical system (smart glasses for cognitive assistance) that supports elderly and people with particular handicaps.

An Agile Perspective on Open Source Software Engineering

2011 ◽  
pp. 141-153
Author(s):  
Sofiane Sahraoui
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Agile Development ◽  
Iterative Development ◽  
Planning And Design ◽  
Software Engineering Process ◽  
Development Processes ◽  
Agile Software

Open source software (OSS) development has been a trend parallel to that of agile software development, which is the highly iterative development model following conventional software engineering principles. Striking similarities exist between the two development processes as they seem to follow the same generic phases of software development. Both modes of development have less emphasis on planning and design and a more prominent role for implementation during the software engineering process. This chapter expounds on this connection by adopting an agile perspective on OSS development to emphasize the similarities and dissimilarities between the two models. An attempt is first made to show how OSS development fits into the generic agile development framework. Then, the chapter demonstrates how the development process of Mozilla and Apache as two of the most famous OSS projects can be recast within this framework. The similarity discussed and illustrated between agile and OSS development modes is rather limited to the mechanics of the development processes and do not include the philosophies and motivations behind development.

Agile Development Processes and Knowledge Documentation

2014 ◽  
pp. 309-328
Author(s):  
Eran Rubin ◽  
Hillel Rubin
Keyword(s):  
System Design ◽  
Support System ◽  
Domain Knowledge ◽  
System Development ◽  
Agile Development ◽  
Operational System ◽  
Agile Processes ◽  
Development Processes ◽  
The Relationship

Agile processes emphasize operational system code rather than its documentation. Ironically, however, some traditional documentation artefacts come to support system-stakeholders interaction, which is another core aspect of agile development processes. In this chapter, the authors examine the relationship between system development and knowledge documentation. They develop an approach that enables incorporating domain documentation to agile development while keeping the processes adaptive. The authors also provide a system design that actively uses domain knowledge documentation.

Sign in / Sign up

Export Citation Format

Share Document