{"title":"持续和协作验证:敏捷需求知识的实地研究","authors":"R. Gallardo-Valencia, S. Sim","doi":"10.1109/MARK.2009.3","DOIUrl":null,"url":null,"abstract":"We present the results of our field study that describe how requirements validation was performed at an industrial software company using agile software practices. As is common in agile processes, the team did not capture requirements knowledge in a comprehensive specification document. Instead, requirements knowledge was captured in user stories, automated acceptance tests, personal notes, and conversations. Validation was performed continuously, during preiteration, iteration planning, and intra iteration using mainly conversations. Validation was also collaborative and involved all team members, including the Product Owner, programmers, and testers. The results of our field study have implications for both agile and validation methods. This successful arrangement of agile practices is instructive for agile practitioners and for researchers studying validation.","PeriodicalId":143105,"journal":{"name":"2009 Second International Workshop on Managing Requirements Knowledge","volume":"38 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2009-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"13","resultStr":"{\"title\":\"Continuous and Collaborative Validation: A Field Study of Requirements Knowledge in Agile\",\"authors\":\"R. Gallardo-Valencia, S. Sim\",\"doi\":\"10.1109/MARK.2009.3\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"We present the results of our field study that describe how requirements validation was performed at an industrial software company using agile software practices. As is common in agile processes, the team did not capture requirements knowledge in a comprehensive specification document. Instead, requirements knowledge was captured in user stories, automated acceptance tests, personal notes, and conversations. Validation was performed continuously, during preiteration, iteration planning, and intra iteration using mainly conversations. Validation was also collaborative and involved all team members, including the Product Owner, programmers, and testers. The results of our field study have implications for both agile and validation methods. This successful arrangement of agile practices is instructive for agile practitioners and for researchers studying validation.\",\"PeriodicalId\":143105,\"journal\":{\"name\":\"2009 Second International Workshop on Managing Requirements Knowledge\",\"volume\":\"38 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2009-09-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"13\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2009 Second International Workshop on Managing Requirements Knowledge\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/MARK.2009.3\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2009 Second International Workshop on Managing Requirements Knowledge","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/MARK.2009.3","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Continuous and Collaborative Validation: A Field Study of Requirements Knowledge in Agile
We present the results of our field study that describe how requirements validation was performed at an industrial software company using agile software practices. As is common in agile processes, the team did not capture requirements knowledge in a comprehensive specification document. Instead, requirements knowledge was captured in user stories, automated acceptance tests, personal notes, and conversations. Validation was performed continuously, during preiteration, iteration planning, and intra iteration using mainly conversations. Validation was also collaborative and involved all team members, including the Product Owner, programmers, and testers. The results of our field study have implications for both agile and validation methods. This successful arrangement of agile practices is instructive for agile practitioners and for researchers studying validation.