检索结果-内蒙古大学图书馆

Modelling the enablers of productivity of enterprise-level agile software development process using modified TISM approach

引用

JOURNAL OF MODELLING IN MANAGEMENT 2024年第6期19卷 1749-1772页

作者： Sathe, Chaitanya Arun Panse, Chetan Symbiosis Inst Business Management SIBM Pune India Symbiosis Int Deemed Univ Pune India

PurposeThis study aims to examine the enablers of productivity of enterprise-level agile development process using modified total interpretative structural modeling (TISM). The two main objectives of the current study are to determine the variables influencing enterprise-level agile development productivity and to develop modified TISM for the corresponding ***/methodology/approachTo identify enablers of the productivity of enterprise-level agile software development process a literature review and opinions of domain experts were collected. A hierarchical relationship among variables that show direct and indirect influence is created using the modified TISM (M-TISM) technique with Cross Impact Matrix-Multiplication Applied to Classification analysis. This study examined and analyzed the relationships between the determinants within the enterprise using a M-TISM *** the literature review, the study could identify ten enabling factors of the productivity of agile development process at the enterprise level. Results depict that program increment (PI) planning and scalable backlog management, continuous integration and continuous delivery (CI/CD), agile release trains (ART), agile work culture, delivery excellence, lean and DevOps practices, value stream mapping (VMS), team skills and expertise, collaborative culture, agile coaching, customer engagement have an impact on the productivity of enterprise-level agile development process. The results show that team collaboration, agile ways of working and customer engagement have a greater impact on productivity improvement for enterprise-level agile development *** limitations/implicationsThe developed model is useful for organizations employing scaled agile development processes in software development. This study provides a recommended listing of key enablers, that may enable productivity improvements in the agile development process at the enterprise level. Strategists should

关键词： agile software development Enterprise-level agile Total interpretative structural modeling (TISM) Enterprise-level productivity

来源：评论

学校读者我要写书评

暂无评论

An Automated Ontology-Based Requirements Traceability Technique in agile software development Context 35th

An Automated Ontology-Based Requirements Traceability Techni...

引用

35th International Conference on Database and Expert Systems Applications (DEXA)

作者： Khan, Saif Ur Rehman Aslam, Uswa Mashkoor, Atif Inayat, Irum Nisa, Habib Un Shifa Tameer E Millat Univ STMU Dept Software Engn Islamabad Pakistan Super Univ Dept Comp Sci Lahore Pakistan Johannes Kepler Univ JKU Inst Software Syst Engn Linz Austria Natl Univ Comp & Emerging Sci FAST NUCES Dept Software Engn Islamabad Pakistan

ISBN: (纸本)9783031683015;9783031683022

agile software development (ASD) is a popular process in the software development industry due to its dynamic nature and ability to release software quickly. However, managing the requirements in the ASD context remains a challenging task. This is because frequent changes need to be accommodated in the iterations. Consequently. It is challenging to effectively handle the changes and trace the requirements among artifacts such as sub-user stories, tasks, models, code snippets, and test cases. On the other hand, semi-automated tool support and organizational issues further complicate the requirement management process. Motivated by this, we propose an automated ontology-based technique to address the above-mentioned challenges, which benefits requirements management in agile development. The proposed technique involves tracing requirements, ensuring ontology consistency using competency questions, prioritizing user stories based on business value, and estimating the effort required for each user story. We empirically assessed the performance of the proposed technique by comparing it with baseline approaches using IEEE standards. The attained results indicate that the proposed technique significantly outperforms the baseline approaches. We believe that the proposed technique provides a cost-effective solution for requirement traceability in ASD.

关键词： software Requirement Management Requirement Traceability Ontology agile software development

来源：评论

学校读者我要写书评

暂无评论

What You Use is What You Get: Unforced Errors in Studying Cultural Aspects in agile software development 24

What You Use is What You Get: Unforced Errors in Studying Cu...

引用

28th International Conference on Evaluation and Assessment in software Engineering (EASE)

作者： Neumann, Michael Schmid, Klaus Baumann, Lars Hsch Hannover Hannover Germany Univ Hildesheim Hildesheim Germany

