{"title":"Automated Functional Testing on the TransCanada Alberta Gas Accounting Replacement Project","authors":"Stephen Marsh, S. Pantazopoulos","doi":"10.1109/Agile.2008.64","DOIUrl":"https://doi.org/10.1109/Agile.2008.64","url":null,"abstract":"Automated functional testing with FIT customization was successfully implemented for a large legacy system replacement. The vision for automated functional testing on this project was to produce a comprehensive automated functional regression test that runs quickly and continuously, while producing worthwhile feedback. The tools, techniques and processes presented in this paper evolved over a time period of five years.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114266364","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":"Dependency Management in a Large Agile Environment","authors":"Eric Babinet, Raja Ramanathan","doi":"10.1109/Agile.2008.58","DOIUrl":"https://doi.org/10.1109/Agile.2008.58","url":null,"abstract":"Salesforce.compsilas R&D organization has over 30 Scrum teams working simultaneously in a single release code branch. This report highlights practices that salesforce.com has been using successfully to scale Scrum and to manage inter-team dependencies.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128447101","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 Product Owner Team","authors":"Alan de-Ste-Croix, A. Easton","doi":"10.1109/Agile.2008.94","DOIUrl":"https://doi.org/10.1109/Agile.2008.94","url":null,"abstract":"BT has been using product owner teams to manage the details of \"what should be built\". These teams ownthe content and the breakdown of business scenarios(user story epics) into user stories for delivery teams and act as proxy customers to those delivery teams. This experience report examines a project, implementing an up to 24 Mbps service over the 21CN network, that was successful in applying the approach and concludes with some advice on how best to apply product owner teams.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127929348","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 with Fragile Large Legacy Applications","authors":"Vandana Shah, Ainsley Nies","doi":"10.1109/Agile.2008.86","DOIUrl":"https://doi.org/10.1109/Agile.2008.86","url":null,"abstract":"Can you imagine applying agility to a huge legacy code base over a decade old, supported by a 100+ person distributed development team? Agitar works with customers who have this type of fragile legacy code environment. These customers seek to improve code quality and reduce risk by formalizing a unit test discipline without disrupting the business. In this paper, we share our experience of how three teams with large legacy applications moved from fragile towards agile.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"128 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133534427","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":"Experience Report: The Social Nature of Agile Teams","authors":"E. Whitworth","doi":"10.1109/Agile.2008.53","DOIUrl":"https://doi.org/10.1109/Agile.2008.53","url":null,"abstract":"Agile software development is often, but not always, associated with the term dasiaproject chemistry,psila or the positive team climate that can contribute to high performance. A qualitative study involving 22 participants in agile teams sought to explore this connection, and answer the question: what aspects of agile software development are related to team cohesion? The following is a discussion of participant experiences as seen through a socio-psychological lens. It draws from social-identity theory and socio-psychological literature to explain, not only how, but why agile methodologies support teamwork and collective progress. Agile practices are shown to produce a socio-psychological environment of high-performance, with many of the practical benefits of agile practices being supported and mediated by social and personal concerns.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"22 6S 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115942300","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":"7 Years of Agile Management","authors":"Christ Vriens, René Barto","doi":"10.1109/Agile.2008.97","DOIUrl":"https://doi.org/10.1109/Agile.2008.97","url":null,"abstract":"This paper describes the experiences in building and growing a professional agile software development group in a research context over the past 7 years.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115094400","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 Agile Approach to Proposition Assessment","authors":"Luke Barrett","doi":"10.1109/Agile.2008.56","DOIUrl":"https://doi.org/10.1109/Agile.2008.56","url":null,"abstract":"Every day, many ideas of widely varying completeness and quality are generated for new products and services. Organizations and individuals face a constant challenge in how they determine which of these ideas will receive further investment and which not. In this paper, we look at a lightweight approach to the assessment of ideas that helps face this challenge.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"458 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116189221","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":"Colossal, Scattered, and Chaotic (Planning with a Large Distributed Team)","authors":"W. Williams, M. Stout","doi":"10.1109/Agile.2008.25","DOIUrl":"https://doi.org/10.1109/Agile.2008.25","url":null,"abstract":"If planning for a large co-located 30-plus development team is not enough to make you want to pull your hair out then try a 30-plus development team located across several time zones, in places with different cultures and languages. Now, youpsilave reached a level in the Agile planning game that would send most product owners running home to their mommies. Planning in Agile Projects requires enabling the team to have a continuous conversation with the customer. How can you have meaningful, continuous conversation and feedback when your team is scattered across several time zones, cultures and languages? This paper describes our experience of how one of our largest teams in Sabre Airline Solutions was able to make changes that allowed the continuous conversations to take place. The paper is written from the perspective of both development locations the main office in Dallas, Texas and the \"remote\" office in Krakow, Poland. The team successfully overcame many obstacles while rapidly growing a small co-located development team into a large globally distributed team that was able to efficiently deliver customer valued, quality code and customer satisfaction with each one-week iteration. It attributed this success to three main Agile areas: evolving the Agile Customer Role, making our meetings valuable and efficient for everyone involved, and good coordination across the sub teams.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121970234","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":"Scaling Up Pushing Scrum out of its Comfort Zone","authors":"Richard Lyon, M. Evans","doi":"10.1109/Agile.2008.19","DOIUrl":"https://doi.org/10.1109/Agile.2008.19","url":null,"abstract":"Single team implementations are where Scrum is most comfortable. Having successfully adopted Scrum for single teams within our department we were now faced with the choice of dropping the use of Scrum on a large multi-team project or scaling Scrum up. We chose the latter, despite the fact that neither we nor anyone else seemed to know exactly what was involved. This is the story of how we dragged Scrum kicking and screaming out of its (and our) comfort zone.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"75 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116794322","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":"Mature Agile with a Twist of CMMI","authors":"C. Jakobsen, Kent Johnson","doi":"10.1109/Agile.2008.10","DOIUrl":"https://doi.org/10.1109/Agile.2008.10","url":null,"abstract":"Systematic is an agile company working at CMMI level 5, where the default way of working is based on Scrum and story based early testing development. Solid experiences in combining CMMI with Scrum and story based development, has shown that the mix provides strong synergies (Sutherland et al., 2007) and insights into what CMMI practices fit and amplify the execution of Scrum and story based early testing development. This paper presents specifically how agile methods like Scrum are successfully combined with CMMI. CMMI provides solid support for what disciplines to consider. When applied the disciplines create a focus on important aspects of agile methods that perhaps are not normally elaborated, for example how to ensure a proper quality of a product backlog or how to ensure a proper \"production line\" for the project. This guidance may not be needed for small agile projects, but as the agile movement continues to grow, and is used for larger and more complex projects, agile projects will need to address these issues related to increased size and complexity. The experiences from combining CMMI and Scrum have led Systematic to identify examples of explicit guidance from CMMI that help to execute normal Scrum activities even better. These activities can be implemented in the spirit of the agile manifesto and principles and by doing so agile methods can be augmented and matured to ensure that even larger and more complex projects in the future can and will benefit from agile - with a twist of CMMI.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124798464","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}