<?xml version="1.0" encoding="UTF-8"?>
<sessions type="array">
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description></description>
    <duration type="integer">90</duration>
    <id type="integer">5107</id>
    <presenters>Philippe Kruchten</presenters>
    <room>Plaza Ballroom A</room>
    <stage-id type="integer">13</stage-id>
    <time-slot-id type="integer">1</time-slot-id>
    <title>Agile Validation is Continuous and Collaborative: A Field Study of Agile Require</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 demonstration will show how the Scrum process and many XP/Agile practices can be implemented using Visual Studio Team System, Team Foundation Server, and the Conchango Scrum Process Template in a .NET development environment. The demonstration will follow a User Story from being added to the Product Backlog, through development during a Sprint, to deployment to production, and back again via a reported defect; covering the entire lifecycle cradle to grave.</description>
    <duration type="integer">90</duration>
    <id type="integer">89</id>
    <presenters>Tommy Norman</presenters>
    <room>Grand Ballroom E</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Implementing Scrum/XP Practices using Team Foundation Server</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 business analyst role seems conspicuously missing from most agile methods. Do agile methods make business analyst an obsolete role? Certainly not!  But how do you integrate what is sometimes portrayed as a plodding and documentation driven role into an agile project?  This tutorial provides participants practical guidance for how the business analyst integrates and collaborates with all members of the team. During this workshop the participant will learn how to construct and evolve an agile business analysis process that is appropriate for their specific project environment.</description>
    <duration type="integer">90</duration>
    <id type="integer">341</id>
    <presenters>Steve Adolph</presenters>
    <room>Columbus IJ</room>
    <stage-id type="integer">6</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Agile Grows up: The Agile Business Analyst</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>Most agile methodologies tend to assume that the team is co-located in a single team room. They give little guidance as to how to address team distribution although proven practices are starting to emerge within the community. The Microsoft patterns &amp; practices team has been experimenting with distributed teams for several years, mining proven practices from the community and experimenting them out on numerous agile projects. This talk summarizes those learnings and proven practices and gives examples of their application - both good and bad - within our teams.</description>
    <duration type="integer">90</duration>
    <id type="integer">447</id>
    <presenters>Ade Miller</presenters>
    <room>Grand Ballroom C North</room>
    <stage-id type="integer">8</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Distributed Agile Development: Experiments at Microsoft patterns &amp; 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>Different testing approaches are needed because quality has many aspects besides functional requirements, such as making sure the code is reliable and secure. How do you know you&#8218;&#196;&#244;ve done the kinds of testing and quality processes are necessary for your product, especially on an agile project? 



The Agile Testing Quadrants help you categorize tests and plan for different testing activities needed over the life of a project. It can be used by the team as a base for this common vocabulary about testing, and as a mechanism to start discussions and encourage collaboration.



</description>
    <duration type="integer">90</duration>
    <id type="integer">480</id>
    <presenters>Janet Gregory</presenters>
    <room>Grand Ballroom D North</room>
    <stage-id type="integer">14</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Using the Agile Testing Quadrants to Plan Your Testing 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> The Agile Alliance states that &quot;The Gordon Pask Award recognizes two people whose recent contributions to Agile Practice make them, in the opinion of the Award Committee, people others in the field should emulate.&quot; This panel brings together some of the previous winners so that they may share their contributions and help encourage others to participate in building the body of Agile knowledge. For the intermediate practitioner, it should reinforce the notion that as we practice Agile and learn how to adapt for the best outcome, sharing what we learn helps the whole community.</description>
    <duration type="integer">90</duration>
    <id type="integer">512</id>
    <presenters>Aaron Sanders, Jeff Patton</presenters>
    <room>Toronto</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>What makes this Agile ours? A talk with previous Gordon Pask Award winners.</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>Scheduling should be done independent of and orthogonal to workflow. In fact, you don&#8218;&#196;&#244;t have to create a schedule for a flow system. It will flow all by itself, and work will flow much faster and much more reliably than it could possibly follow a schedule. But take a closer look at that workflow: Just when you thought it was obsolete, the V model reappears. This talk will step through systems design, approval processes, and scheduling, development workflow, depolyment, from a completely different angle. </description>
    <duration type="integer">90</duration>
    <id type="integer">532</id>
    <presenters>Mary Poppendieck</presenters>
    <room>Grand Ballroom F</room>
    <stage-id type="integer">6</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Workflow is Orthogonal to Schedule</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 thinking about trying agile approaches?  Do you have an agile transition underway?  Is your team or organization trying to become agile, but been less than successful thus far?  A foundational implication &#8218;&#196;&#236; and the biggest potential roadblock &#8218;&#196;&#236; of the agile manifesto is culture change.



Therefore, to be successful with agile approaches and especially to scale them, you *must* go beyond agile technical practices and simultaneously tackle culture changes.  This session shows why this is so, introduces a simple culture model, and gives you an opportunity to try out a culture tool. </description>
    <duration type="integer">90</duration>
    <id type="integer">727</id>
    <presenters>Mike Russell</presenters>
    <room>Columbus KL</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Face culture or face failure</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 biggest risk to most projects is building the wrong product. Regardless of how fast your agile team becomes, nothing matters if you&#8218;&#196;&#244;re building the wrong product. 



In this tutorial we will look at both non-financial ways of both prioritizing product backlog items and choosing among competing project ideas. Included are relative weighting, theme screening, theme scoring, and Kano analysis. You will leave with hands-on experience in very practical ways to prioritize a product backlog.

