精益作为Scrum故障排除器

C. Jakobsen, Tom Poppendieck
{"title":"精益作为Scrum故障排除器","authors":"C. Jakobsen, Tom Poppendieck","doi":"10.1109/AGILE.2011.11","DOIUrl":null,"url":null,"abstract":"Systematic works at CMMI level 5 and uses Lean Software Development as a driver for optimizing software processes. Many of the optimizations described in this paper are the result of using A3 problem solving. What makes the Systematic experience unique, is the larger focus of the problem solving effort, at an organizational level, in which individual projects are used as experiments to try out countermeasures to address root causes. This is possible because Systematic, based on a CMMI focus, already employs a level of standard work across project and product engagements so that we can apply learning from an experiment on one project to future projects. Experience from the past five years has resulted in significant improvements to our processes including our Scrum implementation, and has revealed insight into five key measures to monitor projects. The experiences also show important lessons learned on how to combine team retrospective learning with organizational learning.","PeriodicalId":133654,"journal":{"name":"2011 AGILE Conference","volume":"15 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2011-08-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"18","resultStr":"{\"title\":\"Lean as a Scrum Troubleshooter\",\"authors\":\"C. Jakobsen, Tom Poppendieck\",\"doi\":\"10.1109/AGILE.2011.11\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Systematic works at CMMI level 5 and uses Lean Software Development as a driver for optimizing software processes. Many of the optimizations described in this paper are the result of using A3 problem solving. What makes the Systematic experience unique, is the larger focus of the problem solving effort, at an organizational level, in which individual projects are used as experiments to try out countermeasures to address root causes. This is possible because Systematic, based on a CMMI focus, already employs a level of standard work across project and product engagements so that we can apply learning from an experiment on one project to future projects. Experience from the past five years has resulted in significant improvements to our processes including our Scrum implementation, and has revealed insight into five key measures to monitor projects. The experiences also show important lessons learned on how to combine team retrospective learning with organizational learning.\",\"PeriodicalId\":133654,\"journal\":{\"name\":\"2011 AGILE Conference\",\"volume\":\"15 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2011-08-07\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"18\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2011 AGILE Conference\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/AGILE.2011.11\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2011 AGILE Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AGILE.2011.11","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 18

摘要

系统化工作在CMMI 5级,并使用精益软件开发作为优化软件过程的驱动。本文中描述的许多优化都是使用A3问题解决的结果。系统经验的独特之处在于,在组织层面上,更大的焦点是解决问题的努力,其中单个项目被用作实验,以尝试解决根本原因的对策。这是可能的,因为基于CMMI焦点的Systematic已经在项目和产品约定中采用了一定水平的标准工作,因此我们可以将从一个项目的实验中学习到的知识应用到未来的项目中。过去五年的经验使我们的流程得到了重大改进,包括我们的Scrum实施,并揭示了监控项目的五个关键措施。这些经验也显示了如何将团队回顾学习与组织学习相结合的重要经验教训。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
Lean as a Scrum Troubleshooter
Systematic works at CMMI level 5 and uses Lean Software Development as a driver for optimizing software processes. Many of the optimizations described in this paper are the result of using A3 problem solving. What makes the Systematic experience unique, is the larger focus of the problem solving effort, at an organizational level, in which individual projects are used as experiments to try out countermeasures to address root causes. This is possible because Systematic, based on a CMMI focus, already employs a level of standard work across project and product engagements so that we can apply learning from an experiment on one project to future projects. Experience from the past five years has resulted in significant improvements to our processes including our Scrum implementation, and has revealed insight into five key measures to monitor projects. The experiences also show important lessons learned on how to combine team retrospective learning with organizational learning.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信