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:

Intro to Agile 2005
Sunday July 24, 2005
The goal of this track is to introduce attendees to a wide variety of agile topics to help them know how to best spend the rest of their time at the conference. Most topics are intentionally kept very short (45 minutes) so that presenters have time to cover only the basics. The intent, for example, is that someone attending a 45-minute session on test-driven-development will know whether that is a topic worth further time investment at the conference. A developer may walk away thinking yes, and then find a suitable session or open space topic; a manager may leave with sufficient knowledge to talk intelligently about what TDD is but may not feel compelled to spend further conference time on that subject.
Introduction to Agile Software Development
Sunday July 24, 2005 1:30-5:00pm
INTRO1 Room 1
Hubert Smits      
Abstract: : In this talk Hubert Smits provides a broad introduction to concepts of agile software development and agile methods. The talk is based on his experience as an agile coach and Certified Scrum Master. Concepts that are known from waterfall or plan-driven development are transformed to an agile perspective. Examples are release and iteration planning, progress reporting, meeting formats and scaling projects from 10 people teams to 300 people teams. The session will be interactive and following agile principles: there is more value in responding to change than following a plan.

Engineering Practices of Agile Teams
Sunday July 24, 2005 1:30-5:00pm
INTRO2 Room 2
Agile Requirements with User Stories by Gerard Meszaros
Release and Iteration Planning by Mike Cohn
Agile Project Management by Jim Highsmith
Acceptance Testing with FIT and FitNesse by Rick Mugridge & Ward Cunningham
Abstract:
This session will present short introductions to four practices of agile teams. First up will be Gerard Meszaros, a partner at Clearstream Consulting and author of Effectiveness of Automated Testing. Gerard will discuss Agile Requirements with User Stories. User stories are a lightweight approach to requirements gathering that shift the focus from written documents to conversation and help projects be agile from their inception. Next up will be Mike Cohn of Mountain Goat Software and author of User Stories Applied and the upcoming Agile Estimating and Planning. Mike will be discussing Release and Iteration Planning, which are important skills for answering questions such as when will the product ship, in what order should we build features, and how much can we commit to? Next will be Jim Highsmith, author of Agile Project Management, Adaptive Software Development, and other books. Jim will present on how Agile Project Management supports reliable innovation. The final session will be presented by Ward Cunningham and Rick Mugridge. Ward is a consultant with C2 and the inventor of FIT, the Framework for Integrated Test, along with many other things such as wikis, Extreme Programming, and CRC cards. Rick Mugridge is an associate professor at the University of Auckland and is the co-author (with Ward) of Fit for Developing Software. Rick and Ward will be showing how to perform Acceptance Testing with FIT and FitNesse, two related and widely acclaimed, open source tools.

Intro to Agile 2005
Monday PM July 25, 2005
Agile Development Methodologies  
Monday July 25, 2005 1:30-5:00pm
INTRO3 Room 1
Jean Tabaka, Scrum
Bob Martin, Extreme Programming
    Bob Martin
Abstract:
Firstly Jean Tabaka, agile coach with Rally Software, will introduce Scrum. Her story is based on her experience as a Scrum Master, Facilitator and Agile Coach. She will take you through the core of Scrum: the customer ownership of the planning process, monitoring the delivery progress through daily stand-up meetings and simple reporting, and finally the iteration review. Jean expects to publish her book on Facilitation in Agile Projects in the autumn. Following Jean with an exploration of Extreme Programming is Bob Martin. 'Uncle Bob' is known as co-author, with James Newkirk, of XP in Practice, and author of Agile Software Development: Principles, Patterns, and Practices. Bob will cover the 12 practices that build up the XP software development method and share his experience as an implementer of the method.

More Practices of Agile Teams  
Monday July 25, 2005 1:30-5:00pm
INTRO4 Room 2
Project Automation by Mike Clark
Test Driven Development J.B. Rainsberger
Agile Model Driven Development (AMDD) by Scott Ambler
Agile Database Techniques by Scott Ambler
J.B. Rainsberger
Abstract:
The four speakers for this afternoon take you through four more practices that are widely used in the agile community. Mike Clark, author of Pragmatic Project Automation, starts the session with Project Automation, a practice that provides agile teams with the required support for their short development cycles. Mike wrote the online JUnit Primer and developed JUnitPerf, an open source collection of JUnit extensions for performance and scalability testing. Test Driven Development has moved from one of the 12 XP practices into a practice that is widely accepted in agile development teams. Joe Rainsberger, author of JUnit Recipes, and founder and president of Diaspar Software, highlights and demonstrates this practice. The afternoon closes with an introduction by Scott Ambler into Agile Model Driven Development (AMDD) and Agile Database Techniques. Scott is the well-known author of such books as Agile Modeling, The Object Primer, and Agile Database Techniques.

 
 
 
 
 
 
Invited Talks
Thursday July 28, 2005
The Secrets of Leading from a Position of no Power  
Thursday July 28, 2005 9:00-10:30am
INVITE1  
   
Abstract: At some point while deploying Agile concepts within your organization, you will find that you need to make changes in areas not under your control. You know what needs to be altered, but you don't have the authority to make those improvements.
At this point, are you blocked? Will your Agile movement go no further? Are all the benefits of Agile to be lost?
Not in the least! Actually the most powerful and successful way of install lasting change is from a position where you do not have the authority over that change.
To proceed, you need to use some simple techniques where you effectively lead from a position of no power.