</description>
    <duration type="integer">90</duration>
    <id type="integer">1217</id>
    <presenters>Mike Cohn</presenters>
    <room>Grand Ballroom B</room>
    <stage-id type="integer">4</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Prioritizing 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>Agility in Action&#8218;&#196;&#182; This session will introduce five interactive games that a facilitator can add to their toolkit for team and management training.  The games all illustrate the principles and dynamics that support Agility.  The rationale for this session is that people learn best by embodying the learning, rather than just receiving knowledge at a head level. All participants will be immersed in the games; there are no observers. At the end of the session the participants will have a set of games they can introduce into their own organization to enhance their own Agile adoption process.</description>
    <duration type="integer">90</duration>
    <id type="integer">2001</id>
    <presenters>Tobias Mayer</presenters>
    <room>Grand Ballroom A</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>The Agile Playground</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 2004, SEP tried adopting Agile practices.  However, Agile failed to have the desired lasting impact across the entire organization.  Things changed in 2007, when SEP implemented Kanban for the first time.  We will explore how Kanban teams at SEP matured through the lens of the Dreyfus Model for Skill Acquisition.  We will examine what this pattern has meant for institutionalization of Lean in the organization. We will discuss a counterintuitive technique for higher success and adoption rates of new methodologies.   Finally, we will review common pitfalls teams encountered adopting Kanban.

</description>
    <duration type="integer">45</duration>
    <id type="integer">2232</id>
    <presenters>Chris Shinkle</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Kanban adoption at Software Engineering Professionals (SEP)</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>According to research almost 85% of today&#8218;&#196;&#244;s leaders are constrained by narrow, analytical and habitual thinking.  Typically, they are still struggling with ways of thinking that make them defensive, controlling, and self-centered which deeply affect performance and teamwork.  We know that agile leaders at post-heroic stages are much more capable of working in collaboration.  So, what differentiate these leaders?  What transformative process can be used to develop Catalyst leaders &amp; teams?  This presentation will show you a proven and powerful path to develop post-heroic leaders and teams.  </description>
    <duration type="integer">90</duration>
    <id type="integer">2344</id>
    <presenters>Gilles Brouillette</presenters>
    <room>Columbus GH</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Developing Agile Leaders and Teams: A Developmental &amp; Transformational Path</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 hands-on session will cover a number of low cost, yet powerful research methods, like the &quot;&quot;burrito lunch&quot;&quot; to help you make better data-driven design decisions. We'll provide a number of techniques for recruiting research participants, creating better research questions, and what to do with your data once you've conducted your research. 



We'll provide hands-on demonstrations for how to conduct field research and interview participants. We'll even provide participants, yes, real people, for you to interview during the session. </description>
    <duration type="integer">90</duration>
    <id type="integer">5034</id>
    <presenters>Russ Unger, Todd Zaki Warfel</presenters>
    <room>Acapulco</room>
    <stage-id type="integer">16</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Guerilla Research Methods</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></description>
    <duration type="integer">90</duration>
    <id type="integer">5108</id>
    <presenters>Tore Dyb&#8730;&#8226;</presenters>
    <room>Plaza Ballroom A</room>
    <stage-id type="integer">13</stage-id>
    <time-slot-id type="integer">3</time-slot-id>
    <title>Don&#8217;t Mention the &#8216;A&#8217; Word: Agile Undercover</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 2001, Follett Software Company (FSC) began work on the next generation of its library software. Many options were considered, including sending the effort off shore. In April 2001, members of the Destiny team attended a C-SPIN meeting where Martin Fowler spoke about Extreme Programming (XP). In what was considered a bold experiment at the time, the team chose to adopt an XP process &quot;&quot;the most well-known and controversial&quot;&quot; of the new agile processes.



This experience report will tell of a &quot;&quot;do-it-yourself&quot;&quot; Agile success story, with changes, challenges and lessons learned along the way.

</description>
    <duration type="integer">45</duration>
    <id type="integer">2424</id>
    <presenters>Brian Spears</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">4</time-slot-id>
    <title>The Bold, New Extreme Programming Experiment - Now In Its Ninth Year</title>
    <updated-at type="datetime">2009-08-13T08:29:01Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>This talk will look at the product owner role on an Agile team from a Pragmatic product management perspective.  Many software development companies rely on their product management organizations to represent the needs of customers and the market.  Concentration on problems, the people who have them, and the circumstances under which they experience those problems is what makes the marriage of Pragmatic product management and Agile so valuable.  This presentation will describe how the Pragmatic approach to the MRD gives the Agile product owner a headstart and the entire Agile team an edge.</description>
    <duration type="integer">45</duration>
    <id type="integer">90</id>
    <presenters>Simon Orrell</presenters>
    <room>Crystal C</room>
    <stage-id type="integer">4</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>It's ALWAYS been the problem!</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>For almost a decade our community has claimed that agile is a risk-driven approach. Yet there is very little published material on agile risk management. Traditional risk management is based on avoidance of external variations. While, traditional project scheduling treats tasks homogeneously from a risk perspective. Lean pull systems and Real Options Theory provide new means to manage overall business risk in technology projects. This tutorial describes 3 techniques that evolved in the kanban community that increase sophistication of risk management and provide improved business agility.

</description>
    <duration type="integer">45</duration>
    <id type="integer">96</id>
    <presenters>David Anderson</presenters>
    <room>Grand Ballroom A</room>
    <stage-id type="integer">3</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>New Approaches to Risk Management</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 most common questions asked of practicing Agile teams is:



&gt; How can we increase velocity?



Many teams have had to answer this question, but is it the right question? Velocity is an excellent measurement for determining project timelines and progress towards them but doesn't give us any indication about the overall value of the features being delivered. All too often poor prioritization and solutioning are ignored because velocity is the KPI for the team. This session shows how to use value as a tool to ensure that you get more of the right things done.

