HOME
REGISTRATION
Conference Schedule
Student Volunteers
TRACKS
APM & Testing
Tutorials
Workshops/P2P
Research Papers
Experience Reports
Educators Symposium
Open Space
Intro to Agile
Executive Summit
Invited Talks
Vendor Presentions
CONFERENCE SPONSORS
EVENT ORGANIZERS
DENVER INFO
PRESS RELEASE
SUBMISSION FORMATTING DETAILS
INFORMATION FOR PRESENTERS
PAST CONFERENCES
ADC 2004
XPAU 2004

Conference Wiki

Conference Presented By:


Subscribe to RSS Feed
(version 0.9)

Website Hosted By:

Research Papers
Monday PM July 25, 2005
Research papers present original contributions to the field of agile development that influence the framework of thought in the area. The papers we have this year are quite varied in their approach and in the area they address. They fall into three broad categories: metaphors and quality (Monday afternoon), social and cultural issues (Monday afternoon) and release/iteration planning (Wednesday morning). They are the output of a rigorous and systematic investigation of one or more aspects of agile development resulting in a variety of insights including empirical findings, new perspectives, novel techniques and innovative support environments. Above all, research papers provide a sound foundation for future advancement in the field of agile development.
Metaphors be with you! (Metaphor System)    
Monday July 25, 2005 1:30-3:00pm
Full Text PDF File  
David West- New Mexico Highlands University
Matt Solano - New Mexico Highlands University
     
Abstract: The original formulation of XP promoted metaphor to the status of essential practice. XP was the only agile method that made the use of metaphor this explicit and essential - unique. Unique: and immediately controversial. Few practitioners claimed to understand the intent of metaphor as a practice, how to devise and evaluate metaphors, or the relationship of metaphor to design and the other XP practices. As XP evolved metaphor was demoted and is no longer a separate practice. Most agile proponents mention metaphor and acknowledge minor uses. This paper argues that XP was wrong to abandon metaphor and advocates a more systematic discussion of how metaphor informs development.

Agile Metrics at the Israeli Air Force    
Monday July 25, 2005 1:30-3:00pm
Full Text PDF File  
Yael Dubinsky - Technion, Israel
David Talby - IDF, Israel
Orit Hazzan - Technion, Israel
Arie Keren - IDF, Israel
     
Abstract: It is a significant challenge to implement and research agile software development methods in organizations such as the army. Since it differs from organizations in the industry and the academia, data gathered in the army and its continuous analysis may enrich the community knowledge abut agile methods. This work describes a research, conducted during an entire release, about one development team at the Israeli Air Force that works according to Extreme Programming. The establishment of this team and the investigation of the first release is part of a long-term process, started last year, aiming to reduce delivery time while raising communication and customer collaboration. Among several themes this research is concerned with, we focus on agile metrics and provide a metrics mechanism that was established and refined along the release development.

Are We Ready to be Unleashed? A Comparative Analysis between Agile Software Development and War Fighting    
Monday July 25, 2005 1:30-3:00pm
Full Text PDF File  
Steve Adolph, WSA Consulting Inc.      
Abstract: Agile is for people, but are people ready for agile? This paper compares the Agile Principles and our agile practices to an organization that may have 2,500 years experience practicing agility, the military. This paper suggests there are sufficient similarities between the nature of war fighting and the nature of software development to warrant a comparison between military war fighting philosophy and agile software development. While there are obvious limitations to this comparison, the comparison is enlightening because it both reveals potential deficiencies in our practice of agility and helps legitimizes agile as valid time tested approach to achieving success.

Agile Security Testing of Web-Based Systems via HTTPUnit    
Monday July 25, 2005 1:30-3:00pm
Full Text PDF File
PowerPoint Presentation
 
A. Tappenden, Univeristy of Alberta
P. Beatty, Univeristy of Alberta
J. Miller, Univeristy of Alberta
     
Abstract: The technological advancements of web-based systems and the shift to iterative and evolutionary development processes have given rise to the idea of agile security testing, where the principles and practices of agile testing are applied to the typically traditional domain of security testing. In this paper, we explore common vulnerabilities for web applications and propose two synergistic approaches for mitigating them. The overall testing strategy mingles well with agile development efforts and gives the development team an opportunity to produce applications that have the "right" functionality and the "right" level of security.

Social Behaviors on XP and non-XP teams: A Comparative Study    
Monday July 25, 2005 3:30-5:00pm
Full Text PDF File
PowerPoint Presentation
 
Jan Chong, Stanford University      
Abstract: This is an ethnographic study of two software development teams within the same organization, one which utilizes the Extreme Programming (XP) methodology and one which does not. This study compares the work routines and work practices of the software developers on the XP team and the non-XP team. Observed behavior suggests that certain features of the XP methodology lead to greater uniformity in work routine and work practice across individual team members. The data also suggest that the XP methodology makes awareness development and maintenance less effortful on a software development team.

