Conference Schedule
Student Volunteers
APM & Testing
Research Papers
Experience Reports
Educators Symposium
Open Space
Intro to Agile
Executive Summit
Invited Talks
Vendor Presentions
ADC 2004
XPAU 2004

Conference Wiki

Conference Presented By:

Subscribe to RSS Feed
(version 0.9)

Website Hosted By:

Monday PM July 25, 2005
A workshop/peer-to-peer session is an opportunity for conference attendees to learn from each other about a relevant topic and share the concrete outcomes after the session. The sessions leader(s) are there only to provide a structure to help participants learn from each other and produce deliverables. The goal of these sessions is to help attendees learn about a topic both of interest and of use in their daily work. Sessions are open to all conference participants. Participants can sign up during the conference, unless the attendance limit is reached.

Agile Contracts: How to develop contracts that support agile software development  
Monday July 25, 2005 1:30-5:00pm
Mary Poppendieck, Poppendieck.LLC     Mary Poppendieck
Bio: MARY POPPENDIECK, is a seasoned leader in both operations and new product development with more than 25 years' of IT experience. She has led teams implementing lean solutions ranging from enterprise supply chain management to digital media, and built one of 3M's first Just-in-Time lean production systems. Mary is currently the President of Poppendieck LLC and located in Minnesota. Her book Lean S oftware Development: An Agile Toolkit, which brings lean principles to software development, won the Software Development Productivity Award in 2004.
Abstract: Agile Development sounds great, but it depends on the ability to determine the details of scope as the system is developed, driven by feedback from customers and users. Much software development is done under contract, where there is often a requirement to determine the details of the system early in the development process.

Delivering value early    
Monday July 25, 2005 1:30-5:00pm
Steve Freeman, M3P Limited      
Abstract: The ideal XP project allows the team to ship the code as soon as the next features are ready. In practice, many organizations cannot (or will not) accept this, so the team has to find ways to reduce the stress of releasing or, better, produce something of value to the organization before the final delivery. In this workshop, participants will exchange experiences and ideas about how to maneuver a project into delivering real value early, even where the organization itself is not Agile.

IEEE 1648 Recommended Practice for Agile Methods    
Monday July 25, 2005 1:30-3:00pm
Scott Duncan IEEE S2ESC      
Abstract: Audience: Those already working on this IEEE effort as well as those who want to get an update on what is happening with it. People attending should have a reasonably strong interest in work on this standard, though the first part of the session will be an overview for those less committed to working on it who wish to know where it stands.
Goal: Review the existing proposed content and take ideas for additions and changes.

Process: The first 15-20 minutes will be an overview of where the work stands which I will present. The next 15-20 minutes will be an open discussion on the material covering what a customer should know about their responsibilities in a relationship with an agile development group. The next 15-20 minutes will be an open discussion on the material covering what a customer should expect from an agile development group. The next 15-20 minutes will be an open discussion on the material covering issues confronting agile methods in a more formal methodology environment. The last 15-20 minutes will discuss relationship of this work with other standards.

Deliverables: Updated draft material for the standard with a summary to be prepared after the conference and posted to the conference wiki.

How to apply agile development methods in open source projects    
Monday July 25, 2005 3:30-5:00pm
Robert S. Sfeir, SRA International
David Kane, SRA International
Abstract: There is a strong affinity between the agile development and the open source communities. Many projects using agile development are supported by a wide array of open source tools. Agile development methods have influenced the organization of many open source projects. However, many of the assumptions and structures of the most common agile methods are hard to directly apply in an open source setting. Typically open source projects are much more widely distributed than the typical agile development project, and participants are usually volunteers, employees or a combination of both, as in the example of Apache and JBoss. How can agile development methods be applied to solving the challenges of managing open source projects? During this workshop we will seek to explore these questions. Participants will be invited to share their experience in applying agile development methods in open source projects, or their thoughts on approaches that could be explored.