</description>
    <duration type="integer">90</duration>
    <id type="integer">123</id>
    <presenters>Brandon Carlson</presenters>
    <room>Columbus IJ</room>
    <stage-id type="integer">6</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Value or Velocity?</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>Engaged as a software consultant at a financial services company, we brought up the topic of Agile early on and were told, &#8218;&#196;&#250;No!&#8218;&#196;&#249;    A Vice President at the company said that Agile had been tried there and failed, so the management decided that Agile was a waste of time and money and would be prohibited.   Despite this edict, our team cleverly succeeded at covertly injecting &#8218;&#196;&#250;The approach that shall not be named&#8218;&#196;&#249; into a couple key projects.  Our success caused management to reverse its firm anti-Agile stance, and the whole organization is now moving in that direction.</description>
    <duration type="integer">45</duration>
    <id type="integer">145</id>
    <presenters>Ken Howard</presenters>
    <room>Toronto</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>The Covert Agilist</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 describes how scrum was adopted by more than half of the software developers at Amazon.com (and counting).  The adoption was due largely to the efforts, both accidental and purposeful, of an internal employee. Amazon's corporate and development cultures played important roles, both positive and negative. With no executive sponsorship, adoption occurred primarily a team at a time. The wide range of success across teams and organizations leads to a number of important lessons learned with regard to enterprise scrum adoption. The lesson: you can cause this to happen.



</description>
    <duration type="integer">45</duration>
    <id type="integer">284</id>
    <presenters>Alan Atlas</presenters>
    <room>Regency C</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Accidental Adoption - The Story of Scrum at Amazon.com</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've done user research. Now what? Join us for this hands-on session to learn how to interpret research data, prioritize findings, and create actionable design research items. Learn about the task analysis grid, how to create data-driven personas, and what the persona DNA model is. 



Find out how to use actionable design research to inform your prototype. We'll discuss 8 guiding principles that will help you avoid common mistakes made during prototyping. And finally, we'll discuss a number of prototyping methods and give a number of tips and techniques for common prototyping tools.  </description>
    <duration type="integer">90</duration>
    <id type="integer">323</id>
    <presenters>Joe Sokohl, Todd Zaki Warfel</presenters>
    <room>Acapulco</room>
    <stage-id type="integer">16</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Mission Possible&#8212;from design research to prototype in 2 days or less.</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>Coding Dojos are sessions were participants are invited to participate in a programming challenge. They get the opportunity to practice Extreme Programming techniques such as Test-Driven Development, Simple Design and Pair Programming.

In this dojo, the audience will be asked to concentrate on adding features (while preserving existing functionalities) to a Java project that has not been written with testability in mind. In other words, we will work on legacy code. The Randori format will be used to let as many participants as possible do actual coding.</description>
    <duration type="integer">90</duration>
    <id type="integer">402</id>
    <presenters>Guillaume Tardif, Eric Lefevre-Ardant</presenters>
    <room>Grand Ballroom F</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Coding Dojo: Enhancing Legacy Code</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>Lack of good release planning is endemic. Teams seem caught up in iteration-at-a-time development and not planning for releases. Even those who create initial release plans often fail to keep them current. This approach enables teams to resist request for &#8218;&#196;&#250;spurious&#8218;&#196;&#249; information such as &#8218;&#196;&#250;how much is this project going to cost,&#8218;&#196;&#249; or &#8218;&#196;&#250;how long is this project going to take?&#8218;&#196;&#249; 



This session will address why release planning is so important and then cover a series of release planning topics such as value-driven planning and multi-level planning

</description>
    <duration type="integer">90</duration>
    <id type="integer">411</id>
    <presenters>Jim Highsmith</presenters>
    <room>Crystal A</room>
    <stage-id type="integer">8</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Advances in Release 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>XUnit is the generic name given to the family of  tools/frameworks used by developers when developing automated unit tests. JUnit, NUnit, MsTest and CppUnit are some of the better known members of the family. High quality automated unit tests are one of the key development practices that enable incremental development and delivery of software. This tutorial provides the participants with a vocabulary of smells and patterns with which to reason about the quality of their test code and a set of reusable test code design patterns that can be used to eliminate the smells. </description>
    <duration type="integer">90</duration>
    <id type="integer">542</id>
    <presenters>Gerard Meszaros</presenters>
    <room>Grand Ballroom C North</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>XUnit Test Patterns and Smells; Improving Test Code Through Refactoring</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 has all these weird, expensive-looking practices: pair programming, test-driven development, regular planning meetings, moving the programmers and business people closer together, focusing people on a single project, multi-disciplinary teams. We can't afford to go agile!



In this session, J. B. Rainsberger introduces agile practices by relating them to core business matters: compounding early earned value and reducing unnecessary costs. Learn why practice and learning are really profit centers. Maybe you can't afford not to go agile!

 </description>
    <duration type="integer">90</duration>
    <id type="integer">553</id>
    <presenters>J. B. Rainsberger</presenters>
    <room>Grand Ballroom B</room>
    <stage-id type="integer">12</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>An introduction to Agile Through the Theory of Constraints</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 find games and simulations incredibly valuable in our coaching and training. Given the number of times we've seen &quot;Does anyone have a game or simulation to ... ?&quot; on the mail lists, we know we're not alone. While there's leverage in using games that others create, it's even better to create your own games to address your specific teaching points. In this session, we will introduce some essential elements of game design and demonstrate a process for designing a game starting with a learning objective. Participants will then use materials we supply to create their own Agile games.</description>
    <duration type="integer">180</duration>
    <id type="integer">705</id>
    <presenters>Elisabeth Hendrickson, Chris Sims</presenters>
    <room>Columbus GH</room>
    <stage-id type="integer">11</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Creating Agile Simulations and Games for Coaches and Consultants</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 does it mean to be a professional software developer?  What rules do we follow?  What attitudes do we hold?  And how can we maintain our professionalism in the face of schedule pressure?  In this talk Robert C. Martin outlines the practices used by software craftsmen to maintain their professional ethics.  He resolves the dilemma of speed vs. quality, and mess vs schedule.  He provides a set of principles and simple Dos and Don&#8218;&#196;&#244;ts for teams who want to be counted as professional craftsmen.</description>
    <duration type="integer">90</duration>
    <id type="integer">908</id>
    <presenters>Robert Martin</presenters>
    <room>Crystal B</room>
    <stage-id type="integer">10</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Craftsmanship</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>Project Managers comprise the single largest category of agile practitioners that are actively engaged in the industry (18%). However, there is no clear consensus on the role of project manager within the Agile community.  Viewpoints range from:

