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
APM Track: This year's Agile United conference will feature an Agile Project Management track that includes tutorials, workshops, and papers that emphasize project management practices for both software and non-software projects. This track will give participants an opportunity to hear and discuss topics such as: APM basics, Release and Iteration Planning, Contracting, Management Issues, and the the "Declaration of Interdependence".

While the agile community seems to focus on software development, there have always been a significant number of agile practices that can be categorized as project management rather than software development practices. Adaptive Software Development, DSDM, and Scrum in particular have espoused project management-like practices. We say project management-like, because there has been ongoing debate within the agile community about whether or not project management (in the traditional sense), should be abandoned completely, or merely significantly reformed. This year's APM track should give everyone plenty of opportunity to contribute to this and other project management related debates.

The growing interest in APM is illustrated in part by the number of practitioners who have begun to write about agile project management. Ken Schwaber's "Agile Project Management with Scrum", Jim Highsmith's "Agile Project Management: Creating Innovative Products", Robert Wysocki's "Effective Project Management: Traditional Adaptive, Extreme," David Anderson's "Agile Management for Software Engineering," Doug DeCarlo's "Extreme Project Management", Rob Thomsett's "Radical Project Management," Sanjiv Augustine's "Managing Agile Projects (May)" and Mike Cohn's "Agile Estimating and Planning (August)" all attest to the growing interest in agile project management, not only within the software development community, but within the wider project management community also.

Many of the authors just mentioned and others will contribute to this years Agile Project Management track. Join us for a rousing round of presentations, debates, open space sessions, and hall-way chat sessions.
Testing Track: Where does a 'professional' tester fit into the agile picture? TTD is now fully accepted in the community. A developer practicing agile wouldn't think of coding without writing her test first. Customers have been given the role of defining the customer or acceptance level tests - those that prove the application works as expected. However, there is often a gap between those tests the developers write, and the tests that the customers write. This is where one place tester can add value.
Traditional QA/Test teams that have been practicing some form of waterfall methodology don't always function well in an environment where requirements / stories are changing on a regular basis. What can testers and teams do to make testing a part of the agile development process?
The testing track provides tutorials, workshops, and papers that will help answer some of these questions. People will share experiences and how they have overcome some of the obstacles.

Agile Project Management--Reliable Innovation  
Monday July 25, 2005 1:30-5:00pm
Jim Highsmith: Cutter Consortium     Jim Highsmith
Bio: Jim Highsmith is Sr. VP Agile Project Management Practice at Cutter Consortium. He is the author of Agile Project Management: Creating Innovative Products, Addison Wesley 2004; Adaptive Software Development: A Collaborative Approach to Managing Complex Systems, Dorset House 2000, and, Agile Software Development Ecosystems, Addison Wesley 2002. Jim is a recognized leader in the agile project management and software development movement. He has published dozens of articles including "The Agile Manifesto," co-authored with Martin Fowler, in the August 2001 issue of Software Development). He is coauthor of both the Agile Manifesto and the Declaration of InterDependence. Jim has worked with organizations worldwide to help them adapt to the accelerated pace of development in increasingly complex, uncertain environments.
Abstract: Symyx boasts that their process enables scientists to discover new materials at 100 times the speed and 1% of the cost of traditional research. Drug companies rapidly generate millions of compounds and then test them using ultra-speedy mass spectrometers. Alias Sketchbook Pro a graphics software package was completely planned and developed in two-week iterations. From materials to drugs to software, companies are relentlessly driving the cost of change out of their product development processes in order foster innovation. These projects are the realm of Agile Project Management (APM) which operates under a philosophy of Envision and Explore rather than Plan and Do.
APM focuses on quick starts, iterative exploration, delivering customer value, low-cost change, frequent feedback, and intense collaboration. APM excels on projects in which: new, risky technologies are incorporated; requirements are volatile and evolve; time-to-market is critical; and high quality must be maintained.
APM includes core agile principles, a project management framework, and specific practices. The framework phases are:
Envision - determining the product vision and project scope;
Speculate - developing a feature-based release, milestone, and iteration plan;
Explore - delivering tested features;
Adapt - reviewing the delivered results and adapting;
Close - concluding the project.
This APM presentation will also include a section on Enterprise Agile-getting across to executives what they can expect from agile projects and to agile developers and project managers how they can present agile in an "executive" friendly perspective. Sign up for this tutorial and explore the ideas and practices of APM.

