{"title":"Agile methods applied to embedded firmware development","authors":"Bill Greene","doi":"10.1109/ADEVC.2004.3","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.3","url":null,"abstract":"This paper describes the experience of applying agile approaches to the development of firmware for the Intel/spl reg/ Itanium/spl reg/ processor family. Embedded development (i.e. firmware) projects are quite different from object-oriented and pure software endeavors, yet they face many of the same challenges that agile software development practices address. Several unique challenges are described, including team members' specialized domain knowledge, technical backgrounds and attitudes toward change, and the impact hardware plays in firmware design. We found agile approaches to be well-suited for our project, despite the fact that most agile methodologists come from very different backgrounds.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"39 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":"125098270","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 slacker's guide to project tracking or spending time on more important things","authors":"James Davison, Tim Mackinnon, Michael Royle","doi":"10.1109/ADEVC.2004.22","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.22","url":null,"abstract":"As a project manager, your time is far too important to be wasted on mundane tasks like detailed tracking of the day-to-day activities of each of your developers. Wouldn't it be nice if you spent your time negotiating project scope and identifying and removing team impediments? Our experience has shown that consistency in card sizes and estimates allows you to perform full project planning with little effort. Additionally, it results in diagrams that accurately reflect your project's status. With this, release planning sessions take hours not days, freeing up valuable time for both you and your developers.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"448 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":"125783858","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":"Aligning strategic planning with agile development: extending agile thinking to business improvement","authors":"Colin Rand, Bruce Eckfeldt","doi":"10.1109/ADEVC.2004.5","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.5","url":null,"abstract":"Many development teams have successfully used agile development to build quality software, but often these projects have failed to effectively contribute to overall company success. Our feeling is that this failure is due to the fact that most companies' strategic planning processes have not been aligned to take advantage of the flexibility and adaptability of agile development. We strongly believe in the power of agile development; however we feel that this alone is insufficient to make every software project successful. Projects must be coupled with a complimentary approach to strategy to in order to achieve the overall business goals. If agile development is to continue growing in the business community, complimentary strategic planning capabilities must be developed that share the same agile philosophies.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"125 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":"131641197","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":"Using competition to build a stronger team","authors":"Darin Cummins","doi":"10.1109/ADEVC.2004.25","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.25","url":null,"abstract":"In 2001 we started a new project at our company. Undermanned, short on time, and under the gun to succeed, we knew that we needed a process that would help us stay on track. Unfortunately, once the project got under way, we received a lot of negative feedback from the developers. The process took away from what developers want to do: code. This paper describes how we used competition as a tool to create a more cohesive team that worked better with management and the process.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"143 8","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-06-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"113939919","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":"DecisionSpace infrastructure: agile development in a large, distributed team","authors":"Marjorie Farmer","doi":"10.1109/ADEVC.2004.11","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.11","url":null,"abstract":"DecisionSpace infrastructure was an effort to develop new software in a company where the corporate culture was geared to support old products. The team was large and distributed, and used an agile approach to succeed despite that. In the process, the team helped to lead the company to rediscover how to develop new software products.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"30 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":"125719635","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}
A. Jackson, S. L. Tsang, Alan Gray, C. Driver, S. Clarke
{"title":"Behind the rules: XP experiences","authors":"A. Jackson, S. L. Tsang, Alan Gray, C. Driver, S. Clarke","doi":"10.1109/ADEVC.2004.9","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.9","url":null,"abstract":"Agile processes such as XP (extreme programming) have been recognised for their potential benefits of improving software. During adoption of the XP process, teams can misapply the XP principles by following them verbatim, ignoring the context in which they are applied. In this paper we document our experiences where naive applications of XP principles were altered in recognition of context. We detail our observations of how teams \"looked behind\" the rules and began fitting XP to the problem rather than attempting to fit the problem to XP. We conclude by reflectively focusing on how this transformation occurred and suggest that it is buying into the XP ethos that drives this change of perspective on the XP process and principles.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"34 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":"125412694","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}
Todd A. Little, Forrest Greene, Tessy Phillips, R. Pilger, Robert Poldervaart
{"title":"Adaptive agility","authors":"Todd A. Little, Forrest Greene, Tessy Phillips, R. Pilger, Robert Poldervaart","doi":"10.1109/ADEVC.2004.2","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.2","url":null,"abstract":"To maximize the velocity of business value delivery Alistair Cockburn talks of having a process that is \"barely sufficient\". At Landmark Graphics we developed some guidelines as to what \"barely sufficient\" means for our various software projects. We examined over 60 projects and observed two primary attributes that influenced the type of process used: complexity and uncertainty. We provide a scoring model for plotting projects onto a four quadrant graph, which we use to categorize projects into dogs - simple projects with low uncertainty, colts - simple projects with high uncertainty, cows - complex projects with low uncertainty, or bulls - complex projects with high uncertainty. We adapt our agile process from a core set of barely sufficient practices that all projects use and add processes and practices according to a project's profile. One key benefit of this approach has been identifying project drivers and providing early guidance to project teams so that they can start with a process that is close to appropriate.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"25 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":"134219671","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":"Exploring extreme programming in context: an industrial case study","authors":"L. Layman, L. Williams, Lynn Cunningham","doi":"10.1109/ADEVC.2004.15","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.15","url":null,"abstract":"A longitudinal case study evaluating the effects of adopting the extreme programming (XP) methodology was performed at Sabre Airline Solutions/spl trade/. The Sabre team was a characteristically agile team in that they had no need to scale or re-scope XP for their project parameters and organizational environment. The case study compares two releases of the same product. One release was completed just prior to the team's adoption of the XP methodology, and the other was completed after approximately two years of XP use. Comparisons of the new release project results to the old release project results show a 50% increase in productivity, a 65% improvement in pre-release quality, and a 35% improvement in post-release quality. These findings suggest that, over time, adopting the XP process can result in increased productivity and quality.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"44 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":"129257742","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":"Subclassing XP: breaking its rules the right way","authors":"G. Luck","doi":"10.1109/ADEVC.2004.19","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.19","url":null,"abstract":"Extreme programming encourages adoption of all of its practices. In practice many projects drop practices. What remains can be an incomplete methodology, which is dangerous. This problem can be overcome by replacing each removed dropped practice with a compensating practice tailored to the circumstances of the project - effectively subclassing XP. This experience report recounts the experiences of subclassing of XP at Wotif.com, where pair programming was replaced with \"pairing\" and refactoring was replaced with \"team refactoring\".","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"4 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":"115496429","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":"A study case: evolution of co-location and planning strategy","authors":"Amy Law, Allen Ho","doi":"10.1109/ADEVC.2004.1","DOIUrl":"https://doi.org/10.1109/ADEVC.2004.1","url":null,"abstract":"Agile practices can and should be evolved throughout a project. This paper focuses on the evolution of two agile practices, namely co-location and planning strategy, in a software development project at TransCanada. From inception to conclusion, the evolution contributes to the successful delivery of an in-house developed system and leads to change in organizational culture.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"4 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":"128579373","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}