&#8218;&#196;&#162; The PM is complete waste. 

&#8218;&#196;&#162; The PM is a necessary part-time helper.

&#8218;&#196;&#162; The PM is a crucial communicator and facilitator.



So who's right? This interactive session will seek to address these questions about who is good, who is bad, why they are, and who says so.</description>
    <duration type="integer">90</duration>
    <id type="integer">1097</id>
    <presenters>Jesse Fewell, Pat Reed</presenters>
    <room>Regency A</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>What is an Agile Project Manager anyway?</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>Traditional thinking holds that the more critical the application, the more tightly its development must be planned, staged, and controlled. 

The truth is that a flexible culture is stronger, safer, and more robust. FDA regulatory standards are designed to support a learning organization &#8218;&#196;&#236; fully compatible with Agile! This session gives you practical tips for moving your customers and auditors to a flexible agile approach to planning, team interactions, and risk management. When the culture shifts, the result is not just that teams achieve their goals sooner, but safety is greatly enhanced.</description>
    <duration type="integer">90</duration>
    <id type="integer">1209</id>
    <presenters>Brian Shoemaker, Nancy Van Schooenderwoert</presenters>
    <room>Regency D</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>When it just *has* to work: Agile Development in Safety-Critical 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>Agile coaches attempt to influence teams in different ways. Our experience is that agile coaches typically work by instinct and intuition. This makes it very hard to explain what coaches do and difficult to teach people how to coach agile teams.

Richard Hackman claims in his book &quot;&quot;Leading Teams&quot;&quot; that there a three basic types of coaching intervention: Motivational, Consultative, Educational. We want to test out that theory and explore about what Agile Coaches really do.

We aim to uncover specific coaching interventions that participants have tried and whether these interventions helped.</description>
    <duration type="integer">90</duration>
    <id type="integer">1809</id>
    <presenters>Liz Sedley, Rachel Davies</presenters>
    <room>Regency B</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>What Does an Agile Coach Do?</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>**Intent**



Provide the participants with a hands-on-experience of real world refactoring by taking an open source project and refactoring it.



**Summary** 



Refactoring is a very well established practice not just in the Agile Community, but outside as well. 



This session is an attempt to help the development community understand refactoring a little better. It will provide a hands-on opportunity for developers to explore these concepts in action. This session will try to amplify the participant&#8218;&#196;&#244;s learning process by pairing them with other practitioners and peers.</description>
    <duration type="integer">180</duration>
    <id type="integer">2258</id>
    <presenters>Naresh Jain</presenters>
    <room>New Orleans</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Clean Code Clinic: Refactoring Fest</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 is adopted by large enterprises, the number of transformation success stories has grown.  But, transformation is an ongoing process, and maintaining organizational change is difficult. So, what happens after the success stories?  What can IT leaders expect once the honeymoon is over?  In this talk, Chuck Maples, SVP of R&amp;D at Borland, will address these questions head-on, sharing his experiences in Borland&#8218;&#196;&#244;s Agile transformation. He&#8218;&#196;&#244;ll  discuss the challenges that can emerge after the initial phases of transformation give way a new stage in the journey.   







</description>
    <duration type="integer">45</duration>
    <id type="integer">2272</id>
    <presenters>Chuck Maples</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Enterprise Agile Transformation:  The Two Year Wall</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>Fear of decision making often leads teams to exhibit one or more of the dysfunctional symptoms of Agile ADHD. This tutorial will help agile practitioners overcome the fear of decision making by first embracing that there are no right or wrong decisions. Agile development is ultimately driven by a series of decisions, all of which are made in the face of uncertainty. Tutorial participants will take away principles and practices that enable their team to embrace uncertainty and be proactive in making better decisions at the most responsible moment.</description>
    <duration type="integer">90</duration>
    <id type="integer">3110</id>
    <presenters>Bruce Winegarden, David Ullman</presenters>
    <room>San Francisco</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Overcoming Agile ADHD</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 is a trick question, right? In agile, everyone works on the same items together, at the same time. Yet, the reality is we&#8218;&#196;&#244;re not all interchangeable cogs. Developers and testers each bring their own, unique skills to the table. The key to effective agile is not minimizing our differences, but building upon the strengths each person brings to the team.  Join us for this hands-on simulation and retrospective as developers and testers explore how agile teams build quality into their process, how each member contributes to that quality, and how we can avoid traditional testing pitfalls.</description>
    <duration type="integer">90</duration>
    <id type="integer">3205</id>
    <presenters>Abby Fichtner, Nate Oster</presenters>
    <room>Grand Ballroom D North</room>
    <stage-id type="integer">14</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Where Does Developer Testing End and Tester Testing Begin?</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>Selenium is the 800lb gorilla of open source web application testing.  For four years it has been steadily gaining a following and making a difference for corporations large and small.  Such tools have always been a trap for adept Agile teams though.  Too often teams rely on functional testing and skimp on the much more effective 'small' unit tests.  Now with JBehave steering Selenium, we're seeing test scripts emerge that engage formerly perplexed management and business folks.  The time has come for this type of tool pairing to be valued for its role in validating Agile in the enterprise