Organisational culture and XP: three case studies    
Monday July 25, 2005 3:30-5:00pm
Full Text PDF File
PowerPoint Presentation
 
Hugh Robinson, CESSD
The Open University, UK

Helen Sharp, CESSD
The Open University, UK
     
Abstract: We explore the nature of the interaction between organisational culture and XP practice via three empirically-based case studies. The case studies cover a spectrum of organisational cultures. Our findings suggest that XP can thrive in a range of organisational cultures and that the interaction between organisational culture and XP can be complex & subtle, with consequences for practice.

Clashes between Culture and Software Development Methods:
The Case of the Israeli Hi-Tech Industry and
Extreme Programming
   
Monday July 25, 2005 1:30-3:00pm
Full Text PDF File
PowerPoint Presentation
 
Orit Hazzan
Israel Institute of Technology

Yael Dubinsky
Israel Institute of Technology
     
Abstract: This paper discusses connections between a national culture and the culture inspired by software development methods (SDMs). Specifically, based on our research on cultural issues related to software development teams, we propose a model that can help predict whether a specific SDM fits a specific national culture. This model first defines the terms 'tightness of an SDM' and 'tightness of a national culture'. With respect to an SDM, this term articulates the idea that the tighter an SDM is, the more ordered the software development process and environment it inspires will be; with respect to a national culture, the term 'tightness' reflects the degree to which a culture accepts and adopts ordered, planned and procedural work habits. The model then goes on to outline means that can help in the mapping of a given SDM, as well as a given national culture, along the following five dimensions: Project plan, procedures and standards, responsibility, time estimation, and need satisfaction. Finally, based on these mappings, the fitness of a given SDM and a national culture is examined. It is proposed that this fitness can serve as a tool for predicting the degree to which a given SDM will be accepted by a specific national culture in general, and by a specific team that is part of that culture, in particular. The model is illustrated using the Israeli hi-tech industry as an example of a national cultion and Extreme Programming(XP) as an example of an SDM.

Research Papers
Wednesday AM July 27, 2005
A Case Study on the Impact of Scrum
on Overtime and Customer Satisfaction
   
Wednesday July 25, 2005  
Full Text PDF File  
Chris Mann
University Of Calgary Dept of Computer Science

Frank Maurer
University Of Calgary Dept of Computer Science
     
Abstract: This paper will provide initial results, and experiences from a longitudinal, 2 year industrial case study that is near completion. The quantitative results indicate that after the introduction of a Scrum process into an existing software development organization the amount of overtime decreased, allowing the developers to work at a more sustainable pace while at the same time the qualitative results indicate that there was an increase in customer satisfaction.

An Environment for Collaborative Iteration Planning    
Wednesday July 25, 2005  
Full Text PDF File
PowerPoint Presentation
 
Lawrence Liu, University of Calgary, Alberta
Hakan Erdogmus, National Research Council Canada
Frank Maurer, University of Calgary, Alberta
     
Abstract: Existing project planning software for agile development processes offers limited support for face-to-face, synchronous collaboration. In this paper, we describe an environment, AgilePlanner, that supports team collaboration during planning meetings. Our approach utilizes advanced technologies of pen computing and digital tabletop to create a collaborative work environment. It combines the benefits of paper index cards with those of traditional desktop planning solutions. AgilePlanner is intended as an integral resource in the planning process.

Future of Scrum: Support for Parallel Pipelining of Sprints in Complex Projects    
Wednesday July 25, 2005  
Full Text PDF File  
Jeff Sutherland, Ph.D., PatientKeeper, Inc.      
Abstract: Scrum was invented to rapidly drive innovative new product to market. Six month releases used to be a reasonable time from for an enterprise system. Now it is three months for a major new release, one month for upgrades, and one week for maintenance releases. The initial version of the Agile Scrum development process was designed to enhance productivity and reduce time to market for new product. In this paper, the inventor of Scrum goes back to Scrum basics, throws out Scrum dogma, and designs Advanced Scrum using multiple overlapping Sprints within the same Scrum teams. This methodology delivers increasing application functionality to market at a pace that overwhelms competitors. To capture dominant market share in 2005 requires a metaScrum for release planning, variable length Sprints, overlapping Sprints for a single team, pre-staging Product Backlog, daily Scrum of Scrums meetings, and total automation and integration of Product Backlog and Sprint Backlog with real-time reporting. A practical example of Advanced Scrum describes how mobile/wireless product teams implemented Scrum process automation during 2000-2005. Administrative overhead for over 45 enterprise product releases a year was less than 60 seconds a day per developer and less than 10 minutes a day for a Project Manager. While Advanced Scrum is not for the uninitiated, the future of Scrum is still Scrum, just faster, better, and cooler.

IMPORTANT DATES
Agile 2006 is being scheduled for July 23-28, 2006, at the Hyatt downtown Minneapolis.
Mark your calendars!
The Conference Wiki is up and running!