企业架构在分布式敏捷软件开发中的贡献

IF 1.6 3区工程技术 Q4 ENGINEERING, INDUSTRIAL

Systems Engineering Pub Date : 2023-12-12 DOI:10.1002/sys.21739

Y. Alzoubi, Alok Mishra

{"title":"企业架构在分布式敏捷软件开发中的贡献","authors":"Y. Alzoubi, Alok Mishra","doi":"10.1002/sys.21739","DOIUrl":null,"url":null,"abstract":"Geographically distributed agile development may experience a high failure rate due to communication issues, which has a negative influence on project performance. One suggested solution in the literature is to enhance both communication and project performance by implementing agile enterprise architecture. However, the empirical evidence that supports this claim is still scarce. To address this gap, this study empirically explores the role of agile enterprise architecture as an artifact in distributed agile development. The findings of an in‐depth qualitative case study from a dispersed agile development organization that involves teams distributed over three locations are used in this work. Over 2 months, data was gathered by interviewing 12 key members of the team and watching three Sprint sessions of agile software development. Text analysis qualitative approach was used to analyze the data. The findings imply that agile enterprise architecture has a positive effect on distributed agile software development communication, quality, and functionality. Agile enterprise architecture may also support on‐time completion, but a trade‐off with on‐budget may be necessary. These findings provide valuable insights, frameworks, and best practices that support organizations in achieving greater agility, collaboration, and success in their distributed software development initiatives. As this is one of the first studies to look at the influence of agile enterprise architecture on distributed agile software development communication and performance, further research is needed to confirm and expand on the conclusions of this study.","PeriodicalId":54439,"journal":{"name":"Systems Engineering","volume":"74 6","pages":""},"PeriodicalIF":1.6000,"publicationDate":"2023-12-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Enterprise architecture contribution in distributed agile software development\",\"authors\":\"Y. Alzoubi, Alok Mishra\",\"doi\":\"10.1002/sys.21739\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Geographically distributed agile development may experience a high failure rate due to communication issues, which has a negative influence on project performance. One suggested solution in the literature is to enhance both communication and project performance by implementing agile enterprise architecture. However, the empirical evidence that supports this claim is still scarce. To address this gap, this study empirically explores the role of agile enterprise architecture as an artifact in distributed agile development. The findings of an in‐depth qualitative case study from a dispersed agile development organization that involves teams distributed over three locations are used in this work. Over 2 months, data was gathered by interviewing 12 key members of the team and watching three Sprint sessions of agile software development. Text analysis qualitative approach was used to analyze the data. The findings imply that agile enterprise architecture has a positive effect on distributed agile software development communication, quality, and functionality. Agile enterprise architecture may also support on‐time completion, but a trade‐off with on‐budget may be necessary. These findings provide valuable insights, frameworks, and best practices that support organizations in achieving greater agility, collaboration, and success in their distributed software development initiatives. As this is one of the first studies to look at the influence of agile enterprise architecture on distributed agile software development communication and performance, further research is needed to confirm and expand on the conclusions of this study.\",\"PeriodicalId\":54439,\"journal\":{\"name\":\"Systems Engineering\",\"volume\":\"74 6\",\"pages\":\"\"},\"PeriodicalIF\":1.6000,\"publicationDate\":\"2023-12-12\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Systems Engineering\",\"FirstCategoryId\":\"5\",\"ListUrlMain\":\"https://doi.org/10.1002/sys.21739\",\"RegionNum\":3,\"RegionCategory\":\"工程技术\",\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"Q4\",\"JCRName\":\"ENGINEERING, INDUSTRIAL\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Systems Engineering","FirstCategoryId":"5","ListUrlMain":"https://doi.org/10.1002/sys.21739","RegionNum":3,"RegionCategory":"工程技术","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q4","JCRName":"ENGINEERING, INDUSTRIAL","Score":null,"Total":0}

引用次数: 0

摘要