</description>
    <duration type="integer">90</duration>
    <id type="integer">3207</id>
    <presenters>Paul Hammant, Mauro Talevi</presenters>
    <room>Grand Ballroom E</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Selenium and JBehave : A surprisingly successful shotgun wedding</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 describe our experience in using the Scrum process of Software Development to create complex tools for use in animated movie production. Our process evolved out of the need to keep the task of UI design at least one sprint ahead of software development. Our products are designed for the creative in-house artists who use the tools for long hours over the course of movie production. We will also share ways to capture the complexity in the artists workflow and methods to break it down into reusable components both for graphical user interfaces and for software development. </description>
    <duration type="integer">45</duration>
    <id type="integer">3223</id>
    <presenters>Rajesh Sharma, Brian Wherry</presenters>
    <room>Columbus KL</room>
    <stage-id type="integer">16</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>Software Development for Disney Animated Feature Film Production </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></description>
    <duration type="integer">90</duration>
    <id type="integer">5110</id>
    <presenters>Philippe Kruchten</presenters>
    <room>Plaza Ballroom A</room>
    <stage-id type="integer">13</stage-id>
    <time-slot-id type="integer">5</time-slot-id>
    <title>ActiveStory: A Tool for Agile &#8211; UCD Design 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 development has grown a lot since its rebeleous 2001 start. In fact, it has grown to be the mainstream way of developing software.



The time has come to drop the word 'agile.' Agile development is just modern practices in software development. There is no need to explicitly mark practices as Agile. There is no need anymore for opposing camps. Keeping the word Agile and things like &quot;&quot;the Agile conference&quot;&quot; is holding the development of modern SW development practices back.



This session will be in debate form to discuss the above mentioned motion.

</description>
    <duration type="integer">45</duration>
    <id type="integer">656</id>
    <presenters>Bas Vodde, Steven Mak</presenters>
    <room>Grand Ballroom A</room>
    <stage-id type="integer">3</stage-id>
    <time-slot-id type="integer">6</time-slot-id>
    <title>Lets stop calling it &quot;agile&quot;</title>
    <updated-at type="datetime">2009-08-13T08:28:49Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>An experience report (and video!) on the successful adoption and scaling of Agile practices within an IT organization through a year-long, innovative, and exciting campaign &#8218;&#196;&#236; the Amazing Team Race.  This report shares successful strategies, some failed approaches, and finally how we created a culture of enthusiasm surrounding the adoption of Agile.  It also demonstrates how widespread Agile adoption can be successful even in non-collocated team environments.   The make-up of the IT organization consists of distributed teams with half of whom are outsourced contractors.

</description>
    <duration type="integer">45</duration>
    <id type="integer">811</id>
    <presenters>Gabino Roche, Jr., Belkis Vasquez</presenters>
    <room>Regency C</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">6</time-slot-id>
    <title>The Amazing Team Race &#8211; A Team-Based 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>You championed Agile adoption in your organization. Interest grew as your projects become predictable. You led a group of agilists who helped spread the word to more groups.

Life was good.

Then senior management took notice of the improvements and decided to mandate adoption of Agile. They&#8218;&#196;&#244;ve skimmed some of the books, but don&#8218;&#196;&#244;t have any practical experience.

Your agile adoption has just reached a critical stage as it moves from grass-roots effort to management directive.

You&#8218;&#196;&#244;re about to lose control of your baby.

You&#8218;&#196;&#244;re about to learn that you&#8218;&#196;&#244;ve created a monster.

</description>
    <duration type="integer">45</duration>
    <id type="integer">2844</id>
    <presenters>Michael Marchi</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">6</time-slot-id>
    <title>Weaponized Scrum</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>Today&#8218;&#196;&#244;s developers are quick to adopt leading-edge technologies that can accommodate project peaks and valleys, evolve and change, and support agile principles. Using the CollabNet platform, this session will demonstrate the agile best practice of continuous integration (CI) using cloud provisioning capabilities and the Hudson open source CI engine. Attendees will learn a framework that can be used in their environment, including an understanding of the components, tools, set up, and generalized use cases for development in both virtual private clouds and public clouds, like Amazon EC2.



</description>
    <duration type="integer">45</duration>
    <id type="integer">3027</id>
    <presenters>Darryl Bowler</presenters>
    <room>Columbus KL</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">6</time-slot-id>
    <title>Build and Test in the Cloud &#8211; CI and Cloud Provisioning 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>This experience report, by a project's technical architect, details the adoption of agile methods across several teams after one high profile success. The organization had a long history of waterfall development and a clearly defined remit for technical architects. Years of refinement had led to a set of techniques which contradicted many of the ideals held by agile practitioners.

The author's challenge was to maintain agility and fulfill responsibilities inherited from waterfall processes without reverting to the conventional practices that ultimately lead to the architect's ivory tower.</description>
    <duration type="integer">45</duration>
    <id type="integer">3030</id>
    <presenters>Andrew Rendell</presenters>
    <room>Toronto</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">6</time-slot-id>
    <title>Descending from the Architect's Ivory Tower</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 charting new territory&#8218;&#196;&#236;-enterprise-scale Agile&#8218;&#196;&#236;-traditional roadmaps only take you so far.  When landscapes change in weeks, product management must find a way to reconcile sprint plans and backlogs from multiple teams with longer-term product direction.  David Wilby, SVP of Products at Borland, shares how his teams tackled the roadmap challenge during Borland&#8218;&#196;&#244;s Agile transformation.  He&#8218;&#196;&#244;ll cover how roadmaps became a barrier to scaling Agile, how his teams adopted Agile roadmapping, the challenges, and the impact the new practices have had on Borland&#8218;&#196;&#244;s Agile transformation. 

