{"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}
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.