Androgogical Approaches to Learning in the Agile Software Development Team    
Monday July 25, 2005 3:30-5:00pm
Pam Rostal, New Mexico Highlands University
David West, New Mexico Highlands University
Abstract: This workshop will explore the implications of androgogy (an inquiry-based educational ideology most frequently appropriate for adult learning) for agile software development teams. Often, one of the motivators for agility is the fact that technologies change frequently and therefore teams must adapt. When the change requires new learning, the standard response is to send people off to training for 3 days or a week and then expect them to be productive with the new tool, technology, or methodology. This workshop will bring together professionals, academicians and managers to discuss approaches to learning while doing based on characteristics of adult learners, particularly in the context of the agile software development team.
Tuesday AM July 26, 2005
Living the Declaration of Interdependence    
Tuesday July 26, 2005 9:00am-12:30
Ole Jepsen, CAP Gemini      
Abstract: In January 2005 a group of agile leaders met in Seattle and created the "Declaration of Interdependence". The purpose of this group is to start building an alternative to PMI and IPMI for agile project managers - and the first shipable result of our work is the Declaration:
* We increase return on investment by making continuous flow of value our focus.
* We deliver reliable results by engaging customers in frequent interactions and shared ownership.
* We manage uncertainty through iterations, anticipation and adaptation.
* We unleash creativity and innovation by recognizing that individuals are the ultimate source of value, and creating an environment where they can make a difference.
* We boost performance through group accountability for results and shared responsibility for team effectiveness.
* We improve effectiveness and reliability through situationally specific strategies, processes and practices.
In this workshop we will examine each of the 6 parts of the declaration. As a participant you will have the chance to share your experiences and to participate in the description of practices that have proven themselves to support the way of working, that is described by the declaration.
This workshop will be run as an open space discussion - and the process will be exactly the same as the process used to come up with the Declaration of Interdependence in Seattle in January.

The Courage to Communicate:
Collaborative Skills for Agile Teams
Tuesday July 26, 2005 9:00am-12:30
Diana Larsen, Futureworks Consulting     Diana Larsen
Bio: Diana Larsen Identified as a standard-setting consultant by clients, an exceptional facilitator by colleagues, and the "best boss ever" by former employees, Diana Larsen is a senior consultant with FutureWorks Consulting. Diana partners with leaders of software development projects to strengthen their ability to support and sustain change initiatives, improve project performance, and retain organizational learning. A specialist in the human side of software development, Diana focuses on software team development, facilitation for project chartering and retrospectives.
Abstract: Communication, Feedback, Courage, Simplicity. Individuals and interactions over process and tools. Applying the values of Agile approaches to software development projects highlights a shift to increased importance of functioning well in highly collaborative team environments. The initial excitement of trying something new and the intense learning curve of understanding and applying the practices tends to overshadow team member interactions through the first stages of project team development. However, once XP/Agile practices become the usual way of doing business, team members frequently discover the limits of their ability to communicate and work collaboratively. Effective, collaborative communication becomes the next challenge. Three skills in particular help a team make the move from adequate work performance to high performance. In this highly interactive, experiential tutorial, participants learn the critical collaborative skills of group decision-making, active listening and interpersonal feedback - seeking it, giving it, and receiving it well.
Roadmap to Agile Testing    
Tuesday July 26, 2005 9:00am-10:30
Kay Johansen
The Church of Jesus Christ of Latter-Day Saints

Jeremy Brown, Novell
Abstract: So you want to increase your testing agility, but aren't sure how to get there from here? Are you somewhere en route to agility and want to correlate experiences with your peers? Perhaps you've done extensive exploration in the jungles of Agile testing, but aren't quite ready to open up guided tours? Creating a roadmap to Agile testing adoption can help us organize and distill our experiences and make our journey more enjoyable. This workshop will provide an opportunity to share real experiences and distill lessons learned from them, which will help particpants at all levels of adoption of Agile testing to build and improve their own roadmaps forward.

Informative Workspace  
Tuesday July 26, 2005 11:00am-12:30
Rachel Davies, Agile Experience
Mike Hill
    Rachel Davies
