Using ODC to diagnose an Agile enterprise application development project

R. Chillarege
{"title":"Using ODC to diagnose an Agile enterprise application development project","authors":"R. Chillarege","doi":"10.1109/ISSREW.2013.6688862","DOIUrl":null,"url":null,"abstract":"This paper presents a case study using Orthogonal Defect Classification (ODC) as a diagnostic tool to understand the quality and productivity issues in a Agile enterprise web development project. The project spanned a little over two years and had an effort in the range of 100,000 hours. The use of Agile was new to this engineering team. However, the senior people in the team had several years of experience with different process models. The project used a Scrum development model and ran three week Sprints. The objective of the ODC analysis was to understand the dynamics of the development as it actually occurred - as opposed to what was on paper or believed to have been implemented. We also wanted to understand the quality of the product produced, its stability and causes of customer pain. The development process had a separate Quality Assurance (QA) function, and a development led test and inspection effort. We wanted to understand their individual effectiveness, and how the structure effected production level quality. This case study was conducted by the senior engineering team along with ODC expertise from our firm. A subset of the application (around 4 major components) were chosen for this study. This allowed for an examination of component level issues, versus systemic issues across the entire application.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"10 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ISSREW.2013.6688862","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 1

Abstract

This paper presents a case study using Orthogonal Defect Classification (ODC) as a diagnostic tool to understand the quality and productivity issues in a Agile enterprise web development project. The project spanned a little over two years and had an effort in the range of 100,000 hours. The use of Agile was new to this engineering team. However, the senior people in the team had several years of experience with different process models. The project used a Scrum development model and ran three week Sprints. The objective of the ODC analysis was to understand the dynamics of the development as it actually occurred - as opposed to what was on paper or believed to have been implemented. We also wanted to understand the quality of the product produced, its stability and causes of customer pain. The development process had a separate Quality Assurance (QA) function, and a development led test and inspection effort. We wanted to understand their individual effectiveness, and how the structure effected production level quality. This case study was conducted by the senior engineering team along with ODC expertise from our firm. A subset of the application (around 4 major components) were chosen for this study. This allowed for an examination of component level issues, versus systemic issues across the entire application.
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
使用ODC诊断敏捷企业应用程序开发项目
本文介绍了一个案例研究,使用正交缺陷分类(ODC)作为诊断工具来理解敏捷企业web开发项目中的质量和生产力问题。该项目历时两年多一点,工作时间约为10万小时。对于这个工程团队来说,敏捷的使用是全新的。然而,团队中的高级人员有几年不同过程模型的经验。该项目使用了Scrum开发模型,并运行了为期三周的sprint。ODC分析的目标是了解实际发生的开发动态,而不是纸上空下或认为已经实现的开发动态。我们还想了解所生产产品的质量、稳定性和客户痛苦的原因。开发过程具有独立的质量保证(QA)功能,以及开发主导的测试和检查工作。我们想了解他们的个人效率,以及结构如何影响生产水平的质量。这个案例研究是由我们公司的高级工程团队和ODC专家共同完成的。应用程序的一个子集(大约4个主要组件)被选择用于本研究。这允许检查组件级别的问题,而不是整个应用程序中的系统问题。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
Bug localisation through diverse sources of information A chain of accountabilities in open systems based on assured entrustments Estimating response time distribution of server application in software aging phenomenon Safety assessment of software-intensive medical devices: Introducing a safety quality model approach Detection of missing requirements using base requirements pairs
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1