ISBN: (纸本)9798400717017

Context: Cultural aspects are of high importance as they guide people's behaviour and thus, influence how people apply methods and act in projects. In recent years, software engineering research emphasized the need to analyze the challenges of specific cultural characteristics. Investigating the influence of cultural characteristics is challenging due to the multi-faceted concept of culture. People's behaviour, their beliefs and underlying values are shaped by different layers of culture, e.g., regions, organizations, or groups. In this study, we focus on agile methods, which are agile approaches that focus on underlying values, collaboration and communication. Thus, cultural and social aspects are of high importance for their successful use in practice. Objective: In this paper, we address challenges that arise when using the model of cultural dimensions by Hofstede to characterize specific cultural values. This model is often used when discussing cultural influences in software engineering. Method: As a basis, we conducted an exploratory, multiple case study, consisting of two cases in Japan and two in Germany. Contributions: In this study, we observed that cultural characteristics of the participants differed significantly from cultural characteristics that would typically be expected for people from the respective country. This drives our conclusion that for studies in empirical software engineering that address cultural factors, a case-specific analysis of the characteristics is needed.

关键词： Culture cultural influence empirical software engineering agile software development case study

来源：评论

学校读者我要写书评

暂无评论

The Current State of Operationalizing Value by Dutch Product Owners in agile software development 25th

The Current State of Operationalizing Value by Dutch Product...

引用

25th International Conference on agile software development (XP)

作者： van Daalen, Erik van Solingen, Rini KWD Resultaatmanagement Edisonbaan 15 NL-3439 MN Nieuwegein Netherlands Delft Univ Technol Mourik Broekmanweg 6 NL-2628 XE Delft Netherlands

ISBN: (纸本)9783031611537;9783031611544

agile software development (ASD) teams show their relevance through the continuous delivery of valuable software. As part of ASD, product owners have an important role in four activities: determining most valuable backlog items, refining them, and in validating and measuring business value. In this research we investigate how product owners operationalize business value delivery in these activities. We conducted 38 semi-structured in-depth interviews with product owners in the Netherlands. Overall we found that 55% operationalize value using only two of the four activities, and that 11% apply all four activities. We furthermore found that only 26.5% of these product owners use a structured prioritization method, 47% prioritize based on individual preferences and gut feeling, and 26.5% do not use any prioritization approach at all. We found five different approaches to refinement. The majority (84%) of the product owners state that they validate business value delivery, while just 24% actually measure business value. Overall we conclude that there are opportunities to bring product ownership to a higher level on operationalizing business value delivery, and that there is a clear need in practice for better structure and guidance in operationalizing business value delivery to do so.

关键词： Operationalizing business value delivery prioritization product backlog agile software development refining business value validating business value measuring business value product owner (PO) agile practices

来源：评论

学校读者我要写书评

暂无评论

How to Measure Performance in agile software development? A Mixed-Method Study 50

How to Measure Performance in Agile Software Development? A ...

引用

50th Euromicro Conference on software Engineering and Advanced Applications

作者： Pham, Kevin Phong Neumann, Michael Univ Appl Sci FHDW Hannover Hannover Germany Univ Appl Sci & Arts Hannover Dpt Business Informat Syst Hannover Germany

ISBN: (纸本)9798350380279;9798350380262

Context: software process improvement (SPI) is known as a key for being successful in software development. Measuring quality and performance is of high importance in agile software development as agile approaches focussing strongly on short-term success in dynamic markets. Even if software engineering research emphasizes the importance of performance metrics while using agile methods, the literature lacks on detail how to apply such metrics in practice and what challenges may occur while using them. Objective: The core objective of our study is to identify challenges that arise when using agile software development performance metrics in practice and how we can improve their successful application. Method: We decided to design a mixed-method study. First, we performed a rapid literature review to provide an up-to-date overview of used performance metrics. Second, we conducted a single case study using a focus group approach and qualitative data collection and analysis in a real-world setting. Results: Our results show that while widely used performance metrics such as story points and burn down charts are widely used in practice, agile software development teams face challenges due to a lack of transparency and standardization as well as insufficient accuracy. Contributions: Based on our findings, we present a repository of widely used performance metrics for agile software development. Furthermore, we present implications for practitioners and researchers especially how to deal with challenges agile software development face while applying such metrics in practice.