Bio: Rachel Davies is an agile coach and facilitator from United Kingdom who works with teams learning how to improve their code quality with Test First and Refactoring. She specializes in XP and Scrum and believes thatRetrospectives are a vital tool for a team to adapt their development process to fit the project context. Rachel is a frequent presenter at agile conferences and serving director of the Agile Alliance.
Abstract: Informative Workspace is one of the new XP practices launched in the second edition of XP Explained. The practice is to build feedback mechanisms around an agile team that support them in their daily work. These feedback mechanisms can take the form of visual displays (Information Radiators) that are manually updated by the team or electronic eXtreme Feedback Devices (XFD) such as lava lamps or audio signals linked to automated processes. It is vital to ensure that feedback mechanisms are easy to interpret, low maintenance and adapted to local practices. In this session we will work on new ways to support an Informative Workspace.

Tuesday PM July 26, 2005
Becoming a Collaborative Leader  
Tuesday July 26, 2005 1:30-5:00pm
Christopher Avery, Partnerwerks
Pollyanna Pixton, Evolutionary Systems
    Pollyanna Pixton
Bio: Pollyanna Pixton is President of Evolutionary Systems, a consulting firm that works with organizations in the U.S. and Europe to move great ideas from vision to action through rich collaboration. She is co-founder of the Institute of Collaborative Leadership (www.collaborative- leadership.com), which provides a suite of leadership seminars and workshops that are fully integrated with personal coaching, peer-to-peer mentoring, and open-space meetings that provide support to leaders in every phase of implementation. Pixton serves on the Agile Project Leadership Network Board, and speaks, lectures, and writes about business ethics, organizational development, and collaborative leadership.
Abstract: What is a collaborative leader? What can I do to become one? These are the questions that we will collaboratively answer in this workshop. In this workshop, we will define Collaborative Leadership and compare this with the command and control model and, after each participant compares their current leadership style with the collaborative model, strategies for reaching the full collaborative model will be developed.

Workshop on Agile Transition Management  
Tuesday July 26, 2005 1:30-5:00pm
Mike Cohn, Mountain Goat Software,

Tobias Mayer, Yahoo
Christian Hessler, Sun Microsystems
    Mike Cohn
Bio: Mike Cohn is the founder of Mountain Goat Software, a process and project management consultancy and training firm. Mike specializes in helping companies adopt and improve their use of agile processes and techniques in order to build extremely high performance development organizations. He is the author of User Stories Applied for Agile Software Development and Agile Estimating and Planning, as well as books on Java and C++ programming. With more than 20 years of experience, Mike has previously been a technology executive in companies of various sizes, from startup to Fortune 40. He has also written articles for Better Software, Cutter IT Journal, IEEE Computer, Software Test and Quality Engineering, Agile Times, and the C++ Users' Journal. Mike is a frequent speaker at industry conferences, is a founding member of the AgileAlliance, and serves on its board of directors. He is a Certified ScrumMaster and a member of the IEEE Computer Society and the ACM.He can be reached at mike@mountaingoatsoftware.com.
Abstract: The goal of this workshop will be to come up with a list of things that an organization must do on their way to becoming agile. Beyond making a partial list of these items we plan to work on developing information on how to accomplish each and dependencies between them. For example, "Select a pilot project" may be one of the items. If that is one of special interest to the attending group we will focus on identify steps necessary to or guidelines on how to make that selection.

Stop interacting with the customer!
(...until you know the safety rules.)
Tuesday July 26, 2005 1:30-3:00pm
Zhon Johansen, Acadyn
Jeff Grover, Symantec
Abstract: Pivotal to all agile methods is the notion that customers work closely with the development team. Regardless of the excellent customer interaction techniques you've learned elsewhere, you will not be successful until you have established a working relationship. As with any relationship, things can go wrong. In this peer to peer session, we will learn to navigate the pitfalls in customer interaction. Endowed with a few simple guidelines, techniques, and knowledge you and your budding agile team will have the courage to be more involved with customers.

