<?xml version="1.0" encoding="UTF-8"?>
<sessions type="array">
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Despite what you may have heard, analysis is still an important aspect of projects done in an agile manner.  Teams still need to understand what they are delivering in what order.  The trick is to how to utilize traditional analysis techniques without introducing the corresponding waste that can be experienced with those techniques.  In this session, we introduce Feature Injection and demonstrate how it combines traditional analysis techniques and the agile technique Behavior Driven Development to identify the business value delivered by a project without introducing analysis paralysis.

</description>
    <duration type="integer">90</duration>
    <id type="integer">185</id>
    <presenters>Kent McDonald, Chris Matts</presenters>
    <room>Columbus IJ</room>
    <stage-id type="integer">6</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Feature Injection A Gentle Introduction</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Agile Project Management (APM) addresses the challenges of embracing change, encouraging innovation, and delivering continuous customer value through a set of agile principles and practices. 



The session will present the conceptual framework of agile methods, how agile processes are Envision-Evolve rather than Plan-Do, stories from agile projects both small and large (600 people) and from different domains such as software and medical instruments, and how the &#8218;&#196;&#250;flow&#8218;&#196;&#249; of an agile project differs from more traditionally managed projects.



</description>
    <duration type="integer">90</duration>
    <id type="integer">409</id>
    <presenters>Jim Highsmith</presenters>
    <room>Grand Ballroom B</room>
    <stage-id type="integer">12</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Agile Project Management&#8212;Innovation in Action </title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>There are quite a few good tools available for developers who are interested in writing more expressive tests.  These cover a broad spectrum from unit testing and mocking frameworks to executable requirements platforms.  But sometimes in our excitement for learning new tools we overlook the most useful tool of all...the language features of our chosen programming language.  In this session we will get back to basics by exploring how you can write more expressive tests using the language features of Java, the framework features of JUnit, and the practice of Behavior Driven Development.</description>
    <duration type="integer">90</duration>
    <id type="integer">432</id>
    <presenters>Rod Coffin</presenters>
    <room>Grand Ballroom C North</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Back to Basics - Writing Expressive Tests Without All The Wizardry</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Have you ever been told to multitask&#8218;&#196;&#236;working on so many projects simultaneously you don&#8218;&#196;&#244;t know where to start or what to do next? Or, have you ever felt so pressured by your organization that you asked your staff to multitask?



Multitasking happens when leaders don&#8218;&#196;&#244;t set direction for themselves and other people. When leaders decide which projects people work on in what order&#8218;&#196;&#238;the project portfolio&#8218;&#196;&#238;they set the stage for success. But those decisions are not easy.

We will see what a portfolio is, what it is and isn&#8218;&#196;&#244;t, and we&#8218;&#196;&#244;ll explore how to make  collaborative decisions.

</description>
    <duration type="integer">180</duration>
    <id type="integer">508</id>
    <presenters>Johanna Rothman</presenters>
    <room>San Francisco</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Increase Your Capacity and Finish Projects: Manage the Project Portfolio</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>A huge quality-centered activity in Agile teams is defining **&#8218;&#196;&#250;done-ness&#8218;&#196;&#249;** as it relates to end of iteration or sprint deliverables. How we frame our team work goals, and measure their outcomes,  plays an immense part in determining overall product quality and customer satisfaction. In this session, we examine the 4 levels of Done-ness when it comes to Agile Release Criteria:  





1.	Team Craftsmanship Patterns  

2.	Features &#8218;&#196;&#236; Complete  

3.	Iteration &#8218;&#196;&#236; Complete  

4.	Release &#8218;&#196;&#236; Ready  





and share examples and stories of how Product Owners should interact with their teams.

</description>
    <duration type="integer">45</duration>
    <id type="integer">776</id>
    <presenters>Bob Galen</presenters>
    <room>Crystal C</room>
    <stage-id type="integer">4</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Setting Agile-Centric Release Criteria</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Agile fails without executive leadership. Although pockets of Agile can flourish for a while, only executives have the power to make an entire organization change.



The agile community has tried to sell executives on Agile rather than involve them. This workshop involves participants in discovering and documenting patterns for Agile executives to use. It builds on our previously-presented CTO research.



This session is appropriate for executives with Agile experience and for gurus who commonly work with executives. Others should wait for the results.

</description>
    <duration type="integer">90</duration>
    <id type="integer">915</id>
    <presenters>James Shore, Diana Larsen</presenters>
    <room>Grand Ballroom A</room>
    <stage-id type="integer">3</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>The Agile CTO</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Being nearly agile has caused a number of new words to enter our vocabulary. They include &quot;mini-waterfaull&quot;, &quot;Scrum-but&quot;, &quot;XP'ish&quot;, &quot;w-agile&quot;, &quot;fr-agile&quot; and a host of others. While agility cannot be defined by a particular set of principles or practices, going down a particular agile path only part-way is almost always a recipe for an eventual disaster. This session will focus on exposing the 7 deadly sins that may apply: lack of customer voice, manual testing, never integrating, no incremental deliveries, no feedback loop, silo'd teams and unrealistic deadlines. Learn why each is deadly!</description>
    <duration type="integer">180</duration>
    <id type="integer">934</id>
    <presenters>Bob Hartman, Richard Lawrence</presenters>
    <room>Toronto</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>The 7 Deadly Sins of Almost Being Agile</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>If you&#8218;&#196;&#244;re a practicing Agilist who has tough questions about Agile methods, how they fit together, or how they can be more widely adopted in your organization, then this session is for you. This energy-filled workshop explores the central themes of Agile Project Leadership, why they work, when they don&#8218;&#196;&#244;t and why. Delegates are expected to come with their difficult questions about Agile. Answers will be explored and shared in a fun and interactive way. </description>
    <duration type="integer">90</duration>
    <id type="integer">998</id>
    <presenters>Ole Jepsen</presenters>
    <room>Regency D</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Only Dead Agilists Don&#8217;t Ask Questions</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Many an agile developer has gotten stuck in the AJAX mud when trying to develop Web 2.0 applications.  Google Web Toolkit (GWT) applications are written in Java and compiled to JavaScript.  This helps developers stay unstuck by leveraging the power of well-established Java tools and techniques.  Learn how GWT works with refactoring Java IDEs, supports Test-Driven Development with JUnit, and handles all the cross-browser JavaScript for you.</description>
    <duration type="integer">45</duration>
    <id type="integer">1211</id>
    <presenters>Daniel Wellman, Paul Infield-Harm</presenters>
    <room>New Orleans</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Agile AJAX: The Google Web Toolkit Experience</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This session will focus on the unique challenges companies face when using agile on projects that involve FDA governance: large company conservative culture, regulatory documentation, requirements tracing, and a bias towards waterfall development.



Skeptics argue that agile is best suited to small- and medium-sized companies and wrongly perceive agile as a limited, negating its use in the highly regulated corporate world.



In reality we will show you how we&#8218;&#196;&#244;ve successfully implemented agile in large sized companies operating in a highly regulated world.</description>
    <duration type="integer">90</duration>
    <id type="integer">1275</id>
    <presenters>J.R. Jenks, Tim Hughes</presenters>
    <room>Regency C</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Moving to Agile in an FDA Regulated Environment</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>No, you don't get to skip project planning. Brooke needs to know approximate cost and delivery date, and poor Padma need to know when the good stuff will start showing up. You yourself need to know dependencies and delays.



This is the shortest, fastest, easiest way I know to create a project plan. It's full name is &quot;&quot;Project Planning Jam Session&quot;&quot;, to indicate that all roles are present for the session, from sponsor to business person to designers and testers. Thanks to Jens Coldewey for first showing this to me in 1998 &#8218;&#196;&#236; it instantly improved the way our teams developed project plans.</description>
    <duration type="integer">90</duration>
    <id type="integer">1690</id>
    <presenters>Alistair Cockburn</presenters>
    <room>Grand Ballroom E</room>
    <stage-id type="integer">10</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Blitz Planning</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Agile adoption initiatives succeed and fail.  There is no agreement on why they do so.  The current focus for scaling Agile seems to be on modifying existing Agile practices, adding new ones, and getting the right toolset installed.  I&#8218;&#196;&#244;ve come to believe that the main reason for the success of any Agile adoption effort are the individuals, their skills and their personalities.  All other aspects of Agile are of secondary importance.