关键词： agile methods agile software development performance metrics process improvement

来源：评论

学校读者我要写书评

暂无评论

Towards Optimal Non-functional Requirements Elicitation and Documentation in agile software development: A Case Study 29th

Towards Optimal Non-functional Requirements Elicitation and ...

引用

29th Argentine Congress of Computer Science on Computer Science (CACIC)

作者： Romera, Lourdes Gonzalez, Jeremias Lezcano, Andrea Carruthers, Juan A. Irrazabal, Emanuel Software Qual Res Grp FaCENA UNNE Corrientes Argentina

ISBN: (纸本)9783031622441;9783031622458

In agile software development, non-functional requirements are often underspecified and improperly handled due to the focus on rapidly delivering functionality. Neglecting NFRs in early phases of development may compromise software quality and customer satisfaction. In our previous paper, we introduced a guideline for handling non-functional requirements in agile. This guideline was evaluated in a case study, revealing that improved identification of non-functional requirements led to enhanced development stability and client communication, without losing agility in the process. In this paper, we propose an extension of the guideline aimed at improving the documentation of each stage and incorporating a NFR testing phase.

关键词： non-functional requirements agile software development system stories

来源：评论

学校读者我要写书评

暂无评论

The use of prototypes as a tool in agile software development 24

The use of prototypes as a tool in Agile software developmen...

引用

39th Annual ACM Symposium on Applied Computing (SAC)

作者： Larrea, Vivian Silveira, Milene Selbach da Silva, Tiago Silva Pontif Cathol Univ Rio Grande do Sul PUCRS Porto Alegre RS Brazil Fed Univ Sao Paulo UNIFESP Sao Jose Dos Campos SP Brazil

ISBN: (纸本)9798400702433

The artifacts involved in agile software development are of great importance. One of their main goals is to support the teams in understanding the final product or project and facilitate communication between the development, design team, and end-user. Among these artifacts, prototypes stand out. This work seeks to analyze and understand how prototypes can help the team and what benefits their use can bring to the development process in agile contexts. To do so, we conducted a triangulation between a systematic literature mapping and a study in the industry through semi-structured interviews. Based on the data collected, we were able to list best practices that can be adopted by agile teams, which are related to, for instance, the alignment between written documentation and prototypes, when to create prototypes, the team's involvement in its construction;and the adequacy of the different types of prototypes. agile teams can adopt the proposed practices regarding the use of prototypes to become more efficient and assertive, considering the characteristics of each agile development team.

关键词： agile software development software development teams use of prototypes

来源：评论

学校读者我要写书评

暂无评论

Hybrid Work meets agile software development: A Systematic Mapping Study 17

Hybrid Work meets Agile Software Development: A Systematic M...

引用

17th IEEE/ACM International Conference on Cooperative and Human Aspects of software Engineering (CHASE)

作者： Khanna, Dron Christensen, Emily Laue Gosu, Saagarika Wang, Xiaofeng Paasivaara, Maria Free Univ Bozen Bolzano Bolzano Italy Lappeenranta Lahti Univ Technol Lahti Finland

ISBN: (纸本)9798400705335

Hybrid work, a fusion of different work environments that allow employees to work in and outside their offices, represents a new frontier for agile researchers to explore. However, due to the nascent nature of the research phenomena, we are yet to achieve a good understanding of the research terrain formulated when hybrid work meets agile software development. This systematic mapping study, we aimed to provide a good understanding of this emerging research area. The systematic process we followed led to a collection of 12 primary studies, which is less than what we expected. All the papers are empirical studies, with most of them employing case studies as the research methodology. The people-centric nature of agile methods is yet to be adequately reflected in the studies in this area. Similarly, there is a lack of a richer understanding of hybrid work in terms of flexible work arrangements. Our mapping study identified various research opportunities that can be explored in future research.

关键词： Hybrid work agile software development Flexible working Remote working Work-From-Home

来源：评论

学校读者我要写书评

暂无评论

Technical Debt Management in agile software development: A Systematic Mapping Study 24