Achieving Closure:
Best Practices for Ending the Iteration
Tuesday July 26, 2005 3:30-5:00pm
Jeff Nielsen, Digital Focus
Dave McMunn, Digital Focus
    Jeff Nielsen
Abstract: Agile software teams face some common problems in doing iterative/time-boxed development. While coaching such teams, we have encountered the following types of challenges with ending the iteration successfully.
  • How do you enforce a true "hard stop" for each iteration?
  • How do you get the entire project community aligned around the iteration "rhythm"?
  • How do you appropriately celebrate success and make progress visible to stakeholders?
  • How do you get the customer involved in truly "steering" the development effort and providing meaningful feedback?
  • How does hands-on user acceptance testing fit into the iterative schedule?
We have found that specific end-of-iteration activities can be established and structured that address all of these issues. We are interested in sharing our ideas and in hearing how others have overcome similar problems.

Technical Retrospectives    
Tuesday July 26, 2005 3:30-5:00pm
Richard J. Watt, ThoughtWorks, Inc.
David Leigh-Fellows, ThoughtWorks, Inc.
Abstract: The goal of the Technical Retrospectives is to help the team build a set of common models that can be used to improve their collective understanding of the current design of the system - it is a learning exercise. We do this through various low-fidelity collaborative exercises that encourage us to externalise our internal models of the software, and to explore the differences that may exist between our understandings - we do this at the end of each iteration. An additional benefit we have found is that the documentation produced from this exercise gives us a historic snapshot record (a time-series animation, of sorts) of the design decisions made by the team, and allow us to reflect and reason about why the system design evolved to its current state - useful to current team members and also those that will join later in the life of the software.

Wednesday AM July 27, 2005
Agile Thinking Workshop    
Wednesday July 27, 2005 9:00-10:30am
Tobias Mayer      
Abstract: An "Agile Thinking Workshop" can be used at any level in an organization to introduce Agile principles. It provides participants with an opportunity to explore new ways of thinking and behaving and to experience, through a variety of different activities the Agile dynamics of self-organization, visibility and emergence. Using a number of different approaches, and relying strongly on experiential learning techniques this kind of workshop provides a self-directed learning experience which fosters an Agile mind-set and prepares participants for the Agile challenge.
The "Agile Thinking Workshop" Workshop at Agile 2005 will allow facilitators, or potential facilitators to experience first-hand a set of experiential exercises that they may find useful to introduce into their own organizations, to enhance existing Agile training. The workshop itself will emerge from the input of its participants. It is not formulaic. There may be an output; that too will be determined by the participants. The focus however is on process, not product.

Hiring an Agile Tester  
Wednesday July 27, 2005 9:00am-12:30
Anko Tijman, Ordina, The Netherlands
Lisa Crispin, Fast401k, USA
    Lisa Crispin
Bio: Lisa Crispin has been a tester on agile teams which develop web-based applications since 2000. Previous to that, she has long experience testing and programming on more traditional teams. You can often find Lisa at agile- and testing-related conferences, user group meetings and seminars in the U.S. and Europe, helping people discover good ways for agile teams to do testing, and for testers to add value to agile teams. She co-authored Testing Extreme Programming (Addison-Wesley, 2002) with Tip House. She contributes articles related to agile testing to magazines and newsletters such as Better Software, Methods and Tools, Agile Times and Novatica. Find out more about Lisa's work (and see pictures of her miniature donkey friends) at http://lisa.crispin.home.att.net.
Abstract: Your agile team wants to hire a tester. But there aren't a lot of folks out there calling themselves 'agile testers'. There are plenty of talented testers out there who don't know anything about agile development. How do you find them? When you're hiring a tester for an agile team, what skills, characteristics and experience should you look for? Where should you look? How do you determine if a candidate has the right attitude and mindset, let alone the skills your team needs to add? What questions do you ask in phone screening? What interview questions identify a good fit for your team? In this workshop, participants will work in groups and all together to identify where to look for potential 'agile' testers, what to include in the job posting, how to screen and interview, and other tips to finding the right person to join your team wearing a 'tester' hat.