In this talk I will share several individual skills and mental models that are necessary for successful scaling.



</description>
    <duration type="integer">90</duration>
    <id type="integer">2024</id>
    <presenters>Amr Elssamadisy, Ashley Johnson</presenters>
    <room>Regency A</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Scaling Up by Scaling Down: A (re)Focus on Individual Skills</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Clear definitions of Role, Task and Authority are essential when people assemble to do work. 



Unclear definitions of these items leads to all sorts of waste. 



Scrum's very clear Roles and associated Tasks and Authority are a big part of what makes actually Scrum 'tick'. 



A Boundaries 'collection' is an attribute of the Role, Task and Authority 'objects'.  This session deconstructs Role, Task &amp; Authority in terms of associated Boundaries. Note that boundaries can come in many forms, including: boundaries of time, boundaries in terms of access to resources, etc. 









</description>
    <duration type="integer">45</duration>
    <id type="integer">2153</id>
    <presenters>Dan Mezick</presenters>
    <room>Columbus GH</room>
    <stage-id type="integer">11</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Boundary, Authority, Role and Task : BART Analysis Applied </title>
    <updated-at type="datetime">2009-08-13T08:21:34Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Agile software development means collaboration, and increasingly this collaboration will cross boundaries of organizational and national culture.  The session introduces models of culture and explores the impact of cultural differences on software development processes and methods, especially those involving the practices common in agile development. The session will be organized around two collaborative games that illustrate how cultural differences interact in the software development workplace. Our aim is better understanding of the issues and how to manage them.

</description>
    <duration type="integer">180</duration>
    <id type="integer">2237</id>
    <presenters>Robert Biddle</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Agile Cross-Culture with Games</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>It's easy to speak of test-driven development as if it were a single method, but there are several ways to approach it. In our experience, different approaches lead to quite different solutions.



In this workshop, we're not trying to decide which approach is best. Rather, we'll use concrete examples to explore   

 

 * What goes into the moment of decision when a test is written?

 * How do you think about the problem you're trying to solve?

 * What strategies or techniques help you write the first few tests?



This workshop is targeted at TDD/BDD Practitioners. </description>
    <duration type="integer">180</duration>
    <id type="integer">2257</id>
    <presenters>Naresh Jain, Michael Feathers</presenters>
    <room>Grand Ballroom F</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Styles of TDD: First Tests</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Instead of a whole new set of modeling techniques, agile development requires a new way of applying good modeling methods like UML, ER, and UCD, in an incremental, iterative, and evolutionary (Agile) manner. This tutorial introduces an agile software modeling process that strikes the right sufficient-up-front and just-in-time balance. Participants are introduced to a blend of domain modeling, usability modeling, data modeling, and architectural design. We will utilize appropriate UML, ER, and UCD methods in an agile fashion to help limit technical debt, and increase design quality.</description>
    <duration type="integer">180</duration>
    <id type="integer">2352</id>
    <presenters>Ken Collier</presenters>
    <room>Plaza Ballroom B</room>
    <stage-id type="integer">12</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Just Enough Design: Modeling With Agility</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Is it possible to SCRUM the development of a large software system with contributing teams spread out over three cities, five partners, six sites, and a six hour time difference? It started with vague and ambitious objectives and was built on bleeding edge technologies (grails, flex). By all rights we should have fallen flat on our faces. But a year after its dubious beginning, our project continues. Join us as we present the good, the bad and the ugly of distributed team projects.



  </description>
    <duration type="integer">45</duration>
    <id type="integer">2417</id>
    <presenters>Erik LeBel, Isabelle Therrien</presenters>
    <room>Plaza Ballroom A</room>
    <stage-id type="integer">8</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>From anarchy to sustainable development: SCRUM in less than ideal conditions.  </title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Are you a developer or product manager working without a user experience specialist on your team? Would you like to learn how to quickly explore interaction design concepts? And guide your team in making good UX decisions? This hands-on workshop will teach you to use napkin sketches and whiteboard drawings to make real UX improvements. You'll walk away with experience designing on-the-fly using personas, scenarios and a few ideation and sketching techniques. No special skills required - if you've ever doodled you can learn to design on-the-fly. Be prepared to have fun and participate.





</description>
    <duration type="integer">90</duration>
    <id type="integer">2535</id>
    <presenters>Amanda Willoughby</presenters>
    <room>Columbus KL</room>
    <stage-id type="integer">16</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Designing on-the-fly: ideation &amp; sketching for non-designers</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Self-organization of human beings is a tricky thing. Agile coaches are constantly challenged with how to motivate/persuade/trick their teams into  doing things, without telling them what to do, but there is very little information or training on this topic. Allowing a team to self-organize along the lines of &#8218;&#196;&#250;oh well, they&#8218;&#196;&#244;re all adults, they&#8218;&#196;&#244;ll figure it out&#8218;&#196;&#249; is just as irresponsible as reverting to the command-and control school of management. This tutorial presents an approach utilizing leading-edge research and techniques from social complexity science and team dynamics.</description>
    <duration type="integer">180</duration>
    <id type="integer">3056</id>
    <presenters>Joseph Pelrine</presenters>
    <room>Regency B</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Coaching self-organizing teams</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Why is testing so slow?  Why is testing taking so long?  We've done lots of things to speed up testing, but we still face this time crunch when we get to the end of the iteration; then we find out from the field that there are problems that we didn't anticipate.  In this workshop, we'll gather familiar patterns that slow down testing, and discover a few more in the process--and maybe we'll find that the slowest parts of testing have nothing to do with testing at all.  If you have problems that you'd like to solve or solutions that you'd like to offer, come along.</description>
    <duration type="integer">90</duration>
    <id type="integer">3080</id>
    <presenters>Michael Bolton</presenters>
    <room>Grand Ballroom D North</room>
    <stage-id type="integer">14</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Why Is Testing So Slow?  </title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This session is an explanation and demonstration of Deep Democracy, primarily aimed at coaches interested in learning new techniques. Deep Democracy--originated by Arnold Mindell--maintains that a well functioning group is dependent on all the voices, positions and views in the group being heard and valued. We will start with the definition, origins and applications of Deep Democracy, then conduct a Large Group Process in which all can directly experience the power of this approach. In our debrief, we will harvest the wisdom of the group, and explore practical uses in Agile team situations.</description>
    <duration type="integer">90</duration>
    <id type="integer">3201</id>
    <presenters>Michael Spayd</presenters>
    <room>Crystal A</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">25</time-slot-id>
    <title>Deep Democracy: A Radical Approach to Hearing from Every Voice</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Many facets of Agile apply to simple principles of human nature. Because Agile is so effective in the workplace, I began applying Agile principles (after pleading with my wife) to managing the chaos of our family. For over 2 years now, my wife, 4 children, and I have been using Agile practices to manage our own home life.



The evolved methodology in our home has been discovered over two years of modification using Lean principles while working on weekly iterations.



This is a fun topic with actual learning points for managers learning to accommodate unique personalities in the workplace.</description>
    <duration type="integer">45</duration>
    <id type="integer">1080</id>
    <presenters>David Starr, Eleanor Starr</presenters>
    <room>Columbus GH</room>
    <stage-id type="integer">11</stage-id>
    <time-slot-id type="integer">26</time-slot-id>
    <title>Agile Practices at Home: Iterating with Children</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Participants will discuss the use of virtual worlds with agile teams. Examples will be interjected from an agile project at State Farm where a virtual world was used to collaborate with team members in multiple locations.  The session will end with a brief demo.



The discussion will include:  

1. Necessary qualities for collaboration to occur

2. Obstacles to achieving this on a distributed agile team 

