{"title":"Unfixing the fixed scope project: using agile methodologies to create flexibility in project scope","authors":"Jeff Patton","doi":"10.1109/ADC.2003.1231465","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231465","url":null,"abstract":"Although it seems to be common knowledge that it's impossible to succeed in a project with fixed time, quality and scope, we often continue to try anyway. This experience report discusses our successful failure at running fixed time and scope projects. We say successful failure because we actually failed to fix scope but arrived at an acceptable way to vary scope and deliver on time in an environment not normally amenable to variable scope. We discuss the methods used and make recommendations on how we might unfix scope in our development environment.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132039894","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":"Certifying for CMM Level 2 and IS09001 with XP@Scrum","authors":"Christ Vriens","doi":"10.1109/ADC.2003.1231461","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231461","url":null,"abstract":"This experience report describes the followed road of getting certified for both CMM Level 2 and ISO9001:2000 on a time scale of 2 years by using agile methodologies. We discuss why we selected the combination of extreme programming (XP) and Scrum as the base for our software development process and which \"ceremony\" we had to add in order to satisfy the requirements ofCMML2 and ISO9001. Also our major challenges at the moment are described, and the way we try to solve them. Furthermore we want to share a number of issues and experiences.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132267399","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":"Introducing agile development into bioinformatics: an experience report","authors":"David Kane","doi":"10.1109/ADC.2003.1231463","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231463","url":null,"abstract":"This experience report describes our efforts to introduce agile development techniques incrementally into our customer's organization in the National Cancer Institute and develop a partnering relationship in the process. The report addresses the steps we have taken not only to deploy the practices, but also to gain customer support for them. It addresses variations we have used to adapt to our customer's environment, including our approach to involving customer personnel at remote locations. We also address challenges we still must face, including how best to manage a product-line with agile development techniques.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122132956","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":"Making agile development work in a government contracting environment-measuring velocity with earned value","authors":"Glen B. Alleman, Michael Henderson, R. Seggelke","doi":"10.1109/ADC.2003.1231460","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231460","url":null,"abstract":"Before any of the current \"agile\" development methods, earned value management provided information for planning and controlling complex projects by measuring how much \"value\" was produced for a given cost in a period of time. One shortcoming of an agile development method is its inability to forecast the future cost and schedule of the project beyond the use of \"yesterdays weather\" metrics. These agile methods assume the delivered value, \"velocity\" in the case of XP, is compared with the estimated value-this is a simple comparison between budget and actual cost resulting in a cost variance. No schedule variance process is directly available in XP. Earned value analysis provides a means of predicting future schedule and cost variances through three measurements-budgeted cost for work scheduled, actual cost for work performed, and budgeted cost for work performed (earned value). We describe the use of earned value in conjunction with agile development on a mission-critical, high-security, government project.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"111 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116648720","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":"Iteration advocate/iteration transition meeting: small sampling of new agile techniques used at a major telecommunications firm","authors":"Brian S. Boelsterli","doi":"10.1109/ADC.2003.1231459","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231459","url":null,"abstract":"We document a successful implementation of agile at a major telecommunications firm. Critical aspects to mention about this particular software endeavor include: a) this could be one of the largest implementations of agile documented thus far (approximately 275 immediate and over 3,000 supportive contributors involved), b) the team practicing agile did so under the constraints of a waterfall-gated (both milestone and financial) environment, c) a 'practice tapestry' approach was used to 'weave' together elements of agile that would work for this organization, and finally, d) new practices, not previously documented to the agile community were applied in addition to those well known thus far. We focus on these new practices in an effort to share them with the agile community. The weaving together of existing and new practices, enabled this major telecommunications firm to deliver a major software release to its large customer base.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"04 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127259785","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":"Change your organization (for Peons)","authors":"Jim Little","doi":"10.1109/ADC.2003.1231453","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231453","url":null,"abstract":"A programmer at a medium-sized software company explains his tactics for bottom-up organizational change. The tactics are accompanied by personal recollections of related experiences. Tactics are presented in three primary sections: the difficulty of making change; getting attention; and making a case for change. A brief section on the consequences of change follows.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132842537","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":"Daily iterations: approaching code freeze and half the team is not agile","authors":"C. R. Cooley","doi":"10.1109/ADC.2003.1231467","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231467","url":null,"abstract":"We were asked to bring XP to diverse teams. Our team was split geographically and half the team prefers nonagile methods. Approaching \"code frost\" we decided to do daily iterations to kill bugs and keep the nonagile half of the team happy.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"271 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122865111","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":"Agile development in the old economy","authors":"Géry Derbier","doi":"10.1109/ADC.2003.1231462","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231462","url":null,"abstract":"As part of the delivery an automated hub for a postal operator, the Solystic company has to build a complex and feature rich information system that supports a highly automated process with multiple intricate sub-processes and exceptions. The effort has several challenges: 1) it is business critical for the customer, and the output of the project will give the customer a leading position; 2) it is the first time Solystic is managing a complete system project, although its mother company Northrop Grumman had previous experience of this business; 3) the program is one of the first business of the Solystic company in the international field; 4) it is a fixed price, fixed time contract with a short time frame. To face all these challenges, the software development group in charge of the information system has adopted a number of agile practices and techniques to manage the project. The major project settings are adapted from Alistair Cockburn's crystal set of methodologies, SCRUM and Jim Coplien's work on organizational patterns. We present the findings and lessons learned by the team and its manager.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115366671","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":"Finding a place for discount usability engineering in agile development: throwing down the gauntlet","authors":"David Kane","doi":"10.1109/ADC.2003.1231451","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231451","url":null,"abstract":"Many software development organizations are reporting great success with agile software development techniques. However, few techniques explicitly incorporate usability engineering. Further, some agile techniques may not address certain kinds of usability problems, e.g. they may not address the needs of novices as well as expert users. While there are many techniques for usability engineering, discount usability engineering should be of particular interest to the agile development community because the two disciplines share many of the same underlying principles. The challenge for the agile development community is to find ways to incorporate and gain value from such discount usability engineering practices.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"44 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125477312","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":"\"Ready-to-roll\" boxcar development - a flexible, quality-weighted process","authors":"R. R. Hill","doi":"10.1109/ADC.2003.1231458","DOIUrl":"https://doi.org/10.1109/ADC.2003.1231458","url":null,"abstract":"In January of 1996, Intuit's QuickBooks team was faced with an aging code-base using a custom Mac/Win GUI toolkit, a large and rapidly growing customer base, and a rapidly growing and product-inexperienced engineering team. To increase the product's quality and feature predictability while retaining its ship date rigidity, we created \"ready-to-roll\" boxcar development. The process enabled the defining of each new feature, enhancement, or engineering rearchitecture as a set of boxcars on the product train. A \"coupled\" boxcar was rapidly brought to a supportable level of quality, or \"decoupled\" for reevaluation and reengineering. Frontloading the highest priority boxcars increased predictability of the product train's contents, while the process allowed for greater flexibility with respect to overall content. \"Ready-to-roll\" boxcar development kept the product within 2-3 weeks of being supportable and shippable. The process focused on individuals and interactions, working software, customer collaboration and responding to change. Better yet, it worked.","PeriodicalId":325418,"journal":{"name":"Proceedings of the Agile Development Conference, 2003. ADC 2003","volume":"270 2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-06-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134236204","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}