Extreme Teams Game    
Wednesday July 27, 2005 11:00am-12:30
Erik Meade      
Abstract: It can be difficult to demonstrate how multiple agile teams can work together, in this tutorial participants will learn how to play and lead the Extreme Teams Game. The Extreme Teams Game is a simple game that requires nothing more than pens, index cards, and a bit of preparation to demonstrate the impact of changing communication and feedback between multiple agile teams working together. Past, present, and possible future team interactions will also be discussed.

Thursday AM July 28, 2005
Tools for Acceptance Testing    
Thursday July 28, 2005 9:00am-12:30
Bret Pettichord, ThoughtWorks
Timothy Wall
Abstract: Frequent iterations make automating acceptance tests especially important to agile teams, yet many struggle to make this a reality. Commercial tools often seem designed for more traditional divisions of labor. In this workshop we will explore the tools that agile teams have used, successfully or not, for automating acceptance tests. Are there common characteristics to successful tools? Are there commercial tools that are well-suited to agile teams?
We encourage participants to come ready to share their stories about tools they've used on agile projects. We expect to hear from users of Fit, HttpUnit, QuickTest, Abbot and many other tools.
This workshop will result in a report summarizing the views and experiences of the participants, and any patterns or trends that emerge.
Logistics: Participants will be encouraged to write experience reports in advance of the conference. These will be published on a website. Participants who have submitted reports will be given priority in the discussion. The workshop will use the LAWST-method of facilitated discussion.

Agile Embedded Software Workshop    
Thursday July 28, 2005 9:00am-12:30
James Grenning, Object Mentor      
Abstract: Embedded software has its own set of challenges like limited resources, timing constraints, safety concerns, and custom IO as well as all the classical problems with software development. The goal of this workshop is to bring together experienced embedded software developers, manager and customers. Those using agile techniques and those thinking about it are welcome.

We would like to hear your experiences and plans. Come prepared to discuss your challenges and the creative agile solutions. What results are you getting? Has agile improved your delivery? Has agile improved your reliability? Has agile improved your maintainability? Is it too soon to tell? Do you have any metrics? We would like to collect effective practices, discuss solutions to embedded development problems, and hear about attendees experiences.

Maybe you are considering adopting agile techniques for your embedded software development team. What issues are you trying to solve? What are the challenges in your organization?

Experienced attendees are encouraged to write up a list of the practices they are using and the results they have achieved. Attendees evaluating agile methods should bring their goals, concerns and hopes.

Thursday PM July 28, 2005
Test Driven Development and Beyond  
Thursday July 28, 2005 1:30-5:00pm
Dave Astels, Independent Consultant
Brian Marick, Independent Consultant
    Brian Marick
Abstract: Test Driven Development is becoming a mainstream practice. However, it is a step along the way, not a final destination. This workshop will explore what the next steps and side paths are, such as Behavior Driven Development, Example Driven Development, Story-Test Driven Development.

Leadership in Extreme Programming  
Thursday July 28, 2005 1:30-5:00pm
Kent Beck
Steve Freeman
Dale Emery
Lowell Lindstrom
    Kent Beck
Abstract: Nobody said that XP was going to be easy, just effective. Anyone who is involved in applying XP will encounter obstacles that tests their abilities to deliver code and create an effective organisation, and some of the ideas in XP contradict conventional wisdom about software development. The growing number of books offer guidance but an outside, human perspective can also be helpful.

In this workshop, a team of expert practitioners will offer practical advice on how to address the issues you are facing when applying XP. The format is to consider real-life examples from the participants, to talk about what we would do in these situations, and discuss the principles behind the actions. The goal is to help the participants to be more effective in response to their "leadership moments" as they apply XP. The practitioners are either managers who have applied XP, or consultants who have converted many different organisations to XP.

The workshop will be kept small to encourage open discussion so, if you'd like to join in, please drop a brief note describing your situation to WK12@m3p.co.uk, or contact Steve Freeman during the conference.

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!