由于沟通问题，地理分布广泛的敏捷开发可能会经历较高的失败率，从而对项目绩效产生负面影响。文献中提出的一种解决方案是通过实施敏捷企业架构来加强沟通和提高项目绩效。然而，支持这一观点的实证证据仍然很少。为了弥补这一不足，本研究通过实证研究探讨了敏捷企业架构作为分布式敏捷开发中的一种工具所发挥的作用。本研究采用了一项深入的定性案例研究的结果，该案例研究来自一个分散的敏捷开发组织，其团队分布在三个地方。在两个多月的时间里，通过采访团队的 12 名关键成员和观看三次敏捷软件开发的 Sprint 会议收集了数据。数据分析采用文本分析定性方法。研究结果表明，敏捷企业架构对分布式敏捷软件开发的沟通、质量和功能有积极影响。敏捷企业架构还可以支持按时完成项目，但可能需要与按预算完成项目进行权衡。这些发现提供了有价值的见解、框架和最佳实践，可帮助企业在其分布式软件开发项目中实现更高的敏捷性、协作性和成功率。由于这是首次研究敏捷企业架构对分布式敏捷软件开发沟通和绩效的影响，因此需要进一步的研究来确认和扩展本研究的结论。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

查看原文本刊更多论文

Enterprise architecture contribution in distributed agile software development

Geographically distributed agile development may experience a high failure rate due to communication issues, which has a negative influence on project performance. One suggested solution in the literature is to enhance both communication and project performance by implementing agile enterprise architecture. However, the empirical evidence that supports this claim is still scarce. To address this gap, this study empirically explores the role of agile enterprise architecture as an artifact in distributed agile development. The findings of an in‐depth qualitative case study from a dispersed agile development organization that involves teams distributed over three locations are used in this work. Over 2 months, data was gathered by interviewing 12 key members of the team and watching three Sprint sessions of agile software development. Text analysis qualitative approach was used to analyze the data. The findings imply that agile enterprise architecture has a positive effect on distributed agile software development communication, quality, and functionality. Agile enterprise architecture may also support on‐time completion, but a trade‐off with on‐budget may be necessary. These findings provide valuable insights, frameworks, and best practices that support organizations in achieving greater agility, collaboration, and success in their distributed software development initiatives. As this is one of the first studies to look at the influence of agile enterprise architecture on distributed agile software development communication and performance, further research is needed to confirm and expand on the conclusions of this study.

求助全文

通过发布文献求助，成功后即可免费获取论文全文。去求助

来源期刊

Systems Engineering 工程技术-工程：工业

CiteScore

5.10

自引率

20.00%

发文量

审稿时长

6 months

期刊介绍： Systems Engineering is a discipline whose responsibility it is to create and operate technologically enabled systems that satisfy stakeholder needs throughout their life cycle. Systems engineers reduce ambiguity by clearly defining stakeholder needs and customer requirements, they focus creativity by developing a system’s architecture and design and they manage the system’s complexity over time. Considerations taken into account by systems engineers include, among others, quality, cost and schedule, risk and opportunity under uncertainty, manufacturing and realization, performance and safety during operations, training and support, as well as disposal and recycling at the end of life. The journal welcomes original submissions in the field of Systems Engineering as defined above, but also encourages contributions that take an even broader perspective including the design and operation of systems-of-systems, the application of Systems Engineering to enterprises and complex socio-technical systems, the identification, selection and development of systems engineers as well as the evolution of systems and systems-of-systems over their entire lifecycle. Systems Engineering integrates all the disciplines and specialty groups into a coordinated team effort forming a structured development process that proceeds from concept to realization to operation. Increasingly important topics in Systems Engineering include the role of executable languages and models of systems, the concurrent use of physical and virtual prototyping, as well as the deployment of agile processes. Systems Engineering considers both the business and the technical needs of all stakeholders with the goal of providing a quality product that meets the user needs. Systems Engineering may be applied not only to products and services in the private sector but also to public infrastructures and socio-technical systems whose precise boundaries are often challenging to define.