</description>
    <duration type="integer">45</duration>
    <id type="integer">3032</id>
    <presenters>David Wilby</presenters>
    <room>Crystal C</room>
    <stage-id type="integer">4</stage-id>
    <time-slot-id type="integer">6</time-slot-id>
    <title>Roadmap Transformation:  From Obstacle to Catalyst</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 good QA is worth their weight in gold, but the reality is that the best QA often have trouble working in an Agile Environment. The shift to a quality centred approach surely must be every QA's dream but there are underlying issues that prevent this adoption. In this session we delve into the mind of a career tester, probe the pain points &amp; explore strategies to communicate the value of agile testing to the classically trained. We look at personalities &amp; what drives people to want to test &amp; the benefits that QA provide to a project beyond rubber-stamping the 'done' column on the task board.</description>
    <duration type="integer">90</duration>
    <id type="integer">140</id>
    <presenters>Malcolm Beaton, Simon Bennett</presenters>
    <room>Grand Ballroom D North</room>
    <stage-id type="integer">14</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Why (so many) Testers (still) hate 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>All projects bene&#212;&#168;&#197;t from high quality code but achieving the full bene&#212;&#168;&#197;ts of agile approaches demands higher-than-usual software quality. A Continuous Integration build provides an ideal platform for applying automated tools to issues of code quality. 



This tutorial looks at automated code quality tools that can be used to enforce or monitor code quality in Java and Ruby, and how they can be used to check quality manifested by:



* style enforcement 

* lines per method 

* methods per class 

* code duplication 

* npath and cyclomatic complexity 

* test coverage 

</description>
    <duration type="integer">90</duration>
    <id type="integer">166</id>
    <presenters>Steve Hayes</presenters>
    <room>Grand Ballroom C North</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Java and Ruby Tools for Code Quality</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>Most Agile initiatives focus on delivery while neglecting the impact that such a radical change may have on the project and organization. The Agile PM must protect the team and help influence the change effort when there is no formal change management.  Leveraging a military battle metaphor a lightweight technique can be used to map influences acting on a project.  Participants will learn how to identify potential risks and how and where to respond.  Spending minutes a day using this technique can mean the difference between an Agile change effort and the end of one Agile project.</description>
    <duration type="integer">90</duration>
    <id type="integer">253</id>
    <presenters>George Schlitz, Giora Morein</presenters>
    <room>Regency D</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Mapping the Agile Enablement Battlefield</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>Do you understand why your team behaves the way it does? In this session, you&#8218;&#196;&#244;ll leave with ways to unlock the true potential of your team through better and more productive communication. You will learn how to identify behavioral profiles, and how to capitalize on the diverse behaviors found on typical teams. A highly interactive, fun, and refreshing look at the human element with actionable techniques that target **individuals** and their **interactions**. Topics range from enhancing interpersonal communication (Tango) to effectively leveraging the anatomy of your team (Square Dance).</description>
    <duration type="integer">90</duration>
    <id type="integer">286</id>
    <presenters>Barry Rogers, Ken Howard</presenters>
    <room>San Francisco</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>It Takes Two to Tango; Four to Square Dance</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>Participate in a hands-on workshop, where you'll learn how to use sketching and the design studio method for rapid design iteration. Find out how we've used methods borrowed from architecture and industrial design for faster better design. See how using the design studio method can help you generate several weeks worth of work in just one afternoon. Find out what the 6-8-5 method is. 



But wait... there's more.



Think paper is for making airplanes? Think again. We'll show you how to do things with paper prototyping you never imagined, including AJAX-style transitions and simulations. </description>
    <duration type="integer">90</duration>
    <id type="integer">324</id>
    <presenters>Todd Zaki Warfel</presenters>
    <room>Acapulco</room>
    <stage-id type="integer">16</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Rapid Sketching and Prototyping Design Studio</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>Experienced product managers working with agile product teams for the first time are stuck between old methods and new ones. Developers are requesting new artifacts, advocating new meetings, and defining new roles. Old processes and artifacts that seemed to be working are not valued by agile teams. While developers are learning how to deliver working code faster, without agile product management the team might be building the wrong things. 

Agile product managers and product owners face issues focusing on the business, technical, marketing, and sales roles required for effective agile teams.</description>
    <duration type="integer">90</duration>
    <id type="integer">375</id>
    <presenters>Steve Johnson, Laureen Knudsen</presenters>
    <room>Crystal C</room>
    <stage-id type="integer">4</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Panel: product owner or product manager or both?</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 instructors wish, when they were first learning test-driving, refactoring, and OO, that they had had a side-by-side comparison between code Heaven and code Hell. Such an object lesson would have made the value and benefits of agile programming practices so much more plain, so much sooner. Alas for us, but hurray for you! In this workshop you will be able to compare and work with two very different implementations of the same problem domain: one of them fabulously ugly, and the other of them &#8218;&#196;&#238; well &#8218;&#196;&#238; a lot better. This is a close-repeat of a successful session we gave at Agile 08.



</description>
    <duration type="integer">90</duration>
    <id type="integer">403</id>
    <presenters>Patrick Wilson-Welsh, Corey Haines</presenters>
    <room>Columbus KL</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Ugly Code vs Clean Code: A/B Comparison of Legacy/Test-Driven Implementations</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>Traditional development emphasizes &#8218;&#196;&#250;following a plan with minimal changes,&#8218;&#196;&#249; whereas agile stresses &#8218;&#196;&#250;adapting successfully to inevitable changes.&#8218;&#196;&#249; If agility is delivering customer value by being flexible, then how can measuring agile performance by adherence to schedule, cost, and scope be valid? We need to modify project success measures in order to build effective agile organizations. The session will build a case for changing performance measurement from the traditional Iron Triangle of cost, schedule, and scope to an Agile Triangle that focuses on value, quality, and constraints.

