{"title":"Direct verbal communication as a catalyst of agile knowledge sharing","authors":"Grigori Melnik, F. Maurer","doi":"10.1109/ADEVC.2004.12","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.12","url":null,"abstract":"This paper discusses the role of conversation and social interactions as the key element of effective knowledge sharing in an agile process. It also presents the observations made during a repeated experiment on knowledge sharing conducted in various groups of professionals and students. The study suggests that the focus on the pure codified approach is the critical reason of Tayloristic team failure to effectively share knowledge among all stakeholders of a software project. Drawing on the knowledge-as-relationship perspective of knowledge sharing we theorize that verbal face-to-face interaction facilitates achieving higher velocity by software development teams.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122152021","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Taming the embedded tiger - agile test techniques for embedded software","authors":"Nancy Van Schooenderwoert, Ron Morsicato","doi":"10.1109/ADEVC.2004.21","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.21","url":null,"abstract":"Strong unit testing is the foundation of agile software development but embedded systems present special problems. Test of embedded software is bound up with test of hardware, crossing professional and organizational boundaries. Even with evolving hardware in the picture, agile methods work well provided you use multiple test strategies. This has powerful implications for improving the quality of high-reliability systems, which commonly have embedded software at their heart.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"230 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115006565","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"AntiPractices: AntiPatterns for XP practices","authors":"Yoshihito Kuranuki, Kenji Hiranabe","doi":"10.1109/ADEVC.2004.7","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.7","url":null,"abstract":"When you introduce extreme programming (XP) to your project, the team gets fresh energy and high efficiency. However, sustaining the good condition becomes difficult when you are attacked by its side effects. We call these XP side effects \"AntiPractices\", just as AntiPatterns come from Patterns. \"Turning all the knobs up to 10\" is the XP way, but AntiPractices show bad symptoms of the overdrive. In this experience report, we identify AntiPractices discovered from our projects. We add prescriptions so that XPers can share the countermeasures.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129510430","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"An initial exploration of the relationship between pair programming and Brooks' law","authors":"L. Williams, Anuja Shukla, A. Antón","doi":"10.1109/ADEVC.2004.6","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.6","url":null,"abstract":"Through his law, \"adding manpower to a late software project makes it later,'' Brooks asserts that the assimilation, training, and intercommunication costs of adding new team members outweigh the associated team productivity gain in the short term. Anecdotes suggest that adding manpower to a late project yields productivity gains to the team more quickly if the team employs the pair programming technique when compared to teams where new team members work alone. We utilize a system dynamics model which demonstrates support of these observations. Parameter values for the model were obtained via a small-scale, nonprobabilistic, convenience survey. Our initial findings suggest that managers should incorporate the pair programming practice when growing their team.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"84 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124136225","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The XP customer role in practice: three studies","authors":"Angela Martin, R. Biddle, J. Noble","doi":"10.1109/ADEVC.2004.23","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.23","url":null,"abstract":"The customer is the only nondeveloper role in extreme programming (XP). The customer's explicit responsibilities are to drive the project, providing project requirements (user stories) and quality control (acceptance testing): unfortunately the customer must also shoulder a number of implicit responsibilities including liaison with external project stakeholders, especially project funders, clients, and end users, while maintaining the trust of both the development team and the wider business. In this paper, we report on a series of case studies of the customer role in XP projects. We have found that customers have a pressured and stressful role, leading to issues of sustainability.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"53 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130594418","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Refactoring the development process: experiences with the incremental adoption of agile practices","authors":"P. Hodgetts","doi":"10.1109/ADEVC.2004.17","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.17","url":null,"abstract":"The goal of many current process improvement efforts is to become more agile by adopting an agile process. However, the results of several recent projects suggest that when attempting to become more agile, adopting an agile process is exactly the wrong thing to do! In this experience report, the author discuss his failures with wholesale process adoption and his successes using an incremental adoption strategy based on metric- and retrospection-driven feedback. Similar to refactoring practices for design and code, this strategy identifies \"process smells,\" and targets the worst of them with specific agile practices drawn from several popular agile processes.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130664534","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Emergent database design: liberating database development with agile practices","authors":"Alan Harriman, P. Hodgetts, Mike Leo","doi":"10.1109/ADEVC.2004.13","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.13","url":null,"abstract":"Many agile projects do not apply agile practices to their database development. Common wisdom dictates that the entire data model be carefully designed up front and protected from change thereafter. We believed the common wisdom as well. But the clash of traditional database practices and agile development practices caused us significant pain, and hamstrung our ability to deliver the most business value in each iteration. Once we recognized this pain, we abandoned the conventional wisdom. Incrementally, we applied agile discipline to our database development, eventually reducing up-front design work to just-in-time work that matched our 1 to 2 week development iterations. This paper summarizes our experience.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124343004","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}