{"title":"垂直切片:越小越好","authors":"I. Ratner, Jack Harvey","doi":"10.1109/AGILE.2011.46","DOIUrl":null,"url":null,"abstract":"The technique of vertical slicing was introduced as a mechanism to combat our agile software development teams developing tendency toward building software in horizontal layers, building one service at a time, or grouping stories then breaking them down into layers. Those practices resulted in sprint reviews where no functionality could be demonstrated to the users and several iterations before all of the pieces were working together with useful functionality to show to users. Those habits continued when the next wave of projects with user interfaces came along. In this paper, we highlight the stories of four of our agile teams who tried vertical slicing, the challenges they faced, the victories, and the lessons learned.","PeriodicalId":133654,"journal":{"name":"2011 AGILE Conference","volume":"38 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2011-08-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"6","resultStr":"{\"title\":\"Vertical Slicing: Smaller is Better\",\"authors\":\"I. Ratner, Jack Harvey\",\"doi\":\"10.1109/AGILE.2011.46\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The technique of vertical slicing was introduced as a mechanism to combat our agile software development teams developing tendency toward building software in horizontal layers, building one service at a time, or grouping stories then breaking them down into layers. Those practices resulted in sprint reviews where no functionality could be demonstrated to the users and several iterations before all of the pieces were working together with useful functionality to show to users. Those habits continued when the next wave of projects with user interfaces came along. In this paper, we highlight the stories of four of our agile teams who tried vertical slicing, the challenges they faced, the victories, and the lessons learned.\",\"PeriodicalId\":133654,\"journal\":{\"name\":\"2011 AGILE Conference\",\"volume\":\"38 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2011-08-07\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"6\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2011 AGILE Conference\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/AGILE.2011.46\",\"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.46","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The technique of vertical slicing was introduced as a mechanism to combat our agile software development teams developing tendency toward building software in horizontal layers, building one service at a time, or grouping stories then breaking them down into layers. Those practices resulted in sprint reviews where no functionality could be demonstrated to the users and several iterations before all of the pieces were working together with useful functionality to show to users. Those habits continued when the next wave of projects with user interfaces came along. In this paper, we highlight the stories of four of our agile teams who tried vertical slicing, the challenges they faced, the victories, and the lessons learned.