</description>
    <duration type="integer">90</duration>
    <id type="integer">410</id>
    <presenters>Jim Highsmith</presenters>
    <room>Crystal B</room>
    <stage-id type="integer">10</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Zen and the Art of Software Quality </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>Our ability to identify patterns of behavior and the likely reasons behind them helps when addressing team dynamics issues. The popular Scrum characters chicken and the pig turn out to be just two of many behaviors that comprise the [Scrum Bestiary](http://www.ademiller.com/blogs/tech/2008/10/scrum-bestiary/). Other examples include the seagull - who derails the team and leaves - and the fox - who is intent on stealing vital resources. This humorous workshop presents a taxonomy of some common behaviors on teams and looks at the drivers behind them and strategies for addressing them. </description>
    <duration type="integer">45</duration>
    <id type="integer">448</id>
    <presenters>Ade Miller</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>The Scrum Bestiary: Pigs, Foxes, Chickens and Seagulls a behavioral taxonomy</title>
    <updated-at type="datetime">2009-08-13T08:28:32Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>You&#8218;&#196;&#244;ve read about agile, heard about agile, and your company is probably using it in some form by now.  Here&#8218;&#196;&#244;s your opportunity to experience the rhythm of an agile project in action and learn first hand many of the practices.  Through participation in the Agile/XP Game, this experiential workshop introduces Agile/XP in a non-threatening, non-technical, and fun way.  Attendees will come away with an understanding of many of the best practices used to deliver high-quality software quickly. Experience how the various roles work together as on effective agile team.  </description>
    <duration type="integer">90</duration>
    <id type="integer">476</id>
    <presenters>Glenn Bernsohn, Michael Walkden</presenters>
    <room>Grand Ballroom B</room>
    <stage-id type="integer">12</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>The Agile Game: An Experiential Workshop</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>Find out why we give personal feedback, how to provide effective feedback, what makes feedback ineffective and how to deal with poorly phrased feedback. Learning what makes feedback effective helps you to seek your own feedback and improve, whilst being able to support the people around you.



This is suitable for anyone who's nervous about giving or getting feedback. Coaches and other Agile Transformers may find this simple workshop helpful for their own teams.



</description>
    <duration type="integer">45</duration>
    <id type="integer">517</id>
    <presenters>Elizabeth Keogh</presenters>
    <room>Regency B</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Giving and receiving effective feedback</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>Integration tests are a scam, a self-replicating virus that takes over your project and burdens you with long-running, fragile, hard-to-understand test suites. You're probably writing 2-5% of the integration tests you need to test thoroughly. You're probably duplicating unit tests all over the place. Your integration tests probably duplicate each other all over the place. When an integration test fails, who knows what's broken? When you refactor, you have to fix dozens of integration tests. Stop it. Learn the two-pronged attack that solves the problem: collaboration tests and contract tests.</description>
    <duration type="integer">90</duration>
    <id type="integer">708</id>
    <presenters>J. B. Rainsberger</presenters>
    <room>Columbus IJ</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Integration Tests Are A Scam</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>Test Driven Development is the core of the technical Agile practices. With TDD, programmers get instant feedback that their code does what they intend. This class shows the motivations and mechanics of TDD, but does not stop there. Attendees get first hand experience at TDD, writing well tested code in the challenging world of C++. Attendees see how TDD helps to prevent many bugs and memory leaks from ever making the bug list. CppUTest, an open source test harness, is used to collect, organize and automate C++ unit tests.

</description>
    <duration type="integer">90</duration>
    <id type="integer">878</id>
    <presenters>James Grenning, Bas Vodde</presenters>
    <room>Grand Ballroom F</room>
    <stage-id type="integer">7</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>TDD Clinic: C++</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 method of Modeling in Color (MIC) has its foundation in object-oriented analysis and design; however, given today's modern service oriented architectures (SOA), the approach is more relevant than ever. In any SOA, MIC can provide answers to difficult questions like: How are services properly designed? What's the appropriate level of granularity for those services? Basic MIC techniques will be discussed and how to break a Color Model into discrete, loosely coupled components will be examined. How to convert the componentized model into XML schema and into XML web services will be explored.</description>
    <duration type="integer">90</duration>
    <id type="integer">1417</id>
    <presenters>Daniel Vacanti, Stephen Palmer</presenters>
    <room>Grand Ballroom A</room>
    <stage-id type="integer">3</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>SOA and Color Modeling</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 authors previously showed Scrum teams using XP practices achieved distributed velocity equal to local velocity with multiple distributed teams. Local velocity equaled distributed velocity and production increased linearly as teams scaled up to over 50 developers. Here we show a similar pattern for extreme time zone differences between San Francisco and India. Local velocity was established at five times industry average waterfall velocity. When team members were added in india, production scaled linearly. Detailed data on team process and performance will help others achieve the same goal.</description>
    <duration type="integer">45</duration>
    <id type="integer">1528</id>
    <presenters>Jeff Sutherland, Guido Schoonheim</presenters>
    <room>Crystal A</room>
    <stage-id type="integer">8</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Fully Distributed Scrum: Linear Scalability of Production Between SFO and India</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 more development teams adopt agile, product managers must change the way they work to keep up with faster development cycles and shorter customer feedback loops. Product managers new to agile soon realize that agile processes require more involvement from their group. Given that most product managers are already overworked, how can they manage these new activities to derive more value from software projects and products? I will share my experience transitioning to Agile, pitfalls to avoid and propose solutions to the new challenges that arise.</description>
    <duration type="integer">90</duration>
    <id type="integer">2125</id>
    <presenters>Catherine Connor</presenters>
    <room>Regency C</room>
    <stage-id type="integer">4</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>How Product Management Must Change to Enable the Agile Enterprise</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>Starting up an Agile team is one of the first things you might be asked to do when a company wants to &quot;go Agile.&quot;  What do you need to know before starting up a team?  In the start-up, how much do teams need to know about Agile before they &quot;go&quot;?  What do they need to know about each other...what the project is all about...who they will become as a team?  These and other questions are answered as we walk through good ways to start-up Agile teams.  </description>
    <duration type="integer">90</duration>
    <id type="integer">2341</id>
    <presenters>Lyssa Adkins</presenters>
    <room>Toronto</room>
    <stage-id type="integer">2</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Team Start-up: one of the first Agile Adoption activities</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 &#8218;&#196;&#250;The Fifth Discipline&#8218;&#196;&#249;, his pioneering work on the learning organization, Peter Senge writes that the practice of dialogue is a key skill for team learning. Dialogue is commonly confused with discussion, but as defined by Senge it is distinctly different. As a result of this confusion, the skills that enable effective dialogue are often underdeveloped or misunderstood by teams. In this session we&#8218;&#196;&#244;ll use a specific dialogue format called World Caf&#8730;&#169; to explore the many factors that influence dialogue quality, and how to accelerate agile team learning through the use of dialogue.</description>
    <duration type="integer">90</duration>
    <id type="integer">2794</id>
    <presenters>Eric Babinet</presenters>
    <room>Regency A</room>
    <stage-id type="integer">9</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Improving the Quality of Your Dialogues </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 describes a lightweight approach to code reviews used in co-located and geographically distributed agile teams. It covers lessons learned from several agile projects: real value, best practices and pitfalls of code reviews. The presentation explains how to make code reviews effective, relatively painless, and liked by the team. Moreover, it presents some interesting aspects of code reviews growing beyond their original intention.

The session includes a demo on how Atlassian Crucible integrated with leading IDEs via Atlassian IDE Connector facilitates the whole process.



</description>
    <duration type="integer">90</duration>
    <id type="integer">3070</id>
    <presenters>Wojciech Seliga, Slawomir Ginter</presenters>
    <room>Grand Ballroom E</room>
    <stage-id type="integer">15</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Effective code reviews in 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></description>
    <duration type="integer">90</duration>
    <id type="integer">5111</id>
    <presenters>Yael Dubinsky, Philippe Kruchten</presenters>
    <room>Plaza Ballroom A</room>
    <stage-id type="integer">13</stage-id>
    <time-slot-id type="integer">7</time-slot-id>
    <title>Research on Agile &#8211; presentations, summary, and reflection </title>
    <updated-at type="datetime">2009-08-13T08:28:23Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>Regardless of your coaching experience, there are a wide variety of temptations you can fall into that affect the quality of your coaching.  This presentation will describe: each of the 10 temptations, such as pride or impatience; the negative effects on you and/or your team for each temptation; and strategies to avoid falling into and overcoming each of the 10 temptations.  There will discussion opportunties for people to learn from the more experienced coaches in the audience.  Whether a new or experienced coach, this presentation will have information to improve your coaching.</description>
    <duration type="integer">45</duration>
    <id type="integer">1194</id>
    <presenters>Stevie Borne</presenters>
    <room>Regency B</room>
    <stage-id type="integer">5</stage-id>
    <time-slot-id type="integer">8</time-slot-id>
    <title>10 Temptations of an Agile Coach (new or experienced)</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 is a journey starting in 2005 when establishing a new software company in Bangladesh 7000 km away from Denmark. Hiring 20 people in one week in Bangladesh and start using CMMI processes to integrate development in Denmark and Bangladesh. After some challenging time aborting the CMMI project and switching back to agile and lean techniques to make it work. Experience from implementing global big bang Scrum and building a kaizen culture. From long running projects, technical dept and integration nightmares to small batches, continuous integration and faster delivery of business value.</description>
    <duration type="integer">45</duration>
    <id type="integer">2236</id>
    <presenters>Mads Troels Hansen, Hans Baggesen</presenters>
    <room>Crystal A</room>
    <stage-id type="integer">8</stage-id>
    <time-slot-id type="integer">8</time-slot-id>
    <title>From CMMI and isolation to Scrum, Agile, Lean and collaboration</title>
    <updated-at type="datetime">2009-08-13T08:28:16Z</updated-at>
  </session>
  <session>
    <created-at type="datetime">2009-08-13T03:46:00Z</created-at>
    <description>A splendid way to know if you will succeed at agile in the workplace is to  be guided by an agile experience in a volunteer setting, where little is masked. Volunteers became volunteers because, despite jobs, families and everything else in their lives, they see a unique reward from the donation of their time and efforts. The danger of the workplace is that, rather than keeping the eye on the prize, it is too easy for someone to replace the underlying motivational reward by the paycheck. This report shows how a volunteer organization was able to experience and learn the power of agile values.</description>
    <duration type="integer">45</duration>
    <id type="integer">3123</id>
    <presenters>Ron Morsicato</presenters>
    <room>Atlanta</room>
    <stage-id type="integer">1</stage-id>
    <time-slot-id type="integer">8</time-slot-id>
    <title>We Are Naked Volunteers: How an Agile Users Group Rediscovered Itself</title>
    <updated-at type="datetime">2009-08-13T03:46:00Z</updated-at>
  </session>
</sessions>