3. Using a virtual world on an agile project

4. Best practices for leveraging a virtual world

5. State Farm's use of virtual world environments with agile teams

</description>
    <duration type="integer">45</duration>
    <id type="integer">1650</id>
    <presenters>Keith Voos, Ami Hileman</presenters>
    <room>Plaza Ballroom A</room>
    <stage-id type="integer">8</stage-id>
    <time-slot-id type="integer">26</time-slot-id>
    <title>Using Virtual Worlds for Distributed Agile</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Learn how the Corporate Internet Solutions group at Nationwide Insurance found creative ways to manage the competing and vague priorities of corporate silos by incorporating ideation into the portfolio pipeline.   As the connection point between otherwise disconnected corporate entities, the Product Owner team adapted the Scrum process to better manage 17 dependent projects, reluctant internal business partners, and suspicious methodologists, by articulating clear Pre-Discovery activities,  RITE usability testing,  scenario planning, and kanban in the quest for continuous flow.  </description>
    <duration type="integer">45</duration>
    <id type="integer">2884</id>
    <presenters>Kevin Fisher, arlen bankston</presenters>
    <room>Crystal C</room>
    <stage-id type="integer">4</stage-id>
    <time-slot-id type="integer">26</time-slot-id>
    <title>From Cradle to Sprint:  Creating a Full-Lifecycle Request Pipeline at Nationwide</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>All respectable software craftsmen make efforts to keep their coding claws sharp.  And solely working 9-5 on business applications will dull one's whit.  In this session we will broaden your coding horizons with some Ruby Kata and test your skills will some Ruby Sparring.  



</description>
    <duration type="integer">45</duration>
    <id type="integer">2961</id>
    <presenters>Micah Martin</presenters>
    <room>New Orleans</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">26</time-slot-id>
    <title>Ruby Kata and Sparring</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>In today's Agile development environment, UI testing is still very much done the old way.  We still see long scripts that are easily broken and impossible to maintain.  By applying modern software development techniques like test first development, refactoring, and pair programming we can seek to make better tests that are less fragile and more likely to discover defects in code.  In this session we will demonstrate the techniques listed above and discuss how they can be applied to UI testing.  The demonstration will use a combination of fitnesse and SWAT (an open source web UI testing tool).</description>
    <duration type="integer">45</duration>
    <id type="integer">91</id>
    <presenters>Michael Longin, Christopher Taylor</presenters>
    <room>Regency D</room>
    <stage-id type="integer">14</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Applying modern software development techniques to automating the web UI</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>As the world becomes increasingly &#8218;&#196;&#250;flat&#8218;&#196;&#249;, organizations are seeking out operational and cost efficiencies by leveraging distributed teams. These distributed teams are a common constraint on most technology projects today.  To continue wide-spread adoption, Agile projects must find ways to thrive in distributed environments. The Ambassador Model is a proven, effective approach to building highly productive distributed and off-shore agile teams.  Complementing this model are &#8218;&#196;&#250;carrier pigeons,&#8218;&#196;&#249; a metaphor for tools (technology and practice) used to overcome the challenges of distance. </description>
    <duration type="integer">45</duration>
    <id type="integer">376</id>
    <presenters>Giora Morein</presenters>
    <room>Plaza Ballroom A</room>
    <stage-id type="integer">8</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Ambassadors and Carrier Pigeons - A Model for Effective Distributed Agile Teams</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Agile coaches often need to distinguish when people &quot;do&quot; an agile practice versus &quot;really understand&quot; that practice. This workshop will help coaches develop a tool, mapping agile practices, or more specifically, behaviours people exhibit when using an agile practice, to a learning model. The learning model of choice for this workshop is the Dreyfus Model of Skill Acquisition. We will also discuss how to apply this tool to better communicate and set goals with teams &quot;going agile&quot;.</description>
    <duration type="integer">90</duration>
    <id type="integer">471</id>
    <presenters>Patrick Kua, Elizabeth Keogh</presenters>
    <room>Crystal A</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Climbing the Dreyfus ladder of agile practices</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>In this session, we invite CI tool vendors to give a short demonstration of the best features of their tool. Each vendor will be given 10min to show off the best features of their software, with a further 5min of questions. 



This will allow CI users to quickly get a good grasp on the plethora of CI tools on the market, to help them find out about useful features of various tools that may help their CI implementation, and to learn about the practices that each tool encourages. 