Expressing Business Rules  
Monday July 25, 2005 1:30-5:00pm
Rick Mugridge, University of Auckland     Rick Mugridge
Bio: Rick Mugridge is the author, with Ward Cunningham, of /Fit for Developing Software/, Prentice-Hall, June 2005. He developed the /FitLibrary /as he explored ways of expressing business rules well under change. He has been teaching, coaching, consulting and researching into agile software development for some years. He runs his own company, Rimu Research, and is an associate professor at the University of Auckland.
Abstract: Learn how to express business rules as Customer tests, with a focus on expressing the business domain with clarity and brevity.

Tuesday 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.

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 develop a clearer understanding of what's involved in making the translation to Agile testing.

Wednesday July 26, 2005
Release and Iteration Planning for Agile Projects  
Wednesday July 27, 2005 9:00am-12:30
Mike Cohn, Mountain Goat Software     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: Planning is important even for projects using agile processes such as XP, Scrum, or Feature-Driven Development. Unfortunately, we've all seen so many worthless plans that we'd like to throw planning out altogether. The good news is that it is possible to create a project plan that looks forward six to nine months that can be accurate and useful. In this tutorial we will look at why traditional plans fail but why planning is still necessary even on agile projects. You will leave with a solid understanding of and experience at agile release planning and iteration planning. We will look at various approaches to estimating including unit-less points and ideal time. The tutorial will describe four techniques for deriving estimates as well as when and how to re-estimate. We will look at techniques to create a plan that dramatically improves the project's chances of on-time completion. Also discussed will be using velocity to track progress against the plan.

Scripting Web Tests    
Wednesday July 27, 2005 9:00am-12:30
Bret Pettichord - Thoughtworks
Paul Rogers - Wireless Matrix
Abstract: This workshop is a hands-on introduction to automated testing using Ruby, Watir and a web-based application, all of which are open-source. It presumes no prior knowledge with these tools. It allows key issues related to automated acceptance testing to be raised in a natural environment

Thursday July 28, 2005
A Project Manager's Survival Guide
to Going Agile
Thursday July 28, 2005 9:00am-12:30
Michele Sliger - Author
Alicia Yanik- Author
Abstract: When software development project teams move to Agile methodologies, they often leave project managers behind. Traditionally trained project managers are confused as to what their new roles and responsibilities should be in an environment that no longer needs them to make stand-alone decisions. This tutorial focuses on re-defining the job of project manager, and the new duties of the program management office. Special emphasis is placed on the shift to servant leadership, with its focus on facilitation and collaboration. Attendees should leave not only with a better understanding of what changes they need to make professionally, but also with clear guidance as to how to make these changes and achieve their goals.

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.

Meeting the Agile Leadership Challenge  
Thursday July 28, 2005 1:30-5:00pm
Diana Larsen, FutureWorks Consulting
Pollyanna Pixton, Evolutionary Systems
    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: Many leaders facing the challenge of adapting to their role on agile projects find methods from the field of organizational development methods especially useful. This tutorial covers how several of the most successful of these methods work and how each assists the agile process. Strategies to implement these tools will be discussed and practiced.

How to integrate a Test/QA Team
into an Agile Development Environment
Thursday July 28, 2005 1:30-5:00pm
Janet Gregory, Securac Inc      
Abstract: When we think agile testing, we generally think embedded tester working closely with the development and customer team helping to identify acceptance tests, sometimes coding, sometimes using a tool such as FIT. However, there are cases where a test team needs to have some independence. This tutorial will demonstrate how your test / QA team can work closely with the development team yet maintain their individuality. Large systems require full system regression testing, deployment testing, load testing, etc., in an environment that is similar to a customer's site. Multiple versions of a product require testing and support. When people think about agile projects, they usually think about small projects that a single tester or two can work with the developers and complete all the testing needed.

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!