{"title":"Overhauling a Failed Project Using Out of the Box Scrum","authors":"M. Edwards","doi":"10.1109/Agile.2008.35","DOIUrl":"https://doi.org/10.1109/Agile.2008.35","url":null,"abstract":"A software solutions company out-sourced a ground-up application build to a team of globally distributed independent consultants. The project eventually exceeded time and cost expectations and failed to deliver production ready tested software according to a planned market release window. The asserted reasons for this planned versus actual delta varied with time including failure of leadership, failure of project oversight, to design and implementation flaws and so on. Out of the box Scrum was implemented by a newly contracted consultant and the project delivered 153% of plan by the end of four two-week sprints. This report discusses the problem, the implemented solution, and the results while challenging what really made the difference.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"53 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":"115663983","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}
L. Williams, D. McCrickard, L. Layman, Khaled Hussein
{"title":"Eleven Guidelines for Implementing Pair Programming in the Classroom","authors":"L. Williams, D. McCrickard, L. Layman, Khaled Hussein","doi":"10.1109/Agile.2008.12","DOIUrl":"https://doi.org/10.1109/Agile.2008.12","url":null,"abstract":"Utilizing pair programming in the classroom requires specific classroom management techniques. We have created nine guidelines for successfully implementing pair programming in the classroom. These guidelines are based on pair programming experiences spanning seven years and over one thousand students at North Carolina State University. In Fall 2007, pair programming was adopted in the undergraduate human-computer interaction (HCI) course at Virginia Tech. We present the pair programming guidelines in the context of the HCI course, discuss how the guidelines were implemented, and evaluate the general applicability and sufficiency of the guidelines. We find that eight of the nine guidelines were applicable to the Virginia Tech experience. We amended our peer evaluation guideline to account for constantly supervised pairing, as was the case at Virginia Tech. We add two guidelines stating that a pair should always be working toward a common goal and that pairs should be encouraged to find their own answers to increase their independence and self-confidence.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"28 2 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":"116937799","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":"Effective and Pragmatic Test Driven Development","authors":"A. Rendell","doi":"10.1109/Agile.2008.45","DOIUrl":"https://doi.org/10.1109/Agile.2008.45","url":null,"abstract":"Test driven development has long been a key tool in the agile toolbox. Often it is suggested that the technique has moved into the mainstream and that not applying a test first approach is exceptional. Recent coverage in the community has even started to describe a post-TDD approach. Having worked with TDD for the last five years with varying degrees of rigor and success I have observed that far from being ubiquitous, effective application of TDD is uncommon. This paper takes a pragmatic approach in evaluating the implementation of, impediments against and measurable benefits of TDD on a large, commercially successful, project. Analysis of this experience will show how and why TDD is being used incorrectly and how this situation can be corrected. The analysis will show how project delivery improved when a more effective approach was applied.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"12 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":"121068249","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}
J. Sutherland, Guido Schoonheim, Eelco Rustenburg, M. Rijk
{"title":"Fully Distributed Scrum: The Secret Sauce for Hyperproductive Offshored Development Teams","authors":"J. Sutherland, Guido Schoonheim, Eelco Rustenburg, M. Rijk","doi":"10.1109/Agile.2008.92","DOIUrl":"https://doi.org/10.1109/Agile.2008.92","url":null,"abstract":"Scrum was designed to achieve a hyperproductive state where productivity increases 5-10 times over industry averages and many collocated teams have achieved this effect. The question for this paper is whether distributed, offshore teams can consistently achieve the hyperproductive state. In particular, can a team establish a localized velocity and then maintain or increase that velocity when distributing teams across continents. Since 2006, Xebia started projects with half Dutch and half Indian team members. After establishing localized hyperproductivity, they move the Indian members of the team to India and show increasing velocity with fully distributed teams. After running XP engineering practices inside many distributed Scrum projects, Xebia has systematically productized a model very similar to the SirsiDynix model (J. Sutherland, 2006) for high performance, distributed, offshore teams with outstanding quality.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"7 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":"121111295","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":"Coding Dojo: An Environment for Learning and Sharing Agile Practices","authors":"D. Sato, Hugo Corbucci, M. Bravo","doi":"10.1109/AGILE.2008.11","DOIUrl":"https://doi.org/10.1109/AGILE.2008.11","url":null,"abstract":"A Coding Dojo is a meeting where a group of programmers gets together to learn, practice, and share experiences. This report describes the authors' experience of creating and running an active Coding Dojo in Sao Paulo, Brazil, sharing the lessons learned from the experience. The role of the Dojo in the learning process is discussed, showing how it creates an environment for fostering and sharing agile practices such as test-driven development, refactoring and pair programming, among others.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"21 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":"126080756","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 Project Leadership My Top 10 Value Driven Principles","authors":"Lynne Ralston","doi":"10.1109/Agile.2008.47","DOIUrl":"https://doi.org/10.1109/Agile.2008.47","url":null,"abstract":"I have often been asked, \"How important is strong agile management to an agile project?\" I believe this is due to a failure of the agile process relating directly from ineffective leadership. Based on my experience leading teams on large-scale projects in agile-skeptic environments over last 8 years, I learned that the right kind of leadership is valuable to helping teams to succeed. In this report I will share some of those experiences, and the values I have evolved that I see as important in that leadership role. This report challenges the audience to define their own value based leadership list.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"44 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":"123453936","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 Doctor is \"In\" -- Using the Office Hours Concept to Make Limited Resources Most Effective","authors":"A. Leszek, C. Courage","doi":"10.1109/Agile.2008.46","DOIUrl":"https://doi.org/10.1109/Agile.2008.46","url":null,"abstract":"Salesforce.compsilas technology organization transitioned over 30 product teams from a waterfall development process to an agile development process. After this transition, it was evident that shared resources, such as user experience and product documentation professionals, could not support as many teams as they had in the past using a waterfall process. As a result, shared resources were assigned to fewer teams, which left some teams without designated team members for product documentation and user experience. This report highlights how salesforce.com has adopted the concept of office hours in order to make these limited, shared resources most effective and to support teams that do not have a designated resource for user experience or product documentation.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"59-60 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":"125688115","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":"Fast & Predictable A Lightweight Release Framework Promotes Agility through Rhythm and Flow","authors":"Amy Farrow, Steve Greene","doi":"10.1109/Agile.2008.83","DOIUrl":"https://doi.org/10.1109/Agile.2008.83","url":null,"abstract":"Embarking on salesforce.compsilas large scale transformation to our adaptive development methodology presented many unique challenges due to the scale of the rollout as well as the need to align a large number of teams (30+) to a common release date, 3-4 times per year. To specifically address the latter challenge, we created a lightweight release framework in order to optimize on-time, high quality delivery to our customers and partners. Salesforce.com delivers product functionality using the software-as-a-service hosted model and has 30+ scrum teams working on a single release concurrently. The release framework that we created exhibitscharacteristics different than most release processes--simple, lightweight, unambiguous, and visibleeverywhere, to our entire technology organization. By implementing this lightweight release framework and making it highly visible, wepsilave organically promoted a cyclical harmony and rhythm in our organization and across all scrum teams. This cyclical harmony and rhythm has created an environment where local team agility is promoted, facilitated and thrives. To support an agile methodology effectively on an enterprise scale, a lightweight release framework is highly useful in empowering small self-organizing teams while \"optimizing the whole\" of the product you are focused on delivering. Interestingly enough, we found that the absence of one can actually inhibit agility and avoidable ambiguity, in an environment where there is a high degree of unavoidable ambiguity.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"61 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":"114956721","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 Design Studio: Interface Design for Agile Teams","authors":"Jim Ungar","doi":"10.1109/Agile.2008.51","DOIUrl":"https://doi.org/10.1109/Agile.2008.51","url":null,"abstract":"In this report we describe our experience with the merger of user centered design (UCD) into agile (team) development practice as manifest in a one day design studio. We will walk through our process from the preliminary design research through the conclusion of the day-long workshop that is the design studio by describing those activities in the context of one project. We will follow by enumerating and explaining the benefits we have observed from taking a studio approach to design.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"3 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":"122292603","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":"Technical lessons Learned Turning the Agile Dials to Eleven!","authors":"Paul King, Craig Smith","doi":"10.1109/Agile.2008.15","DOIUrl":"https://doi.org/10.1109/Agile.2008.15","url":null,"abstract":"This report outlines technical lessons learnt by about 20 of Australiapsilas most experienced agile specialists over several years across several projects within an organization which aggressively applied the agile practices with much success. In these projects the agile dials were cranked to eleven to achieve very high levels of quality. Most of the specialists involved believe that they produced the highest quality software of their careers with some of the highest productivity they have ever experienced.","PeriodicalId":129146,"journal":{"name":"Agile 2008 Conference","volume":"19 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":"114159047","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}