Commoditizing Agility  
Thursday July 28, 2005 11:00am-20:30
INVITE2  
Joshua Kerievsky, Industrial Logic     Joshua Kerievsky
Bio: Joshua Kerievsky is the founder of Industrial Logic, a company that specializes in Extreme Programming. After a decade of programming at a Wall Street bank, he founded Industrial Logic in 1995 to help companies practice successful software development. Kerievsky has programmed and coached on small, large, and distributed XP projects since XP's emergence. He recently pioneered Industrial XP, an application of XP tailored for large organizations. Kerievsky has written XP articles in Extreme Programming Examined and Extreme Programming Perspectives and has recently authored the 2005 Jolt Productivity award winning book, Refactoring to Patterns.
Abstract: Many organizations can't afford quality, enterprise-wide transitions to agility. The costs are simply too high in dollars or time. As a result, organizations have settled for watered-down transitions that fail to realize the true potential of agility. To dramatically lower the cost of agile transitions, we must commoditize agility. Join Joshua Kerievsky as he explores the strategies, tools and collaborations necessary to help agility succeed on a grand scale.

 
 
 
 
 
 
Vendor Presentations 2005
Agility without Borders
Why should agile methods be restricted to small, co-located teams?
   
Tuesday July 26, 2005 Morning
VP1 - Valtech  
Tim Snyder      
Abstract: Over the last few years, the software development community at large has come to recognize the value of agility. Agile methods such as XP, SCRUM and others have proven to be a most effective catalyst to *better software, sooner*. And while we're still relatively early in the adoption curve, there seem to be limitations in sight. Not limitations in the sense of how effective agility can be, or even to what kind of problem can it be applied. This limitation is much more insidious - it's a restriction of who can apply it or where they can apply it. Differences aside, several agile methods and their pundits agree: 'agile software development begins with developers and customer in one room'. No such statement exists in the Agile Manifesto, but two passages from that infamous decree seem to support the idea of co-location as prescribed by the most popular agile methods. But why must this be? Such a limitation seems to preclude attempting agility in a multi-site or globally distributed team. Most agilites would agree and perhaps suggest "better to do your project with a smaller scope and a smaller, co-located team". But in these days of globally distributed business we find very real situations of globally distributed customers. Recommending a co-located team may not be feasible or even logical when considering other factors. So what then? Are we confined to experience the benefits of agility only when working with a co-located team? The Manifesto states that "business people and developers must work together daily throughout the project" and "the most efficient and effective method of conveying information to and within a development team is face-to-face conversation". Why must the requirement of face-to-face communication be tied so tightly to only one solution: co-location? Indeed, agile methods can and should be utilized by multi-site teams, offshore development projects, open source, and all forms of projects co-located and distributed alike. This discussion recounts one company's experience applying agility to globally distributed teams. Come hear and see what worked, what failed and what work-arounds made it possible to distribute agility to global teams.

Integrated lifecycle tools and process guidance
Visual Studio 2005 Team System
   
Tuesday July 26, 2005 Morning
VP2 - Microsoft  
Bindia Hallauer      
Abstract: Visual Studio 2005 Team System is an extensible lifecycle tools platform that significantly expands the Visual Studio product line and helps software teams collaborate to reduce the complexity of delivering modern service-oriented solutions. This approach increases team productivity and project predictability by integrating software development life cycle tools at the UI level, the data level and in the project context at the process level. This session covers using Visual Studio 2005 Team System and innovative techniques from the new software development processes, MSF for Agile Software Development and MSF for CMMI Process Improvement.

VP3 - ThoughtWorks

"Tooling to Scale Software Agility:
How to enable critical project visibility and coordination for distributed Agile teams
 
Tuesday July 26, 2005 Morning
VP4 - Rally Software  
Ryan Martens     Ryan Martens  
Abstract: As larger, distributed development teams adopt Agile practices they often find themselves lacking the team coordination and project visibility required to reliably deliver software in rapid, fully-tested iterations.
Scaling agile practices beyond the co-located team presents several challenges. Ad-hoc tools or heavy-weight project management systems simply do not provide the real-time communication and coordination required for the distributed software team to reap the benefits of agile practices. Additionally, the productivity of global teams suffers without a common understanding of how to set project priorities and objectively measure the team's progress.
In this session, Ryan Martens, founder and president of Rally Software will discuss Rally's experience in scaling the enterprise project visibility that distributed Agile teams need to be more responsive to fast-changing business priorities and new customer opportunities.

"Showcasing" Agile Development: An Adoption Strategy for Large Organizations  
Tuesday July 26, 2005 Morning
VP5 Digital Focus  
Jeff Nielsen, Chief Scientist
Dave McMunn, Agile Practice Lead
    Jeff Nielsen  
Abstract: Many large organizations could benefit from adopting some form of agile software development. However, larger companies typically face significant organizational barriers to the type of change that agile adoption mandates. Without some evidence that the benefits will outweigh the costs in their environment, these organizations are hesitant to begin experimenting with agile practices in a significant way.

In our work over the last several years with large companies, we have developed a successful technique for addressing this situation which we call "showcasing." Showcasing is essentially the outsourcing of a project to an independent group that can model and demonstrate the agile approach while assuming the responsibility for successful project completion. Showcasing sets up a situation where the client can see and experience the benefits of agile development while minimizing the organizational risks associated with introducing a new process.

In this session, we will cover the showcasing technique, and discuss our successful use of showcasing as a first step towards agile adoption with several Fortune 500 companies. Attendees will leave with a greater understanding of showcasing's value as a tool in the agile change agent's arsenal.

Agile Transition    
Tuesday July 26, 2005 Morning
VP6 - Object Mentor  
     
Abstract: Object Mentor is the industry leader in transitioning enterprises, both large and small, to Agile Software Development. Our approach tackles the whole organization, including Executive Management, Project Management, Quality Assurance, Business Analysis, and Development.
This talk describes the concept of the Agile Transition, and how Agility, and the transition to Agility, can scale to both large and small organizations. We will also discuss the successes and failures we've seen.

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!