It also helps CI tool vendors gauge the market, and improve the standards and features of all CI products.</description>
    <duration type="integer">90</duration>
    <id type="integer">572</id>
    <presenters>Tom Sulston</presenters>
    <room>Grand Ballroom E</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>CI vendor cage-fight!</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>One of the barriers to wider adoption of TDD is that it is best taught from within a team, and the technical challenges of writing tests frequently thwart those looking to teach themselves. This session will be a live demonstration of Test Driven Development in Java, using Eclipse and JUnit, aimed at those new to TDD and looking to learn. Audience members will be encouraged to follow along on their own laptops as we walk through common scenarios that frequently discourage new TDDers, and demonstrate some techniques for overcoming them in a live coding session.</description>
    <duration type="integer">90</duration>
    <id type="integer">713</id>
    <presenters>Ben Rady</presenters>
    <room>Grand Ballroom B</room>
    <stage-id type="integer">12</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Test Driven Development in Java: Live and Uncensored</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>How do agile teams account for backlog items that do not fit the user story paradigm? Aside from user stories, what are ways you can represent product needs? Teams struggle with incorporating quality attributes (sometimes called &#8218;&#196;&#250;quality of service&#8218;&#196;&#249; requirements), external interfaces, design and implementation constraints, and team or technical &#8218;&#196;&#250;stories&#8218;&#196;&#249; into their backlogs. Without these items, you will not build the right product, or build it right. This tutorial will introduce you to ways that agile teams represent these nonfunctional requirements and other items in the backlog.   </description>
    <duration type="integer">90</duration>
    <id type="integer">742</id>
    <presenters>Ellen Gottesdiener</presenters>
    <room>Columbus IJ</room>
    <stage-id type="integer">6</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Beyond User Stories: Identifying Missing Links in Your Product Backlog</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This presentation applies Agile thinking to critical aspects of strategy and execution at a time of uncertainty and disruption. The essential point is simple and logical: Agile values and principles are indivisible. To succeed, they must be applied not just to R&amp;D, but also to customer and company, simultaneously. This requires reconfiguration of customer relationships, employee policy, software development, and the relationship that binds the three. The resulting paradigm shift could lower the cost of software and produce prosperity similar to the one induced by ultra-cheap oil in the 50&#8218;&#196;&#244;s.</description>
    <duration type="integer">90</duration>
    <id type="integer">1141</id>
    <presenters>Israel Gat</presenters>
    <room>Crystal B</room>
    <stage-id type="integer">10</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Role of the Agile Leader in Reconfiguring the Business </title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Nonfunctional Testing has always been ignored and neglected because no one is sure what to do with it. Agile environments make Nonfunctional Testing more difficult as people try to invent ways to make it conform to whatever they are using. The goal of this workshop is to define methods to integrate and maneuver nonfunctional testing into agile environments. We will discuss the current concepts and determine the How, What and Why of Nonfunctional Testing. </description>
    <duration type="integer">90</duration>
    <id type="integer">1270</id>
    <presenters>Jeremy Brown</presenters>
    <room>Grand Ballroom D North</room>
    <stage-id type="integer">14</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Nonfunctional Agile Testing &#8211;How and Where to start?</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Priorities shifted twice a week. My favorite lightweight practices were all too heavy. Facebook thinks I might be a spammer. On November 5, the code became totally worthless. It was the best project I've been on!



Come and hear about a project that was too strange for normal, comfortable agile methods. I hope you can learn from my experience, and make sure you are bringing the right tools and processes to your next project. Focus on the principles of agile (communication, simplicity, feedback, courage) instead of the practices (CI, pairing, iterations, etc).

</description>
    <duration type="integer">45</duration>
    <id type="integer">1326</id>
    <presenters>Andy Slocum</presenters>
    <room>Grand Ballroom A</room>
    <stage-id type="integer">3</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Agile's Too Slow: Developing a Facebook App For the Obama Campaign</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>James Shore (coauthor of The Art of Agile Development) and Rob Myers of Agile Institute help you examine the role of metrics on Agile teams.  We take a broad survey of metrics being used on Agile projects, both traditional and innovative, and look at the value and dangers to the success of the team.  We look at how the simple act of measuring, itself, can be harmful, and when it is well-justified.  Metrics at every level of the Agile organization will receive scrutiny:  Measuring value, team performance, progress, quality, and even code design attributes will be taken into consideration.</description>
    <duration type="integer">90</duration>
    <id type="integer">1574</id>
    <presenters>Rob Myers, James Shore</presenters>
    <room>Regency A</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Metrics in an Agile World</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>As Agile practitioners, a great deal of our time is focused on having targeted, directed impact.  But sometimes we miss opportunities to repurpose our efforts into syngergistic, many-pronged effects.  Not multi-tasking -- multi-EFFECTing, from one piece of effort.  This talk will explore this topic, both in theory and in practice.  We will examine a particular client case-study, where two disparate 6-person developer teams, with minimal pairing and TDD experience, were developed into highly-productive &quot;gelled&quot; teams, through &quot;Group Pair Programming&quot; -- 6 individuals, 1 workstation.</description>
    <duration type="integer">45</duration>
    <id type="integer">1866</id>
    <presenters>Ken Kolchier</presenters>
    <room>New Orleans</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Exploring Synergistic Impact Through Adventures In Group Pairing</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Welcome to the world of Visual Management! Task boards, post-its, mind maps, burndown charts, kanban boards, lava lamps... information visualization techniques and the visual workplace play a fundamental role in creating visibility and helping build transparency and trust among Agile teams. Come to this workshop to experience in person the value of Visual Management, and help cooperatively come up with the ultimate task board!</description>
    <duration type="integer">90</duration>
    <id type="integer">1898</id>
    <presenters>Xavier Quesada Allue</presenters>
    <room>Columbus GH</room>
    <stage-id type="integer">11</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Visual Management for Agile Teams</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Understanding the forces driving and restraining the adoption of Agile in your organization is key to your success.  This audience participation workshop creates two teams, the Drivers and the Restrainers and has them present the forces at work in the most original and humorous way possible.



This results in a lot of fun and learning.



The workshop will be led by two experienced coaches to bring out the subtle details of the forces and lead the discussion on how to improve the success given the forces at work.</description>
    <duration type="integer">90</duration>
    <id type="integer">2473</id>
    <presenters>Rod Claar, Douglas Shimp</presenters>
    <room>Regency C</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>May the Forces Be With You, Exploring the Forces Driving and Restraining Agile</title>
    <updated-at type="datetime">2009-08-13T08:20:45Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Agile methods are frequently associated with iterations, incremental development, and adding one thin slice of functionality at a time. We have mantras such as YAGNI and &#8218;&#196;&#250;The Simplest Thing That Could Possibly Work.&#8218;&#196;&#249; We promote refactoring. These concepts are, however, harder to apply to UI-intensive application code than faceless back end systems. In this tutorial, we will incorporate ideas from user-centered design, discussing how we approach user-facing agile application development at [Reaktor](http://www.reaktor.fi/en) through a mixture of presentations and hands-on exercise.</description>
    <duration type="integer">90</duration>
    <id type="integer">2804</id>
    <presenters>Lasse Koskela</presenters>
    <room>Columbus KL</room>
    <stage-id type="integer">16</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>GUIDe for Saving Face: Developing Killer GUIs with Agile Methods (90min)</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Tools and practices as subscribed by the XP methodology are reasonably well known and used by the majority of agile project teams. As agile teams become more mature, so does their thirst for tools to push them to the next level of productivity. In this talk, we will walk through a number of project tools used by some teams we work with. In some cases, we will explain how we hacked tools that you may already be using to make them more efficient or useful. In other cases, we'll describe new tools designed by teams we have been working with who are trying to move to the next level. </description>
    <duration type="integer">90</duration>
    <id type="integer">2840</id>
    <presenters>Craig Smith, Paul King</presenters>
    <room>Grand Ballroom C North</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Agile Tool Hacking - Taking Your Agile Development Tools To The Next Level</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Successful software products deliver a set of features your customers' value and will pay for. To determine the correct priority and presentation of features, it's important to understand the different behaviors and attitudes that exist in the audience for your product. Ethnographic field research is very valuable, yet can be expensive, time consuming and require skilled researchers. In this hands-on workshop, you will learn how to use collaborative play with customers to discover how they think and what they value, and use this intelligence effectively with your agile teams. </description>
    <duration type="integer">90</duration>
    <id type="integer">3047</id>
    <presenters>Lane Halley, Luke Hohmann</presenters>
    <room>Crystal C</room>
    <stage-id type="integer">4</stage-id>
    <time-slot-id type="integer">27</time-slot-id>
    <title>Beyond features: How to listen to your customers and learn what they really need</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This report will focus on challenges we faced maintaining hundreds of builds that encompass tens of thousands of assertions.  Over the past five years our development team, at Iowa Student Loan (ISL), leveraged TDD and Continuous Integration to develop software.  Tests and builds quickly accumulate and maintaining them can be like herding cats.  We were often tempted to neglect these tests in the pursuit of developing new functionality.  We would like to share strategies that helped us maintain our automated test investments.</description>
    <duration type="integer">45</duration>
    <id type="integer">806</id>
    <presenters>David Kessler, Tim Andersen</presenters>
    <room>Regency D</room>
    <stage-id type="integer">14</stage-id>
    <time-slot-id type="integer">28</time-slot-id>
    <title>Herding Cats: Managing Large Test Suites</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>How do you sell an agile project? 

Most customers expect to buy software by time-and-material or by fixed-price-fixed-scope contracts based on detailed requirements.  These models can not create a fertile environment for collaboration between customer and supplier.  In this presentation, we will report on our experiments with commercial contracts  that supports an agile development process, based on concrete examples of  win-win contract types. We will outline the different aspects of these contracts, as well as experiences creating and delivering software solutions under these contracts. </description>
    <duration type="integer">45</duration>
    <id type="integer">859</id>
    <presenters>Lars Thorup, Bent Jensen</presenters>
    <room>Grand Ballroom A</room>
    <stage-id type="integer">3</stage-id>
    <time-slot-id type="integer">28</time-slot-id>
    <title>Experiments with Agile Contracts in the Real World</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>A major challenge for software organizations is creating software that can continue to adapt and change over time, a code base the team can live with. This session reviews the lessons learned from CruiseControl, a popular tool for continuous integration. CruiseControl is an open source success story not only because it has had over 400,000 downloads but also because it has successfully contributed to by over 200 different people. For practitioners who are tired of brittle code that must be discarded and rewritten CruiseControl provides valuable lessons.</description>
    <duration type="integer">45</duration>
    <id type="integer">1335</id>
    <presenters>Jeffrey Fredrick, Paul Julius</presenters>
    <room>New Orleans</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">28</time-slot-id>
    <title>Creating Habitable Code: Lessons in Longevity from CruiseControl</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Can my large, geographically distributed, systems program benefit from agile development methods?  Absolutely.  This talk presents real-world experiences applying agile practices to large, systems projects with a high degree of governance.  The practices discussed are technical (continuous integration, test-driven development, user stories) and non-technical (communication, welcome changing requirements, frequent collaboration).  And it presents several challenges we experienced while scaling agile practices and changes we hope to make on future programs.</description>
    <duration type="integer">45</duration>
    <id type="integer">2898</id>
    <presenters>Harry Koehnemann</presenters>
    <room>Plaza Ballroom A</room>
    <stage-id type="integer">8</stage-id>
    <time-slot-id type="integer">28</time-slot-id>
    <title>Experiences Applying Agile Practices to Large Systems Development</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Continuous Integration is a key practice in the agile toolkit.  The practice is pretty simple - when checkins occur, some process is run against the codebase. This usually includes compilation and unit tests, but could include all sorts of things. 



The panel of CI experts host discussion of the audience's problems, questions, concerns and ideas about how to make best use of CI.



We aim to draw together the experience of the panel with the enthusiasm and fresh eyes of the participants to share our collective CI knowledge with those having issues with their CI implementations. </description>
    <duration type="integer">90</duration>
    <id type="integer">266</id>
    <presenters>Tom Sulston</presenters>
    <room>Grand Ballroom B</room>
    <stage-id type="integer">12</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>How to be really awesome at Continuous Integration.</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>When it is achieved together, the combined benefits of both Agile and Offshore software development, can be multiples greater than either approach alone. During this interactive session, we will simulate a distributed project with some participants being onsite and the others offshore. With 4 teams of upto 8 people each, this game will draw out learning around the challenges of Distributed Agile and different methods to communicate successfully on such projects. The rules of the game help illustrate how to deal with travel, different timezones, delayed communication and other such hurdles.</description>
    <duration type="integer">180</duration>
    <id type="integer">401</id>
    <presenters>Sumeet Moghe, Jonathan McCracken</presenters>
    <room>Plaza Ballroom A</room>
    <stage-id type="integer">8</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>The Distributed Agile Game</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>There are plenty of good tools out there - the trick is to get them all to play together well. In this session, we will go through the full process of setting up an automated software development infrastructure, from code changes and version control right through to automated deployment to staging and production. We will go through the key steps involved in automating a typical Java project using Maven, Hudson and a large cast of other supporting tools. We will see not only how to automate the build itself, but also how to improve code quality, manage releases, and improve team communication.</description>
    <duration type="integer">180</duration>
    <id type="integer">482</id>
    <presenters>John Smart</presenters>
    <room>Grand Ballroom E</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Java Power Tools - getting it all together</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This tutorial teaches how to use a simple 5 component model to identify and prioritise stories on a project.

The five elements to the model are:

 Business Objectives (value and goals)

 Business Actors (who does this)

 Business Events (when does this happen)

 Business Process (what needs to be done)

 Business Objects (what do we do it with - information and/or tools)

The tutorial introduces the model as a tool for understanding current (&quot;&quot;as is&quot;&quot;) and future state (&quot;&quot;to be&quot;&quot;), identifying the stories for the future state and  teaches the participants how to use it on a mock project.



</description>
    <duration type="integer">90</duration>
    <id type="integer">768</id>
    <presenters>Shane Hastie</presenters>
    <room>Columbus IJ</room>
    <stage-id type="integer">6</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>A Business Value Focused Model for Story Identification &amp; Prioritisation</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This tutorial introduces the concept of playtesting - a central component of software development processes in the game industry - which is the process through which players inform the ongoing evolution of a game's design. The importance of playtesting is derived from the fact that in the game industry, the quality of the software produced is measured in terms of the user's subjective experience of it. In the tutorial the participants explore the benefits, pitfalls and relevance of playtesting for their business, be it a game company or any other software development operation.</description>
    <duration type="integer">90</duration>
    <id type="integer">879</id>
    <presenters>ron carmel, Orit Hazzan</presenters>
    <room>Grand Ballroom D North</room>
    <stage-id type="integer">14</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Playtesting in the Game Industry </title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This tutorial will provide you with a proven process for how to prioritize a backlog for profit. It will debunk the mistaken theory that you can prioritize a backlog for ROI and provide concrete examples of how to structure backlogs to meet the needs of key stakeholders, align your backlog to corporate strategy, and show how your release will drive profit. By following the process described in this tutorial, agile product managers / product owners can create backlogs that support the company&#8218;&#196;&#244;s longer-term goals as well as short-term development needs.</description>
    <duration type="integer">180</duration>
    <id type="integer">951</id>
    <presenters>Luke Hohmann</presenters>
    <room>Regency A</room>
    <stage-id type="integer">6</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Prioritizing for Profit</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This game is designed to teach/learn/experiment how to use Kanban.  In this session, everyone will play it and learn the way how Kanban works, effective use, and how to teach their colleagues &quot;&quot;Kanban.&quot;&quot;



I have designed this game to teach new members the Kanban.  Attendees form teams and will have a set of task cards. They will build a Kanban Board from the tasks and 'commence' on the project.  Using dice, the project might finish by the time or not, as in reality.  An important part of the game is how teams must face problems happening by accident.

</description>
    <duration type="integer">180</duration>
    <id type="integer">970</id>
    <presenters>Tsutomu Yasui</presenters>
    <room>Plaza Ballroom B</room>
    <stage-id type="integer">12</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>The Kanban Game</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Cucumber is a new acceptance testing (AT) tool that works with RSpec. Already popular in the Ruby community, this tutorial shows you how to use Cucumber to test drive Java applications, when you combine Cucumber and RSpec with JRuby.



We'll also discuss Cucumber *vs.* FitNesse and using RSpec *vs.* JUnit. You'll learn tips for writing good acceptance tests. Half of the time will be devoted to a hands-on exercises, where you will test drive a simple Java application using Cucumber.



Bring your laptop (or a pair partner with one), with the latest Cucumber, RSpec, and JRuby installed. 



</description>
    <duration type="integer">180</duration>
    <id type="integer">1276</id>
    <presenters>Dean Wampler, Aslak Helles&#8730;&#8719;y</presenters>
    <room>Grand Ballroom C North</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Acceptance Testing Java Applications with Cucumber, RSpec, and JRuby</title>
    <updated-at type="datetime">2009-08-13T08:18:35Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>A participatory workshop where coaches can share their experiences in coaching agile teams in hostile environments, what they did to avoid the pain, and how they turned toxic organizational inertia and attack against itself or circumvented the same to realize more agility.  The session will be facilitated and will be oriented around capturing tricks, tips, and techniques, but will also allow for some sobbing and frustration and ranting.  Epic fails are definitely welcome.   The most sought after stories and ideas will be those which use the opposition's own strength to advance the effort.</description>
    <duration type="integer">90</duration>
    <id type="integer">1431</id>
    <presenters>Lisa Moore, Christian Gruber</presenters>
    <room>Regency B</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Coach Aikido: Lessons and support for abused coaches in hostile environments.</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>The use of metaphorical games as a strategy for adopting an agile culture has shown to be weak because most of trainers don&#8218;&#196;&#244;t know the principles of changing beliefs and values of a human mind. The Neuro-Linguistic Programming (NLP) Logical Levels of Learning and Change (LLLC) is a powerful framework to be considered when we need to challenge skeptical and analytical minds in traditional software development environments. This tutorial presents the structure of the LLLC and a set of three statistical games that can be used as a seed for an agile training or a movement into the agile culture.</description>
    <duration type="integer">90</duration>
    <id type="integer">1587</id>
    <presenters>Luiz Claudio Parzianello, Rafael Prikladnicki</presenters>
    <room>Crystal A</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Logical Levels and Statistical Games: A Powerful Strategy for Agile Adoption</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This experience report is about a professional services company in Egypt that was able to deliver a project 25% ahead of schedule after the team had adopted agile. The interesting part about this experience report is this company is using the SAMI Roadmap to adopt agile. The SAMI roadmap is a 5-step value based roadmap to help companies adopt agile. In this experience report we want to present the SAMI and show the agile community the real tangible business benefits (early delivery) realized from using this roadmap to adopt agile.</description>
    <duration type="integer">45</duration>
    <id type="integer">2021</id>
    <presenters>ElMohanned Ahmed, Ahmed Sidky</presenters>
    <room>Toronto</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>25% Ahead of Schedule and just at &#8220;Step 2&#8221; of the SAMI</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Deploying to servers has replaced shrinkwrapping CDs for delivering software. In the internet enabled era, the application is the infrastructure.



The basis of all Agile engineering practices is reproducibly building from source code. If software is delivered on servers, and those servers can't be reproducibly deployed from bare metal to working services, how Agile can you be?



Continuous Integration is great, but what about Continuous Delivery! What are you waiting for?



This talk will outline innovations in tools, process, planning and culture emerging at the front lines.</description>
    <duration type="integer">90</duration>
    <id type="integer">2151</id>
    <presenters>Andrew Shafer, Paul Nasrat</presenters>
    <room>Grand Ballroom A</room>
    <stage-id type="integer">3</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Agile Infrastructure</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>A glimpse behind the scenes of the production of a weekly show like Saturday Night Live offers an incredible example of a team of people who have agility in their DNA. Writers, actors, set designers, producers, studio execs, etc. all have a single-minded focus on delivering an exceptional quality show every single week. Slipping the schedule is not an option. Customer satisfaction (viewer ratings) are the central measure of success. The production team must collaborate and adapt to unexpected challenges every single week. This interactive session provides examples of highly adaptive behaviors.</description>
    <duration type="integer">90</duration>
    <id type="integer">2349</id>
    <presenters>Ken Collier</presenters>
    <room>Regency D</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Agility Night Live - TV Sketches and Project Stories</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>As the internet proliferates beyond the PC to myriad devices - from iPhone to smart-phone - anyone delivering digital products deals with complexity: varying form factors, cultural differences and contexts of use. In this workshop we explore the implications of this complexity, discover through collaborative experience where the pain points lie, and identify strategies for dealing with them. We conclude that the unique challenges faced in the design and development of mobile applications benefit from agile software development and its ability to cope with such complexity.</description>
    <duration type="integer">90</duration>
    <id type="integer">2562</id>
    <presenters>Tom Hume, Johanna Hunt</presenters>
    <room>Columbus KL</room>
    <stage-id type="integer">16</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Many paths to the top of the (mobile) mountain</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Currently, the iPhone is the hottest platform for mobile development, with everyone wanting to develop on it.  Test Driven Development is a proven technique for developing high-quality software, but isn't encouraged by the iPhone development platform.  Open Source developers have stepped in, creating Unit Test Libraries for the iPhone.  We'll show you how to get started, run your first tests, put tests in your build, and touch on advanced techniques like mock objects and dependency injection.  Perfect for the Agile Developer looking to get started on iPhone.</description>
    <duration type="integer">90</duration>
    <id type="integer">2591</id>
    <presenters>Eric Smith, Eric Meyer</presenters>
    <room>Grand Ballroom F</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Test Driven Development on the iPhone</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Dr. Rico will provide an experience report introducing agile methods to a master's degree program in software engineering at a large online university. He will describe the goals, objectives, strategy, and implementation plan for transitioning the program from traditional to agile methods. He will describe the adoption challenges he faced from both the faculty and students who were steeped in traditional methods. He will describe how three teams of 15 students in four time zones successfully built three fully functional e-commerce websites, lived to tell about it, and became agile converts.</description>
    <duration type="integer">45</duration>
    <id type="integer">2592</id>
    <presenters>David Rico</presenters>
    <room>Regency C</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Use of Agile Methods in Software Engineering Education</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Agile Methodology has been widely accepted in the private sector for a number of years and has caught the attention of government program managers as a process for software development designed to make work more efficient. Chief Technology Officers (CTO) and Chief Architects of the Lockheed Martin programs will provide an overview of the challenges experienced by the program&#8218;&#196;&#244;s leadership when balancing between Agile and traditional methodologies used on Government programs.</description>
    <duration type="integer">45</duration>
    <id type="integer">2669</id>
    <presenters>Min-Gu Lee</presenters>
    <room>San Francisco</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Executive Leadership Challenges for Agile Adoption</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Teams who have been practicing Agile, Lean and Scrum are finding that as they are maturing their practices, they appear to be Agile on the surface but never quite seem to get the benefits promised. This tutorial will teach attendees how to effectively analyze problems to find systemic fixes underlying the symptomatic causes, and grow into learning and problem solving organizations. Examples from many diverse industries will also be presented and discussed and breakout sessions will allow attendees to try their hand at creating a value stream and identifying issues. Tom Poppendieck presenting.</description>
    <duration type="integer">180</duration>
    <id type="integer">2921</id>
    <presenters>gabrielle benefield, Tom Poppendieck</presenters>
    <room>Crystal B</room>
    <stage-id type="integer">10</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title> How to identify and fix problems using Value Stream analysis and A3 thinking</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Values can be powerful forces when applied to a small company. From their seed can come personalized principles and practices. By starting with agile values, and then making them your own, you can instill a creative force for change and adaptation necessary for success. Traditional agile practices become personalized through iterative improvement measured against these values. Different teams can create new practices that are applicable to their discipline. Most important, they frame every conversation and decision, enabling rapid execution and shared vision.</description>
    <duration type="integer">45</duration>
    <id type="integer">3043</id>
    <presenters>Paul Ingalls, Troy Frever</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Growing an Agile Culture from Value Seeds.</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Agile is taking off in the marketplace, and agile processes are the norm for helping IT departments deliver great software... but what about the business?  What about the product manager?  What about the software itself?  What can we do to ensure that we build the RIGHT software with the RIGHT features... the features that will make us the MONEY!  

This session will introduce the concepts of Business Value Metrics and Customer-Based Design a simple formula to help Business Stakeholders evaluate their application feature by feature to ensure they are building the MONEY (honey.)  

</description>
    <duration type="integer">180</duration>
    <id type="integer">3088</id>
    <presenters>Marina Chiovetti, Julian Boot</presenters>
    <room>Crystal C</room>
    <stage-id type="integer">4</stage-id>
    <time-slot-id type="integer">29</time-slot-id>
    <title>Build me the Money, Honey!</title>
    <updated-at type="datetime">2009-08-13T08:18:16Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This talk presents an evolutionary roadmap for architects to support Product Owners, Scrum Teams and ScrumMasters through Agile Architecture Teams. Based on coaching and practical experience, a pattern of growth in Architectural teams has emerged as Agile scales up in an organization. This talk describes the possibilities when Agile Architects transform into a collaborative team and find better ways to extend Agile Principles, Agile Architecture foundations, and Scrum based workframes in adding value.



</description>
    <duration type="integer">45</duration>
    <id type="integer">343</id>
    <presenters>Mike Dwyer</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">30</time-slot-id>
    <title>The impact of Agile Architect Teams in Scaling Enterprise Efforts</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>When most people think of the phrase &quot;Agile won't work here&quot; they think of resistance to adopting agile. There are teams and situations, however, that are truly challenging even to the most dedicated agile adherents. During this sharing experience, I plan to take you on a &quot;cook's tour&quot; of a dozen or so teams that had difficulty adopting agile, even after the team was sold on the benefits. Filled with humorous stories, how these teams succeed (or failed) is an object lesson for us all.</description>
    <duration type="integer">45</duration>
    <id type="integer">658</id>
    <presenters>Daniel Markham</presenters>
    <room>Columbus GH</room>
    <stage-id type="integer">11</stage-id>
    <time-slot-id type="integer">30</time-slot-id>
    <title>Agile won't Work: Implementing Agility in Non-Standard Teams</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Could an executive team be happy using Scrum? Yes, it&#8218;&#196;&#244;s possible! Picture the scene: executives of strategic departments (financial, HR, IT, sales &amp; marketing, production, etc.) being part of a cross-functional executive team&#8218;&#196;&#182;an executive Product Owner prioritizing an Executive Product Backlog  that helps the team to follow the company&#8218;&#196;&#244;s vision. What are the main challenges of an executive ScrumMaster?  In this session I will show a real case of a Brazilian company that uses Scrum in their executive team. </description>
    <duration type="integer">45</duration>
    <id type="integer">1081</id>
    <presenters>Alexandre Magno</presenters>
    <room>Toronto</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">30</time-slot-id>
    <title>An Executive Scrum Team</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>What happens when the CIO decides the dev team needs to adopt agile practices and the dev team nods their heads but don't plan on doing zilch? 

It is time to leverage those fancy shmancy influencing skills we agilists are so famous for.  We'll cover new fun tactics that have not yet been explored in some of the prevalent literature.  All fresh information from the field.</description>
    <duration type="integer">45</duration>
    <id type="integer">2902</id>
    <presenters>Anda Abramovici</presenters>
    <room>Regency C</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">30</time-slot-id>
    <title>The Ogre and The Wimp: Clever Influencing Tricks - Help the Most Reluctant Teams</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>We will describe our journey from a process where design/planning work was performed away from development to one where small cross-functional Feature Teams self-organized to complete design, planning, and construction within the same sprint. Each team member is involved in getting READY, planning, executing and being DONE. The results we observed are an increase in team morale, more predictable results and accumulation of less debt, while maintaining a constant velocity. Our process is a deviation from the established approach where upfront work needs to be ready before starting a sprint. </description>
    <duration type="integer">45</duration>
    <id type="integer">3060</id>
    <presenters>Andre Frank</presenters>
    <room>San Francisco</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">30</time-slot-id>
    <title>Feature Teams - Collaboratively Building Products from READY to DONE</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>In this talk Ola Ellnestam explains the differences between push and pull in a software development context.



The difference between push and pull is described and discussed. Followed by examples from other industries. Mentioning Toyota and Dell. After this rather brief introduction follows a simple and easy to understand exercise.</description>
    <duration type="integer">45</duration>
    <id type="integer">400</id>
    <presenters>Ola Ellnestam</presenters>
    <room>Grand Ballroom B</room>
    <stage-id type="integer">12</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Push, Pull, What is the difference</title>
    <updated-at type="datetime">2009-08-13T08:17:59Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This talk discusses techniques that can be used to apply Agile practices to atypical technologies, and presents case studies on how to apply Agile practices to projects built with technologies including Teradata (Database), and MicroStrategy (BI). &lt;!--break--&gt;Most of the discussion around Agile is focused on traditional object-oriented development using technologies such as .NET, Java, and Ruby. It is important to realize, however, that the Agile practices are not technology specific, and many opportunities exist to apply these practices to projects that use other technologies as well.</description>
    <duration type="integer">90</duration>
    <id type="integer">494</id>
    <presenters>Scott Dillman</presenters>
    <room>New Orleans</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Applying Agile Development Practices to Atypical Technologies</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>How can mock objects help you design your system better? Want to know how mocking saved hours of work? We focus on establishing best practices based on examples with mock objects. We cover design of classes, using mock objects to understand and test interaction between objects of the system. By the end of the session it should become clear how mocking,when applied correctly helps with system design, improves testability by reducing cost of change. An explicit part of this session is dedicated to the Mocking top offenders. We talk with examples about bad usage of Mocks, and its consequences. </description>
    <duration type="integer">90</duration>
    <id type="integer">747</id>
    <presenters>Paulo Caroli, Sudhindra Rao</presenters>
    <room>Grand Ballroom F</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Mock Objects in Action</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Animal behaviors such as Swarming, Flocking &amp; Shoaling provide intriguing insights into how groups spontaneously form and interact. The natural world is full of rules, both simple and complex that enable groups of animals to function extremely efficiently. Looking at these examples, we can draw interesting parallels with the behavior of groups of people - and we can learn interesting things about the rules that we use when we work in teams. This presentation draws on extensive research on groups, both human and animal, and provides useful insights into how we can best organize ourselves.</description>
    <duration type="integer">90</duration>
    <id type="integer">800</id>
    <presenters>Tom Perry, Dhaval Panchal</presenters>
    <room>San Francisco</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>What Nature Can Teach Us About Building Great Teams</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>End-to-end tests appear everywhere: test-driven development, story-test-driven development, acceptance testing, functional testing, and system testing. They're also slow, brittle, and expensive. In this expert-level workshop, we will discuss why end-to-end testing is used, examine where and why it breaks down, and generate more effective solutions. We will spark ideas for participants to explore further on their own.



We will not be debating the premise (that end-to-end tests are problematic). This is an expert-level workshop and attendees will be expected to participate fully.</description>
    <duration type="integer">90</duration>
    <id type="integer">1010</id>
    <presenters>Arlo Belshee, James Shore</presenters>
    <room>Grand Ballroom D North</room>
    <stage-id type="integer">14</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Slow and Brittle: Replacing End-to-End Testing</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Inkubook.com came into existence in March 2008 when an existing software development and marketing organization received a new CEO and was immediately tasked with building an entirely different product. This report discusses the evolution from the existing Scrum process through four major changes as the team's process shifted to meet the team's goals and management's demands.  Focus will be given to the barriers benefits that the team perceived with each stage. Where possible, a discussion of the unintended consequences of the team's actions will be explored with specific examples.</description>
    <duration type="integer">45</duration>
    <id type="integer">1594</id>
    <presenters>Eric Willeke</presenters>
    <room>Toronto</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>The Inkubook experience: A tale of five processes</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>To enable the Agile Value &#8218;&#196;&#250;Courage&#8218;&#196;&#249;, we have to empower internal coaches, project managers, team leaders, and team members to change the organizations culture. 

Only a coach (or a manager / executive in his/her role as coach) is in the position to initiate and keep this process alive. 

Thus a coach has to be able to:



* make human systems transparent

* reduce or adjust complexity

* enforce dialogues and solutions

* set and enact clear goals

* build trust in the team and in the customer collaboration

* focus on sustainable decisions 

* clarify conflicts

</description>
    <duration type="integer">90</duration>
    <id type="integer">1793</id>
    <presenters>Thomas Walker, Werner Wild</presenters>
    <room>Regency B</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Courage 2.0 - &quot;How to Coach Culture Change&quot;</title>
    <updated-at type="datetime">2009-08-13T08:16:47Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Changing methodology in the midst of the high-risk project is a risky proposition.  At the University of Michigan we had several options:  spoon feed and implement as you go, make immediate and drastic changes, plan carefully to implement confidently and thoroughly.  



</description>
    <duration type="integer">45</duration>
    <id type="integer">1835</id>
    <presenters>Katarina Thomas</presenters>
    <room>Regency C</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Starting Agile implementation half way through the critical project</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>What happens when your organization practices Agile software development for many years? 

Well, you get pretty good at Agile: you are able to apply Agile with reducing effort on challenging projects. But there is another interesting side-effect which is that your people internalize Agile values, so much so that Agile becomes second-nature to everyone! 



In this photo tour, come see how a culture is infected with Agile thinking, you will see how we apply Agile to many activities like training- sessions, recruitment, staffing, office reforms, strategic decisions and more.

</description>
    <duration type="integer">45</duration>
    <id type="integer">1914</id>
    <presenters>Chirag Doshi</presenters>
    <room>Regency D</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>A peek into an Agile infected Culture  </title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>*&#8218;&#196;&#250;Tell me and I'll forget; show me and I may remember; involve me and I'll understand.&#8218;&#196;&#249;* &#8218;&#196;&#236; Chinese Proverb



Agile teams that rapidly learn and apply new-found skills become increasingly adept at embracing change and delivering value. Team members feel more fulfilled, motivated and valued. And they have way more fun!



In this session you will learn about agile learning! Learn to recognize learning moments and put in place effective learning patterns tuned to your team and context. Learn how to build and sustain an effective learning culture on your agile team.</description>
    <duration type="integer">90</duration>
    <id type="integer">2402</id>
    <presenters>Declan Whelan</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Learning is key to Agile success: Building a learning culture on your Agile team</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>What happens when you get Agilists together to build an organization within one of the most ill-reputed bureaucracies in the world? 



When the Project Management Institute chartered the PMI Agile Forum, it was a huge announcement. However, now the team had to deliver a fully functioning organization to support the Agile-minded members within PMI's membership...and do so on schedule and under budget. How do we build a business plan? How do we execute a marketing effort? How do we plan a launch event? Come see how this all-volunteer distributed virtual team extended PMI's reach using Agile.</description>
    <duration type="integer">45</duration>
    <id type="integer">2419</id>
    <presenters>Jesse Fewell</presenters>
    <room>Columbus GH</room>
    <stage-id type="integer">11</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Growing PMI using Agile</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Set-based design (also known as set-based concurrent engineering) offers a paradoxical way to make Agile teams even more effective by actively exploring multiple options. In this back and forth conversation between the presenters, we'll talk about the relationship between Agile, Lean ideas, and the Toyota approach to product development. We'll describe the specific mechanics of how you can get started with set-based design, and the benefits you can see. Finally, we'll dispel the notion that this is just another form of analysis paralysis.</description>
    <duration type="integer">90</duration>
    <id type="integer">2440</id>
    <presenters>Bill Wake, Jean Tabaka</presenters>
    <room>Grand Ballroom A</room>
    <stage-id type="integer">3</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Set-Based Design: Anti-Agile or Agile's Future?</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Human relationships are at the center of the Agile manifesto. Anything we do as coaches to allow humanity expression in our teams directly affects the individuals' ability to live the manifesto more fully. This immediately translates into better, more astonishing, creation-ability in teams, and a greater sense of accomplishment and fulfillment for the team members.  In this session, experienced coaches/trainers Lyssa Adkins and Tobias Mayer will introduce 'Powerful Questions' and share their personal experiences of coaching teams and individuals towards a more human-centric way of working.

</description>
    <duration type="integer">90</duration>
    <id type="integer">2444</id>
    <presenters>Tobias Mayer, Lyssa Adkins</presenters>
    <room>Crystal A</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Powerful Questions: Human-centric coaching</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>You're negotiating a project with a client or internal customer, but they balk when you don't present a fixed budget and a predefined list of requirements.  How do you convince them that the benefits of an Agile team outweigh a top heavy and fragile requirements document?  Based on Agile experience with government and commercial clients, we will discuss ways to make your customer feel comfortable with process changes that don't always result in the same set of documents they are used to.</description>
    <duration type="integer">45</duration>
    <id type="integer">2869</id>
    <presenters>Arin Sime</presenters>
    <room>Columbus IJ</room>
    <stage-id type="integer">6</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>How to sell a traditional client on an agile project plan</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Over the last several years, innovative UX practitioners working in agile environments have improvised and invented ways to include effective user experience practice inside agile projects.  This short talk describes many common emergent agile-ux practices.  Some of these practices are lighter weight versions of traditional techniques, while others are new inventions combining the best of UX rigor with a collaborative and pragmatic twist.   As a participant, you&#8218;&#196;&#244;ll leave with a buffet of useful UX techniques to add to or adapt your agile process. </description>
    <duration type="integer">45</duration>
    <id type="integer">2911</id>
    <presenters>Jeff Patton</presenters>
    <room>Columbus KL</room>
    <stage-id type="integer">16</stage-id>
    <time-slot-id type="integer">31</time-slot-id>
    <title>Agile User Experience Design Emergent Practices</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This talk summarizes the results of 4 years of industry surveys concerning the adoption and effectiveness of agile techniques.  Very often the reality is significantly different than the rhetoric presented in mailing lists, in articles, and even in books.  How effective are agile approaches compared to traditional approaches?  To iterative approaches?  Are people modeling?  Writing documentation?  Doing TDD?  How much co-location is actually going on?  How many organizations are really doing agile?  To what extent?  Come and find out answers to these questions and more.</description>
    <duration type="integer">45</duration>
    <id type="integer">263</id>
    <presenters>Scott Ambler</presenters>
    <room>Regency C</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">32</time-slot-id>
    <title>Agile by the Numbers: What People Are Really Doing in Practice</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Even teams with good skills, appropriate technologies, and posters of the Agile Manifesto on the wall can have trouble. Giving into temptation is often the cause. Guiding values are what keep us on the straight and narrow path in the face of temptation. Teams that have strong internalized values will stick to or invent good Agile practices while teams without them will drift into the ditch.



In this talk, I'll present what I think of as the most important guiding values:



* courage

* working software

* ease

* being reactive

* fast feedback

* naivet&#8730;&#169;

* visibility

* joy</description>
    <duration type="integer">45</duration>
    <id type="integer">444</id>
    <presenters>Brian Marick</presenters>
    <room>Columbus GH</room>
    <stage-id type="integer">11</stage-id>
    <time-slot-id type="integer">32</time-slot-id>
    <title>Eight Guiding Values</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>The off-shore model for IT services is held up as the most cost effective delivery model. As companies gain experience with the out-sourced model, it is becoming clear that there are serious flaws even using Agile methodologies.  

The presenter will directly compare the productivity metrics of off-shore distributed Agile teams with co-located Agile Teams.  Co-located teams are far more productive and cost effective even accounting for the relative lower resource cost.  Companies should be rediscovering co-located project teams as the paradigm for delivering real value for their IT projects.

</description>
    <duration type="integer">45</duration>
    <id type="integer">1098</id>
    <presenters>Beth Cohen</presenters>
    <room>Columbus IJ</room>
    <stage-id type="integer">6</stage-id>
    <time-slot-id type="integer">32</time-slot-id>
    <title>The Failure of the Offshore Experiment</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Success in adopting an Agile culture depends on the team's ability to adapt, while establishing common objectives/principles across the team. This case-study observes this theme via the lens of a project team at Liquidnet. The project's concept was actually originated by the UX team. Eventually, with an interdisciplinary team of 30, the vision became a reality. It wasn't until a major change in scope occurred when Liquidnet decided to bring an agile coach to facilitate process change. This experience report documents the team's experience integrating the Agile culture into their very own.</description>
    <duration type="integer">45</duration>
    <id type="integer">2712</id>
    <presenters>Lily Cho</presenters>
    <room>Columbus KL</room>
    <stage-id type="integer">16</stage-id>
    <time-slot-id type="integer">32</time-slot-id>
    <title>Adopting an Agile Culture</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>When we adopted agile we were not looking to reinvent our human resource policies, but our organization changed in fundamental ways that we did not predict.  Peers routinely provide feedback to each other on performance.  Team members schedule their own reviews.  Everyone on the team has an opportunity to work with clients.  Vacation schedules are submitted without regard to project delivery dates.  We have programmers who job share, and mothers bring their infants to work.  Come hear how adopting agile helped us become a three time winner of the Alfred P Sloan Award for Workforce Flexibility.</description>
    <duration type="integer">45</duration>
    <id type="integer">2738</id>
    <presenters>Clement &quot;James&quot; Goebel</presenters>
    <room>Regency D</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">32</time-slot-id>
    <title>How Agile has changed our Human Resources</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Plan an iteration - sounds pretty easy right? It can be easy using a well defined framework.

This sessions will cover the following:



- Owner or facilitator of the meeting

- When to hold the meeting

- Whom to invite

- Materials - please note that this session is not tool specific other than Sharpies and Sticky Notes! But the plan can be input into your tool of choice.

- Purpose

- Agenda

- Planning Data - what to bring to the planning meeting

- Output &amp; Deliverables  -

All contribute to the iteration planning meeting



A handout will be provided for future reference.



</description>
    <duration type="integer">45</duration>
    <id type="integer">2871</id>
    <presenters>Julie Chickering, Ken Clyne</presenters>
    <room>Grand Ballroom B</room>
    <stage-id type="integer">12</stage-id>
    <time-slot-id type="integer">32</time-slot-id>
    <title>Painless Iteration Planning</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>A series of cartoons depicts the terrible things that happen when agile practices aren't followed.  This session is valid for any persona, but especially for the product owner who will suffer when their product fails because they follow a process that isn't helping their team deliver!</description>
    <duration type="integer">45</duration>
    <id type="integer">3122</id>
    <presenters>Anda Abramovici, Tim Brown</presenters>
    <room>Toronto</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">32</time-slot-id>
    <title>A comical approach to project smells</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
</sessions>