Technical Debt Management in Agile Software Development: A S...

引用

23rd Brazilian Symposium on software Quality

作者： Leite, Gilberto de Sousa Porto Vieira, Ricardo Eugenio Cerqueira, Lidiany Pitangueira Maciel, Rita Suzana Freire, Savio Mendonca, Manoel Univ Fed Bahia Salvador BA Brazil Univ Fed Sergipe Lagarto Sergipe Brazil Fed Inst Ceara Morada Nova Ceara Brazil

ISBN: (纸本)9798400717772

Context: agile methodologies use continuous delivery and adaptability to develop software that meets the needs of its users. However, such methods are prone to accumulate technical debt (TD). agile teams must balance the benefits and risks of incurring debt by managing TD items. Knowing how TD management is conducted in agile software teams can help agile practitioners increase their ability to handle TD items. Aims: To investigate, based on the state of the art, how agile software teams have managed existing TD items in their projects. Method: We carried out a systematic mapping study covering 39 articles from 2010 to 2023. Results: Among the agile methodologies, Scrum was the most used for TD management. Regarding practices, agile teams employ mostly user stories and sprint backlogs to identify TD items. Sprints and sprint backlogs are used to monitor debt, while refactoring is applied to prevent and repay TD items. Conclusion: This study maps current knowledge on TD management in agile methodologies, serving as a starting point for new investigations in the area.

关键词： Technical debt Technical debt management agile software development Systematic mapping study

来源：评论

学校读者我要写书评

暂无评论

Investigating Communities of Practice in Large-Scale agile software development: An Interview Study 25th

Investigating Communities of Practice in Large-Scale Agile S...

引用

25th International Conference on agile software development (XP)

作者： Tobisch, Franziska Schmidt, Johannes Matthes, Florian Tech Univ Munich TUM Sch Computat Informat & Technol Dept Comp Sci Munich Germany

ISBN: (纸本)9783031611537;9783031611544

Nowadays, responsiveness is essential to be competitive, particularly in software development. Traditional methods face limitations in meeting this demand for agility, which led to the rise of agile practices. Inspired by their success in small projects, organizations have begun to use agile methods in larger contexts. However, scaling agile practices introduces complexities and requires coordinating teams, managing dependencies, and collaboration. Communities of Practices (CoPs) are argued to address these issues and support organizations in adopting agile methods at scale. Still, empirical insights into the establishment of CoPs in scaled agile settings are limited. This study fills this gap by conducting expert interviews, exploring why organizations applying agile methods at scale adopt CoPs, and examining their characteristics. Our key findings include that, next to benefit from known advantages of CoPs, like knowledge sharing, organizations establish them to foster empowerment, strengthen alignment, and drive their agile transformation. Moreover, CoPs focus not only on agile but also on classical themes such as architecture. Communities are not necessarily established bottom-up but are often initiated by management, e.g., to empower employees. In general, CoPs are accepted by management and play an essential role in decision-making.

关键词： agile software development Large-scale agile Communities of Practice

来源：评论

学校读者我要写书评

暂无评论

建议与咨询留下您的常用邮箱和电话号码，以便我们向您反馈解决方案和替代方法

时间限定

文献类型

馆藏选择

核心期刊

语言

文献类型

帮助

文字说明：

检索规则说明：

检索范例：

分类表

所选分类

限定检索结果

文献类型

馆藏范围

日期分布

学科分类号

主题

机构

作者

语言

请选择保存的检索档案：

请选择收藏分类：

通借通还

建议与咨询 留下您的常用邮箱和电话号码，以便我们向您反馈解决方案和替代方法

时间限定

文献类型

馆藏选择

核心期刊

语言

文献类型

帮助

文字说明：

检索规则说明：

检索范例：

分类表

所选分类

限定检索结果

文献类型

馆藏范围

日期分布

学科分类号

主题

机构

作者

语言

请选择保存的检索档案： 新增检索档案 确定 取消

请选择收藏分类： 新增自定义分类 确定 取消

通借通还

建议与咨询留下您的常用邮箱和电话号码，以便我们向您反馈解决方案和替代方法

请选择保存的检索档案：

请选择收藏分类：