2009-08-13T03:46:00Z 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. 90 89 Tommy Norman Grand Ballroom E 15 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 90 Simon Orrell Crystal C 4 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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). 45 91 Michael Longin, Christopher Taylor Regency D 14 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 96 David Anderson Grand Ballroom A 3 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In this session, you will learn one thing: how to enable emergent design in a database. The reality is that database development is different from application code development. They are similar, but databases bring about some forces that we haven’t given much thought. This session challenges traditional, foundational database development techniques and proposes a new framework into which Agile processes, as well as techniques such as TDD or refactoring, can better fit. 45 104 Max Guernsey Grand Ballroom D North 14 12 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z There is much information available about how to *begin* automated UI testing projects. There is little information available about how to *maintain* successful, effective, long-term, large-scale UI testing projects. Over the course of more than two years, my company Socialtext was able to grow a test automation project from a proof of concept of 400 test steps, run on demand, to nearly 10,000 test steps run automatically 24 hours a day, 7 days a week. This talk will cover test design, test architecture, test creation, test maintenance, and the project's future steps. 45 111 Chris McMahon Grand Ballroom D North 14 20 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z One of the most common questions asked of practicing Agile teams is: > 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. 90 123 Brandon Carlson Columbus IJ 6 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 & explore strategies to communicate the value of agile testing to the classically trained. We look at personalities & what drives people to want to test & the benefits that QA provide to a project beyond rubber-stamping the 'done' column on the task board. 90 140 Malcolm Beaton, Simon Bennett Grand Ballroom D North 14 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Engaged as a software consultant at a financial services company, we brought up the topic of Agile early on and were told, “No!” 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 “The approach that shall not be named” 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. 45 145 Ken Howard Toronto 2 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Maintaining a good working relationship while also staying true to Agile principles can be extremely challenging at times. Over the last two years we have been using William Ury's "Yes! No. Yes?" approach to confronting anti-Agile behavior to great success. This workshop will train participants in the approach and go through several role playing examples to help practice the technique. 45 154 Bruce Eckfeldt Crystal A 5 24 2009-08-13T08:22:54Z 2009-08-13T03:46:00Z Continuous Integration means different things to different people. This workshop will demonstrate a set of best practices that allow a software delivery team to derive the most value out of their software development dollars, by adhering to the Agile Manifesto principle that states “Working software is the primary measure of progress.” That is, we will see how software can be delivered that allows rapid change, monitors that the changes do not adversely affect quality, and delivers potentially shippable code from easy to implement open source tools available to the community at large. 90 161 Howard Deiner Grand Ballroom C North 15 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Traditional product managers have broad inbound and outbound responsibilities including segmentation, requirements, positioning and pricing - often shortchanging their teams. Product owners are always available and own backlogs/stories - but often lack real market experience. Both roles have challenges. PO/PM discussions are short on context and clarity. How can agile address the broader product mgmt challenge? How to agilize waterfall PMs? Do technical POs need marketing/sales/pricing skills? We'll look at roles and organizational models that work for commercial software companies. 45 162 Rich Mironov Crystal C 4 12 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z All projects benefit from high quality code but achieving the full benefits 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 90 166 Steve Hayes Grand Ballroom C North 15 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z When adjectives and adverbs appear in User Stories, they can be easily overlooked and seen as simple adornments to the story. There are a couple schools of thought on how to handle non-functional requirements on Agile projects. Mike Cohn recommends writing a User Story for each non-functional requirement, while others recommend creating task cards to drive out specification using Thomas Gilb's approach. In this session, examples of various techniques for handling non-functional requirements will be demonstrated, with a discussion of pros and cons of each technique. 45 173 Ken Howard Crystal C 4 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Do you mentor, coach, teach or just help other people? Do you wonder why after your greatest teaching moments people just don't get it? In recent years neuroscience has started to provide us with a number of insights in what happens when we're teaching. These insights make it clear that learning is really about building and reinforcing existing neural networks. Instead of providing lots of new ideas out of the blue, we need to understand the learners existing context and work with that. Instead of focusing on mistakes and errors, we need to focus on what good solutions look like. 90 174 Mark Levison, Linda Rising Columbus GH 11 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Agile development has taken a number of concepts and principles from the study of [complex adaptive systems](http://en.wikipedia.org/wiki/Complex_adaptive_system). But since the birth of the [Agile Manifesto](http://agilemanifesto.org/), the study of complexity has not stopped. In this talk I give a number of ideas copied from complexity experts, and I will review what [fitness landscapes](http://en.wikipedia.org/wiki/Fitness_landscape), adaptive walks and [evolutionary stable strategies](http://en.wikipedia.org/wiki/Evolutionarily_stable_strategy) could mean for agile software development. 45 177 Jurgen Appelo Grand Ballroom A 3 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 185 Kent McDonald, Chris Matts Columbus IJ 6 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z During 2005-2009 Scrum teams were formed in churches in Massachusetts, Connecticut, Florida, Delaware, and Virginia. This experience report will show how Scrum broke out of the IT silo into finance, marketing, operations, and senior management teams. Churches have to solve difficult impediments – part-time and volunteer workers, narrow specialization, little experience with project teams, and political problems that started in 1692. Their unique contribution has been to successfully address the larger question of continuous process improvement for the whole organization. 90 189 Arline Sutherland Columbus GH 11 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Dean Leffingwell describes how agile methods are being successfully applied to enterprise-class development. • Part I describes team practices that scale to the enterprise, including: structuring agile teams, mastering the iteration, concurrent testing and continuous integration. • Part II describes additional practices necessary to achieve full enterprise benefits. Topics include: intentionally emergent architectures, lean requirements at scale, coordinating releases with the agile release train, agile training and rollout strategies and measuring business performance. 90 201 Dean Leffingwell Toronto 2 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z So what is Scrum anyway? And what is Scrum not? How do I apply Scrum in practice? Scrum seems to be the most popular agile method at the moment and Scrum jargon is used everywhere. This session is for those of you who have perhaps heard the word Scrum, but never really received a proper introduction to what it actually is. Hopefully you'll feel less alienated afterwords :o) 90 231 Henrik Kniberg Grand Ballroom B 12 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Bob Scoble Esq. and Ted "Theodore" Logan are about to embark on a new technology start-up venture when a mystical figure with a fondness for beagles and the Galapagos Islands appears before them, promising great prospects for their new business if they first agree to accompany him on a unique adventure. They accept. Spotting a theme common across the many amazing conversations they have subsequently, Bob and Ted decide to follow the XP principle of doing extreme amounts of the practices that work: they implement the world's first completely Darwinian complex systems risk management program. 45 236 Julian Everett Grand Ballroom A 3 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z I propose that the larger issue with Agile Contracts is not that we don't know how to write them. After all we know how to deliver Agile projects, so a contract can simply describe that process. The problem is with making Agile Contract commercially competitive; against suppliers who are offering the promise of delivering the perfectly predicted dream - offering the certainty that people crave. This is a prisoners dilemma, with organisations driving themselves towards a sub optimal solution. Through game theory we will explore ways in which to improve the appeal of the agile offering. 90 238 Simon Bennett Grand Ballroom A 3 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z The "pomodoro technique" is a simple tracking and feedback process where the unit of work is the "pomodoro", a time slot of 25 mins. In this tutorial I'll give you advanced practical advices on how to implement the daily pomodoro practice, common pitfalls, tools you may find useful and how to read and use pomodoro metrics and answer questions like: what did I do the last week, on which tasks I spent most of the time, how frequent is the context switching. Hopefully after this talk you'll be able to go back to your team and give pomodoros a try with all the practical information needed. 90 246 Renzo Borgatti Grand Ballroom C North 15 19 2009-08-13T08:25:40Z 2009-08-13T03:46:00Z The software development industry has a poor track record with metrics. Many metrics are tangential to development's goal of delivering business value, and are thus ill-regarded by agile developers. However, good metrics are important to management, in order to understand the status and progress of their teams, and to make projections into the future. In this class we discuss velocity, burndown graphs, EVM metrics (CPI and SPI), and earned business value, including methods for calculation, why they're important, and how they enforce (or fight against) agile values. 90 248 Dan Rawsthorne Crystal C 4 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 253 George Schlitz, Giora Morein Regency D 1 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z We want to deliver maximum business value. Prioritising is easy if someone assigns business value to each story. How do you estimate business value? How should you prioritise between stories, projects or clients? The aim of the game is to deliver maximum value. Your development team only has a finite capacity, so you're going to have to make some tough choices. We provide the clients and their requests. We suggest techniques for estimating business value. The rest is up to you. The game teaches you how to build and use a Business Value Model to deliver maximum value. Max. 28 players 90 257 Portia Tung, Pascal Van Cauwenberghe Plaza Ballroom B 12 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 263 Scott Ambler Regency C 2 32 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 266 Tom Sulston Grand Ballroom B 12 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 284 Alan Atlas Regency C 2 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Do you understand why your team behaves the way it does? In this session, you’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). 90 286 Barry Rogers, Ken Howard San Francisco 9 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 323 Joe Sokohl, Todd Zaki Warfel Acapulco 16 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 324 Todd Zaki Warfel Acapulco 16 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Agile methods put a great deal of emphasis on trust, empowerment, and collaboration. Agile moves us away from command and control project management toward an approach designed to harness the passion, creativity, and enthusiasm of the team. Mike will tackle the assumptions behind traditional project management and explore a more agile approach to managing time, cost, and scope. He will address the PMI Processes and Knowledge areas and explore how to adapt them to agile projects. Participants will leave with practical tips they can implement today to begin building a culture of agility. 90 333 Mike Cottmeyer Crystal A 5 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 341 Steve Adolph Columbus IJ 6 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 343 Mike Dwyer Atlanta 1 30 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Spending more time maintaining your tests than your code? Started to write tests only to be discouraged by the complexity involved? Imagine if you could implement robust automated testing on even your most complex projects by simply writing one extra line of code… Now you can! Regardless of which testing framework you use, Approval Tests allow you to painlessly capture tested output in a visible, verifiable, and automated way. Particularly useful in the context of writing tests for legacy code, GUIs, databases and web pages, this open source solution is as pretty as a picture! 90 346 Llewellyn Falco, Daniel Gilkerson Grand Ballroom C North 15 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 375 Steve Johnson, Laureen Knudsen Crystal C 4 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z As the world becomes increasingly “flat”, 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 “carrier pigeons,” a metaphor for tools (technology and practice) used to overcome the challenges of distance. 45 376 Giora Morein Plaza Ballroom A 8 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z After revolutionizing the automobile industry, Lean principles have been applied to different knowledge areas, such as software development. However, many people haven't been introduced to the concepts that made Lean successful. In this interactive session, the participants will work in a small Lego production line, experiencing the problems and applying Lean practices to overcome them. 8 to 20 participants, divided in 4 teams, will learn about: systems thinking, push vs. pull systems, waste, etc. We will also compare the production line scenario with the software development industry. 90 397 Danilo Sato, Francisco Trindade Grand Ballroom B 12 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Automating your build process with Continuous Integration is certainly a great idea, but why stop there? Why not go the whole nine yards and automate the deployment process as well? Staging and production deployments are typically more complicated and more involved than a simple development deployment, but doing them by hand can be time-consuming, tricky and error-prone. Indeed, turning your staging and production deployments into a one-click affair has a lot going for it. 90 399 John Smart Grand Ballroom E 15 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 400 Ola Ellnestam Grand Ballroom B 12 31 2009-08-13T08:17:59Z 2009-08-13T03:46:00Z 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. 180 401 Sumeet Moghe, Jonathan McCracken Plaza Ballroom A 8 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 402 Guillaume Tardif, Eric Lefevre-Ardant Grand Ballroom F 7 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 — well — a lot better. This is a close-repeat of a successful session we gave at Agile 08. 90 403 Patrick Wilson-Welsh, Corey Haines Columbus KL 7 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z A Continuous Integration system is often considered one of the key elements involved in supporting an agile software development and testing environment. As a traditional software tester transitioning to agile environment, it became clear that we would needed several changes to make the transition to agile testing possible. This experience report discusses a continuous integration implementation I led last year. The initial motivations, technical specifics of the implementation, perceived benefits to the team, and retrospective results are all discussed. 45 406 Sean Stolberg Grand Ballroom D North 14 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Those who attend conferences or read books and articles discover new ideas they want to bring into their organizations—but they often struggle when trying to implement those changes. This session offers proven change management strategies to help you become a more successful agent of change in your organization. Learn how to plant effective seeds of change, and what forces in your organization drive or block change. Come and discuss your organizational and personal change challenges. 180 407 Linda Rising Regency C 2 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z The power of the placebo is based on our brain's belief system. Because we believe the medication can work it does. I wonder if there is some of that placebo effect in our successes with agile? Could it be that all our successes are really a matter of proper expectation? It often seems that the software industry is seeking one magic potion after another. We embrace the latest and greatest and hope it will cure our ills. Is agile just the latest elixir? 90 408 Linda Rising Regency D 1 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 “flow” of an agile project differs from more traditionally managed projects. 90 409 Jim Highsmith Grand Ballroom B 12 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Traditional development emphasizes “following a plan with minimal changes,” whereas agile stresses “adapting successfully to inevitable changes.” 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. 90 410 Jim Highsmith Crystal B 10 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 “spurious” information such as “how much is this project going to cost,” or “how long is this project going to take?” 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 90 411 Jim Highsmith Crystal A 8 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Behavior-Driven Development, or BDD, is an excellent development strategy that can help bridge the traditional gap between requirements and implementation. This talk will go discuss the basic principles of Behavior Driven Development, and look at how it builds on and differs from "traditional" Test-Driven Development. This session will demo two BDD tools: JDave, an open source framework that incorporates BDD concepts into JUnit, and easyb, a DSL-based behavior driven development framework for Java that uses Groovy to let you pretty much write tests that document themselves. 90 415 John Smart, Lasse Koskela Grand Ballroom E 15 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This presentation illustrates, using an animated Agile Story Card Wall, the concepts of Lean's Work in Progress, Drum–Buffer–Rope from Theory of Constraints and Systemic Thinking from Peter Senge’s The Fifth Discipline. The presentation, originally inspired by the MIT Beer Game, uses Flash animation to show the flow of story cards across a Story Card Wall over 10 iterations, demonstrating the effects on the team’s throughput as a result of a staffing decision made during the project. The presentation also includes an Excel spreadsheet to do ‘What If’ scenarios. 90 431 Tom Looy Regency A 9 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 432 Rod Coffin Grand Ballroom C North 15 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z We struggled with long-running, complex builds and difficulty in sharing code across multiple projects. We started using Maven to simplify our builds. This lead to many more benefits that we didn't expect. It also minimized the overhead costs of extracting, introducing and maintaining new modules. This provided a path for us to move away from a few monolithic slow builds to many small, lightweight fast builds. Using conventions improved cross-team communication. Managing dependencies, versions and performing releases have all become trivial. Maven is a wonderful tool for enhancing agility. 45 434 Tim Andersen, Luke Amdor Grand Ballroom E 15 12 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Of the many benefits of agility, none is more transforming than the power of self-organizing teams. Yet, building such teams remains one of the most elusive goals. This is due to the challenging transition functional managers must make to develop the right organizational environment for teams to mature. This session is for managers who are challenged in building strong self-organizing teams. This session will develop your agile organizational leadership awareness and competencies to build committed, disciplined and self-organizing teams who share responsibility. 90 438 Pete Behrens Crystal B 10 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z There is no better way to gauge an organization’s culture than to watch its meetings - usually dull and lifeless. Meetings are often cited as one of the most wasteful activities in business - yet Scrum demands more meetings more often. Engineers find themselves micro-managed with little time left to get “real” work done. This session provides leaders a whole new perspective and techniques for Scrum Meetings in building high-performing disciplined teams through focused, active, engaged, visual and time-boxed facilitation techniques to take teams from DOING Scrum to OWNING Scrum! 90 440 Pete Behrens Regency D 1 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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é * visibility * joy 45 444 Brian Marick Columbus GH 11 32 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In the battle of YAGNI and the performance testers, who wins out on an agile project? Join us as we walk through a historical account of what happens when you need to meet heavy performance targets on an agile project. Find out what was at stake, and the dire consequences if either side annihilated the other. We'll focus on technical detail, planning and management techniques that led to the only outcome, collaborative success! Finally, discover the impact this battle had in the war agile wages to align the needs of end customers, the business, and IT, to see how it all worked out. 45 445 Alistair Jones, Patrick Kua Grand Ballroom D North 14 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 & 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. 90 447 Ade Miller Grand Ballroom C North 8 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 448 Ade Miller Atlanta 1 7 2009-08-13T08:28:32Z 2009-08-13T03:46:00Z Increasing gender intelligence strengthens our ability to maximize the contributions of all members of the team while maintaining both equity and uniqueness. New research from neurobiology sheds light on the real differences in male and female brain structure, chemistry, and blood flow. This data underlies the emerging science of gender intelligence, providing a new vision of gender relationships. Gender-intelligent supervision, employee coaching/mentoring and negotiation and conflict management leads to a competitive edge in the toolkit of forward-looking companies. 90 468 Sharon Buckmaster, Diana Larsen Crystal A 5 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z When my Scrum-style backlog grows up, it wants to be an FDD feature list ... or is it the other way round?' Why does Feature-Driven Development (FDD) organize its feature lists into a hierarchy? Why does FDD use a specific template to name the items in a feature list? While a Scrum-style backlog for a single team may never grow to more than a couple hundred items, backlogs serving multiple teams may easily do so and become hard to work with. We compare Scrum-style backlogs and FDD-style feature lists, and consider the relative merits of different ways of working with large backlogs. 45 469 Stephen Palmer Grand Ballroom A 3 14 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Agile coaches often need to distinguish when people "do" an agile practice versus "really understand" 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 "going agile". 90 471 Patrick Kua, Elizabeth Keogh Crystal A 5 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z You’ve read about agile, heard about agile, and your company is probably using it in some form by now. Here’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. 90 476 Glenn Bernsohn, Michael Walkden Grand Ballroom B 12 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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’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. 90 480 Janet Gregory Grand Ballroom D North 14 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 180 482 John Smart Grand Ballroom E 15 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z An Exercise in Agile Facilitation - http://agilejournal.com/articles/columns/articles/1233-the-invisible-project This session focuses on an approach taken by Agile Project Managers to develop empowered and effective teams using a series of techniques focused on trust, transparency, team dynamics, and agile facilitation. More so, ensuring that the Project Manager does not end up as the central figure dominating the project is equally critical, highlighting that it takes an unselfish personality to create a truly self-organizing team. 90 487 Mack Adams Regency A 9 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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). <!--break-->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. 90 494 Scott Dillman New Orleans 7 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z To make lasting changes, we need to visualise the situation, understand the system, know how to improve it and work together. The Theory of Constraints tells us how to do all that. In this game, we apply the ""Five Focusing Steps"" process improvement method from ToC. Step by step we use Agile, Lean and Real Options techniques to make our ""work"" more fun and productive. After the simulation game, you'll be able to apply these techniques to your work. You'll be able to use the open source ""Bottleneck Game"" to share these techniques with others. Max. 28 players 90 503 Pascal Van Cauwenberghe, Portia Tung Grand Ballroom A 3 17 2009-08-13T08:26:50Z 2009-08-13T03:46:00Z Have you ever been told to multitask–working on so many projects simultaneously you don’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’t set direction for themselves and other people. When leaders decide which projects people work on in what order—the project portfolio—they set the stage for success. But those decisions are not easy. We will see what a portfolio is, what it is and isn’t, and we’ll explore how to make collaborative decisions. 180 508 Johanna Rothman San Francisco 9 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z The Agile Alliance states that "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." 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. 90 512 Aaron Sanders, Jeff Patton Toronto 9 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 517 Elizabeth Keogh Regency B 5 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This session covers a successful transition to a new business model in a limited time span. Typically, Iowa Student Loan (ISL) sells bonds to fund the creation of private student loans. As financial markets deteriorated in 2008, the potential of successful bond sales diminished to the point of nonexistence. Heretofore, our systems assumed ISL as the only lender. Collaborative bank relationships changed this assumption to one of multiple lenders. A redesign of the loan program/loan type structure of our software followed to make the funding model very configurable. 45 522 Justin Davis, Tim Andersen Columbus IJ 6 24 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z The design goal for Scrum teams is 5 to 10 times waterfall performance yet the majority of Scrum teams never achieve this goal. A pattern is emerging at MySpace in Beverly Hills and Jayway in Sweden, for bootstrapping high performance Scrum teams. Rigorous implementation by an experienced coach creates a total immersion experience akin to Shock Therapy. Unfortunately, management disrupts hyperproductive teams by removing key resources. Velocity data is provided on five teams at MySpace and one team at Jayway where management repeatedly “killed the golden goose.” 45 524 Jeff Sutherland, Scott Downey Atlanta 1 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In the nature vs. nurture debate, researchers have declared nurture the winner. People who excel are the ones who work the hardest; it takes ten+ years of deliberate practice to become an expert. Deliberate practice is not about putting in hours, it’s about working to improve performance. It does not mean doing what you are good at; it means challenging yourself under the guidance of a teacher. Unfortunately, our organizations are not set up to develop experts, nor do agile practices encourage them. So how will we develop the experts we need to improve? 90 526 Mary Poppendieck Columbus GH 11 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Scheduling should be done independent of and orthogonal to workflow. In fact, you don’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. 90 532 Mary Poppendieck Grand Ballroom F 6 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 542 Gerard Meszaros Grand Ballroom C North 7 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Many agile methodologies assume a customer (or product owner) walks into the room with a swack of money and a pile of story cards and tells the development team to start building the functionality described on the top few cards. This tutorial provides an overview of what needs to go on “behind the scenes” between when a project is conceived and when development can start in earnest. It identifies the artifacts that may need to be produced, whether and when they should be produced, which activities can be used to produce them and who should be involved in those activities. 90 543 Gerard Meszaros Crystal C 4 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z The introduction of Scrum at a CMMI Level 5 company doubled productivity and cut defects by 40% compared to waterfall projects in 2006 by focusing on early testing and time to fix builds. Systematic institutionalized Scrum across all projects and used data driven tools like story efficiency to surface Product Backlog impediments . This allowed them to systematically develop a strategy for a second doubling in productivity. Two teams have achieved a sustainable quadrupling of productivity compared to waterfall projects. We discuss here the strategy to bring the entire company to that level. 45 545 Carsten Jakobsen Columbus GH 11 24 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z By now, your company has made the transition to Agile. "Sprints", "backlogs", and "retrospectives" are everyday words, but you’re also discovering the serious challenges that software agility brings to product management. The Product Owners, who have been scattered across multiple teams, are not cohesively aligned around the same prioritized set of corporate initiatives and strategies. In addition, there are cross-product dependencies that are not being effectively recognized and addressed. My company's solution was to build a single, enterprise level, Unified Backlog. 45 551 Marie Kalliney Crystal C 4 22 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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! 90 553 J. B. Rainsberger Grand Ballroom B 12 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In 2005, Microsoft’s DevDiv (with 2000 participants and 40 million lines of code) overhauled its engineering practices to improve agility, quality, and customer satisfaction. Four years into the journey, *customer satisfaction has increased dramatically. Product quality improved 10x. Velocity improved 2x, with schedule time for major releases was cut by eighteen months and quarterly releases of “power tools” allowed incremental delivery to external customers.* Practices that change include planning, org, quality gates, branching, testing, tooling, reporting, backlogs, transparency. 90 560 Sam Gucikenheimer Regency D 1 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Facilitation skills are essential for anyone. In fact, *everyone facilitates whether they know it or not*! Do you work on a team, manage an organization, or otherwise work with others? The opportunity to facilitate *will* come up. Steven ""Doc"" List will lead you to explore the common patterns & antipatterns that come up in facilitation, for the facilitator and the participants. We'll have some fun by taking on roles, and exploring the behaviors that work and that don't work. The session will include some time on specific activities and techniques that can be used for effective facilitation. 90 562 Steven "Doc" List Regency A 9 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 572 Tom Sulston Grand Ballroom E 15 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Flirting is about connecting. A German university now requires their IT engineers take a flirting class—not to attract a partner, but to learn how to interact more effectively in the workplace. We will explore how flirting techniques translate to use in a business setting—inspiring us to create stronger connections with our customers. Our 8 Steps to connecting with your customers will help teams better understand customer requirements and build business value. “Flirting” With Your Customers creates the connection that can make a significant difference in a project’s success. 90 573 Jenni Dow, Ole Jepsen Columbus IJ 6 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Why do testers on some agile teams find iterations productive and enjoyable, while other teams struggle to "keep up" with testing and get stories to "done done" within the iteration? Succeeding with agile testing is more than just automating tests or sitting with the developers. To create working software quickly, your whole team must be able to build a shared understanding of a feature - and do this rapidly, accurately, over and over again, every feature, every iteration. This hands-on tutorial teaches you how to use the agile technique of acceptance criteria to build shared understanding. 90 622 Kay Johansen, Zhon Johansen Grand Ballroom D North 14 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Agile teams practicing Acceptance Test Driven Development (ATDD) define acceptance tests collaboratively while discussing each story. This practice helps uncover assumptions and confirm that everyone has a shared understanding of "Done". During implementation, the technical team automates the natural-language Acceptance Tests by writing code to wire them to the emerging software. In this way, ATDD tests become executable requirements. This session is a demo of the full ATDD workflow from initial discussions to distilling tests into an automatable format to implementing code to the final demo. 90 641 Pekka Klärck, Elisabeth Hendrickson Crystal B 10 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This talk focuses around a series of diagrams that help explain how various practices work. Many practices work to different degrees of success depending on exactly how they're implemented. We'll discuss why this is so, with examples of multiple ways to do pair programming, testing, and planning. Along the way, we'll show some new work: how to get a better plan by not estimating, models to identify which practices to experiment on, and how to find what to vary. Each concept will be explained with diagrams that get to the gist of the practice - and methods of thinking about variations. 90 649 Bonnie Aumann, Arlo Belshee Atlanta 1 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Any successful recording artist eventually submits to releasing a “Greatest Hits” album. This is the opposite: a beat-up XP coach putting his biggest and furthest-reaching mistakes in a neat package and releasing them to the public. This talk could also be named “Ten ways to guarantee your Agile transition is a total failure”, or “Apologies of an XP coach”; however I’m sure I’ll mention more than ten mistakes and I make no apology for them. 90 650 J. B. Rainsberger Regency B 5 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 ""the Agile conference"" is holding the development of modern SW development practices back. This session will be in debate form to discuss the above mentioned motion. 45 656 Bas Vodde, Steven Mak Grand Ballroom A 3 6 2009-08-13T08:28:49Z 2009-08-13T03:46:00Z When most people think of the phrase "Agile won't work here" 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 "cook's tour" 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. 45 658 Daniel Markham Columbus GH 11 30 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z We know why engineers use agile but should Executives fund it? Through this panel discussion learn the benefits of Agile 4 those that hold the checkbooks: *Why Executives should see Agile as a necessary change *Benefits of Agile 2 an enterprise business, including non-engineers *Justify funding 4 training, tools, etc *Link Agile metrics 2 the balanced scorecard without compromising the principles of Agile Industry leaders Stephen Williams (HP), Laureen Knudsen (Qualcomm), and Israel Gat (BMC) tell how they use Agile 2 positively impact all areas of large, global, corporations 90 681 Laureen Knudsen Atlanta 1 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z We find games and simulations incredibly valuable in our coaching and training. Given the number of times we've seen "Does anyone have a game or simulation to ... ?" 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. 180 705 Elisabeth Hendrickson, Chris Sims Columbus GH 11 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 708 J. B. Rainsberger Columbus IJ 7 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Continuous Testing (CT) is a developer practice that shortens the feedback loop established by Test Driven Development. It gives you near instant feedback about the correctness of your code, and helps you find bugs as quickly as syntax errors. This session will cover how CT has evolved in the last year, it's current capabilities, and limitations. The presenters will also show several demos of the practice using freely available continuous testing tools, and examine how these tools can be integrated with existing infrastructure to bring the benefits of CT to a wider audience. 90 712 Ben Rady, Rod Coffin Grand Ballroom C North 15 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 713 Ben Rady Grand Ballroom B 12 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z How do you scale Scrum to hundreds of people? This presentation will explain a way of organizing your development so that it scales up well. It involves breaking the link between architecture and organization, breaking code ownership and organize the development in a more customer centric way. This has its drawbacks too! These are explained and some techniques for overcoming these drawbacks are discussed. This talk is based on the "feature teams" and "requirement areas" chapters in the recently published "Scaling Agile & Lean Development" by Bas Vodde and Craig Larman. 90 715 Bas Vodde Regency D 1 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 – and the biggest potential roadblock – 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. 90 727 Mike Russell Columbus KL 1 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In replacement projects one of the biggest questions is what strategy to use in replacing the old system. The simplest strategy is to wait until the new system is "at least as good as the old one" before switching. Although this strategy sounds compelling it has many serious drawbacks. An alternative strategy is based on what I call a "Minimal deployable entity". Switch systems when you have just enough to be able to survive with the new system. The concept is similar to "Minimal Marketable Feature" but more focused on deployment strategy. But how do you identify the Minimal deployable entity? 45 736 Niklas Bjørnerstedt Crystal C 4 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 “quality of service” requirements), external interfaces, design and implementation constraints, and team or technical “stories” 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. 90 742 Ellen Gottesdiener Columbus IJ 6 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 747 Paulo Caroli, Sudhindra Rao Grand Ballroom F 7 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 (""as is"") and future state (""to be""), identifying the stories for the future state and teaches the participants how to use it on a mock project. 90 768 Shane Hastie Columbus IJ 6 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z A huge quality-centered activity in Agile teams is defining **“done-ness”** 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 – Complete 3. Iteration – Complete 4. Release – Ready and share examples and stories of how Product Owners should interact with their teams. 45 776 Bob Galen Crystal C 4 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Increase Productivity With Large Scale Continuous Integration Iteratively: Reduce Feedback Cycle From Weeks To 100 Minutes Using iterative development – create an continuous integration environment using open source and commercial tooling for hundreds of developers From migration to new environment – the tools and process lessons learned Effects seen in product development – real life experience after 18 months in production 45 782 Hannu Kokko Grand Ballroom E 15 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Animal behaviors such as Swarming, Flocking & 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. 90 800 Tom Perry, Dhaval Panchal San Francisco 9 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 806 David Kessler, Tim Andersen Regency D 14 28 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 – 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. 45 811 Gabino Roche, Jr., Belkis Vasquez Regency C 2 6 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z An agile-tester needs to wear many different hats to be effective in their role. Sometimes they have the 'Detective' hat on, sometimes the 'Scientist' and others the 'Police Officer'. Working in small groups we will create a taxonomy of the hats testers wear. Once a the list is produced we will then see which are the most common, enjoyable, frustrating, Agile and a number of other attributes. 45 839 Adam Goucher Grand Ballroom D North 14 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 859 Lars Thorup, Bent Jensen Grand Ballroom A 3 28 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z One of the challenges global teams are facing, is overcoming cultural differences. Yet, these differences have their origin not only in geography and language, but also in strategies, politics, values and history. A company, no less than the broader society, shapes a culture that influences its employees behavior. A distributed team needs to leverage this and jointly develop a project culture and keep the project history alive for emphasizing the common culture. This session points out techniques that have helped to create a common culture in different global projects I have been working on. 90 862 Jutta Eckstein Crystal A 8 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This hands-on advanced workshop teaches incremental Test-Driven Development, showing how to grow code one feature at a time. It will show: how to use tests at multiple levels to focus on requirements, how to use unit tests to drive the discovery of roles and responsibilities in your design; and how to write resilient tests that express your intent and don't break for irrelevant changes. The workshop is for programmers who want to improve their TDD practice. It has been presented at several conferences, one review from XpDay London was ""Incredibly useful; the best technical I’ve heard"". 180 863 Steve Freeman New Orleans 7 17 2009-08-13T08:26:23Z 2009-08-13T03:46:00Z Over the last ten years, Test-Driven Development has grown from something exotic, that only a handful of people knew about, to near- commodity. So there's nothing left to say, right? We don't think so. In this talk, we'll review some of the landmarks in the history of Test-Driven Development and what they tell us about how to develop software; the ideas, techniques, objections, and misunderstandings. We'll talk about our experiences of discovering TDD and what we've learned about how to do it well, how to adopt it, and how to bring it into existing code. 45 864 Steve Freeman, Michael Feathers Crystal B 10 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z As individuals we work in transient isolation to reduce the impact of work in progress on each other. Organizations isolate WIP by using only official versions of 3pty sources and by producing official releases for customers. Multi-stage continuous integration (MSCI) scales CI to large distributed environments by isolating work in progress at the team level. Changes move from individual to team to mainline as fast as CI allows, but stop on failure. MSCI is particularly important in a distributed environment where fixes to problems exposed by CI can be delayed by a full day. 45 872 Damon Poole Plaza Ballroom A 8 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This report shares the successful adoption of agile practices in redefining the support group in our IT Organization. The report includes a unique organization of a collaborative, team-based approach to handling support requests, benefits achieved, lessons learned, and the next steps towards continual improvements for the customer experience and excellence in software development & support. We describe how an organization can use an innovative approach to transform the culture and the effectiveness of the support organization from an operational cost center to a value-added thought partner. 45 873 Bhaven Sheth Atlanta 1 18 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 878 James Grenning, Bas Vodde Grand Ballroom F 7 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 879 ron carmel, Orit Hazzan Grand Ballroom D North 14 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Ever heard a programmer say ""I think the code's trying to tell us something""? A joke, right? A metaphor. There's a social world, where people tell people things, and there's a world of objects that, at most, exert passive pressure. But what if we deny that the two worlds are separate? What if we treat everything as a moving mashup of objects, ideas, individuals, and groups? This workshop will present some recent perspectives from sociology on that question, and will ask participants the following: if you believed in one of those perspectives, what would you do differently on your project? 90 882 Brian Marick, David Carlton Grand Ballroom A 3 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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’ts for teams who want to be counted as professional craftsmen. 90 908 Robert Martin Crystal B 10 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Dive deep into the topic of clean Java code by examining what makes a good function. In this talk you will look at a lot of code; some good and some bad. You will experience how such code is analyzed, critiqued, and eventually refactored. You will understand the decisions made by an expert in the field as bad code is gradually transformed into good code. How big should a function be? How should it be named? How should it be documented. How many indent levels should it have? How should it deal with exceptions, arguments, and return values. 90 909 Robert Martin Grand Ballroom F 7 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 915 James Shore, Diana Larsen Grand Ballroom A 3 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Two industries that extensively deal with risk are Investment Banking and Oil Exploration. As seasoned veterans involved in developing software in these industries, Chris and Todd will introduce a number of theories, tools and practices surrounding risk and risk management. They will share their practical experience using these techniques and approaches, explaining what works and what does not based on their experience and that of their colleagues. 90 926 Chris Matts, Todd Little San Francisco 9 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Being nearly agile has caused a number of new words to enter our vocabulary. They include "mini-waterfaull", "Scrum-but", "XP'ish", "w-agile", "fr-agile" 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! 180 934 Bob Hartman, Richard Lawrence Toronto 2 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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’s longer-term goals as well as short-term development needs. 180 951 Luke Hohmann Regency A 6 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Most sessions show us how to do various agile practices right. What is sorely lacking is the opportunity to learn how to do the practices wrong. How can we be expected to bring agile into an organization successfully without mastery of that key skill? Pairing isn't controversial, done effectively it: * reduces defects (by up to 86%, according to the 2000 University of Utah study), * improves productivity (up to three-fold, according to the 1975 US Army study) However, learning by doing wrong is actually an effective learning technique, and that's what you'll see here. 90 967 Brett Schuchert Plaza Ballroom B 12 17 2009-08-13T08:26:14Z 2009-08-13T03:46:00Z Imagine yourself with a team that flies in from AU, the UK, and US in bi-weekly shifts to work with a telecommunications giant. Mix in inexperience, a shared resource model, bad behaviours, and a mandated intro to Agile in a silo-ed non-agile environment. Couple this with a capability driven / satellite team who's focus is to assist other teams to drive out SOA: and you have a recipe for a Team in Flux. Working to find a system that worked for this team was a long and arduous journey full of misdirection, poor choices, and learning around structure, Agile methodologies, and people in general. 45 969 Sharlene McKinnon San Francisco 9 22 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 ""Kanban."" 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. 180 970 Tsutomu Yasui Plaza Ballroom B 12 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z One of the biggest problems when managing Agile projects is to decide when and how to integrate a story. Traditional versioning tools offer poor support to branching and merging so it's hard to select specific stories at the end of a sprint. In this talk, we present Git--a modern, distributed version control system--and an Agile versioning process using it that will help Agile Developers to solve those issues, offering a way to have a continuously releasable branch and also minimizing merging problems. 45 972 Tiago Jorge Grand Ballroom C North 15 16 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Join Esther and Diana, the authors of *Agile Retrospectives: Making Good Teams Great!*, on an interactive journey of __*Adventure*__. Follow the trail of a flexible framework for Retrospectives, a map for designing and leading Retrospectives. Retrospectives offer the greatest lever for project or process improvement—based on the solid data of a team’s immediate past experience of success and failure. The Adventure lies in holding Retrospectives throughout the project--capturing, managing, and disseminating technical knowledge and process wisdom to improve current and future projects. 180 975 Diana Larsen, Esther Derby Grand Ballroom B 12 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Panelists: Yael Dubinsky, Amr Elssamadisy, David Hussman, Linda Rising Moderator: Orit Hazzan Diversity can be expressed in different ways, such as, worldviews, minorities, cultures and skills. Studies tell us that diversity benefits with societies that foster it. Diversity is also perceived as a powerful management practice, and therefore, not surprisingly, diversity is introduced into agile environments. In the panel the panelists present their views at diversity, specifying how diversity can be expressed and fostered. 90 986 Orit Hazzan Regency D 1 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z If you’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’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. 90 998 Ole Jepsen Regency D 1 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 1010 Arlo Belshee, James Shore Grand Ballroom D North 14 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This stimulating talk starts by exploring the popular Technology Adoption Lifecycle, and how it relates to agile adoption. Next Ahmed illustrates how to practically “cross the chasm” between project-level and enterprise-wide agile adoption initiatives using a value-based roadmap. The roadmap, which consists of five steps (Collaborative, Evolutionary, Integrated, Adaptive, & Encompassing), is a result of 4 years of research and industry experience. Participants will see how to create their own value-based agile roadmaps as well as discuss key concepts related to enterprise agile adoption. 90 1029 Ahmed Sidky, Chris Sterling Regency C 2 11 2009-08-13T08:28:05Z 2009-08-13T03:46:00Z 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. 45 1080 David Starr, Eleanor Starr Columbus GH 11 26 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Could an executive team be happy using Scrum? Yes, it’s possible! Picture the scene: executives of strategic departments (financial, HR, IT, sales & marketing, production, etc.) being part of a cross-functional executive team…an executive Product Owner prioritizing an Executive Product Backlog that helps the team to follow the company’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. 45 1081 Alexandre Magno Toronto 2 30 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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: • The PM is complete waste. • The PM is a necessary part-time helper. • 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. 90 1097 Jesse Fewell, Pat Reed Regency A 9 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 1098 Beth Cohen Columbus IJ 6 32 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In this session, we'll test some real small to medium size applications for quality and bugs. Through three main activities of collation, investigation and prediction, we'll move through our explorations understanding applications then experimenting with discovery and failure situations, utilizing tools when relevant. While Erik will guide the session and explain the context, a large part of the testing will come from the audience, either as ideas or driving the keyboard. While this is accessible as an introductory session, it will also show how to perform industrial strength ET. 90 1099 erik petersen Grand Ballroom D North 14 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This session will introduce and demonstrate some of the free or near free tools available for a functional tester (or developer) to assist with test planning, execution, analysis and test support. We'll look at mind mapping tools, portable applications, firefox extensions, and various other tools including an amazing test data generator. These tools will help organize ideas, look "under the hood", verify compliance to various standards, record test results and assist in breaking software from a functional and security point of view. We''ll also look at some general tools as well. 45 1101 erik petersen Grand Ballroom E 15 18 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Ok, maybe we exaggerated a bit. CI deployments focus on the testing and deployment of the application. The 'world' (OS, Application & DB server) within a CI doesn’t change that much. But what if you could define your applications environment from a kind of ‘source’ and build and unit test it? f.i. Test security patches by using unit tests of your application? Using the concept of a pipeline we will show how to use existing tools/concepts for a Continuous Build for your Infrastructure allowing you to better integrate your production environment. Your sysadmin might even get interested? 90 1125 Patrick Debois Grand Ballroom C North 15 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Agile designers need to quickly see the essence of a problem and shape reasonable solutions. When things don't go according to plan, they must react, readjust their thinking, and try again. Seasoned agile designers strike a balance. They know the difference between core and revealing design tasks and plan accordingly. When unanticipated difficulties crop, they adapt their work rhythms. This tutorial introduces techniques and vocabulary for articulating design solutions and simple measures of technical debt and different kinds of development work. 90 1140 Rebecca Wirfs-Brock New Orleans 7 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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&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’s. 90 1141 Israel Gat Crystal B 10 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Most of the software world has realized that BDUF (Big Design Up Front) doesn't work well in software. But lots of developers struggle with this notion when it applies to architecture and design. Surely you can't just start coding, right? You need some level of understanding before you can start work. This session describes the current thinking about emergent architecture & design. This philosophy allows you to specify only the critical items up front and allow the important architecture and design criteria emerge once you understand the problem better. 90 1146 Neal Ford Grand Ballroom F 7 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Integrating customer feedback into an agile process is a challenge. Iterations are short, and finding time for research, design & development means making sacrifices. In this session we'll talk about finding organizational allies who can become collaborators in customer feedback tasks, getting effective & timely results, & potential pitfalls. Enlisting your organization in these efforts builds a customer-centric culture and provides the team with critical input. Examples will be drawn from our experience at Viget Labs re-designing the international web presence of a global hotel chain. 90 1161 Jackson Fox Columbus KL 16 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Three basic tools - pen, paper and a kitchen timer - will give you Agile values like… * Constant feedback about your working habits * Dedicated decision points to respond to change * Opportunities on a day to day basis to improve your personal process * A sustainable pace even when the deadlines are getting closer * Improved quantitative and qualitative estimates * Strategy for coping with interruptions and task switching * Ability to regulate complexity The Pomodoro Technique is a personal Time Management method and it fits perfectly inside Scrum and XP. 90 1179 Staffan Noteberg Crystal B 10 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 1194 Stevie Borne Regency B 5 8 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z I think Pair Programming is vital to the success of a programming team, but every time I join a new team I seem to find I'm in a minority of people who feel that way, let alone have any experience of actually doing it. This is not a session about convincing a manager that it's a good idea: let's assume he or she trusts you to do whatever is right for the project. This is about exploring, understanding and ultimately tackling the hidden influences which inhibit your peers from coming out of their caves and sharing their thoughts and ideas in regular, constructive, creative, pairing sessions. 90 1206 Matt Wynne Regency B 5 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 – 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. 90 1209 Brian Shoemaker, Nancy Van Schooenderwoert Regency D 1 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 1211 Daniel Wellman, Paul Infield-Harm New Orleans 7 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z The biggest risk to most projects is building the wrong product. Regardless of how fast your agile team becomes, nothing matters if you’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. 90 1217 Mike Cohn Grand Ballroom B 4 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z The technique of expressing requirements as user stories is one of the most widely applicable techniques introduced by the agile processes. User stories are an effective approach on all time constrained projects and are a great way to begin introducing a bit of agility to your projects. In this session, we will look at how to identify and write good user stories. The class will describe the six attributes that good stories should exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project’s initial stories. 180 1220 Mike Cohn Columbus IJ 6 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Planning is important, even for agile projects. Too many teams view planning as something to be avoided and too many organizations view plans as something to hold against their development teams. In this session you will learn how to break that cycle by learning and practicing skills that will help create useful plans that lead to reliable decision-making. You will learn about story points, ideal days, and how to estimate with “Planning Poker.” Both short-term iteration and long-term release planning will be covered. 180 1223 Mike Cohn Columbus IJ 12 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In 2007, OpenView Venture Partners decided to adopt Scrum as best practice in software development in its portfolio companies and Scrum as the standard practice in all internal operations. The OpenView Scrum teams aggressively remove all impediments (take no prisoners). Attached is a reference model that supports best practices in management, sales, marketing, finance, development, and customer support in OpenView portfolio companies. After over 52 weekly Sprints, OpenView is the first non-software Scrum to provide a working manual on how to do Scrum outside of software development. 90 1230 Jeff Sutherland, Igor Altman Crystal B 10 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Effective management of a software portfolio is a challenge that many companies ignore, avoid or fail to follow through because it is too hard. Many approaches to portfolio management get so complex that decisions fail to get made. In this hands-on tutorial we explore “barely sufficient” portfolio management and introduce a simulation game where participants make decisions about which investments a company makes. Participants will learn about product, project, and portfolio management issues tying decisions to strategy and purpose in order to optimize overall return. 180 1232 Todd Little, Kent McDonald Crystal C 4 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z One of the core values expressed in the agile manifesto is "working software over comprehensive documentation" because working software is what delivers value to our customers. Agile development requires a sofware development team have working software ready to deploy at the end of each iteration; but accomplishing this can be harder than it seems, especially when first starting with agile. In this highly interactive session you will understand how a team definition of "Done" is necessary to making agile delivery possible, and what you can do to make it happen while avoiding the pitfalls. 90 1236 Paul Rayner Plaza Ballroom B 12 19 2009-08-13T08:25:22Z 2009-08-13T03:46:00Z Using Google Docs you can create your own lightweight project management tools and through simple and powerful visual management provide the people involved with shared information that will give transparency into progress and problems Compared to most commercial project management tools using Google Docs is very flexible. That way the tools can be adapted to how the processes of the project continuously improve. And not the other way around. The demonstration is based on more than 2 years of experience using Google Docs for Agile processes in a distributed development context. 45 1247 Thomas Blomseth Christiansen, Bent Jensen Grand Ballroom E 15 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Anyone who's seen a user trying to get to grips with their application knows what a humbling experience it can be. No matter your design experience there's no substitute for testing with actual users. But the whole user testing process can seem daunting & costly in terms of time, effort & materials. Seeing this Jakob Nielsen proposed a lightweight approach, 'Guerilla User Testing', in the mid-nineties. It emphasized what could be done on limited resources by a team committed to providing a decent user experience. Marc & Luke share over 20 years of experience applying this type of technique. 90 1252 Luke Barrett, marc mcneill Columbus KL 16 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 1270 Jeremy Brown Grand Ballroom D North 14 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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’ve successfully implemented agile in large sized companies operating in a highly regulated world. 90 1275 J.R. Jenks, Tim Hughes Regency C 2 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 180 1276 Dean Wampler, Aslak Hellesøy Grand Ballroom C North 15 29 2009-08-13T08:18:35Z 2009-08-13T03:46:00Z Many Java teams want a more modern language that preserves their investment in Java technology. This talk looks at Scala, a new JVM language that fixes many of the limitations of Java. I'll show why Scala is an ideal ""upgrade"" language for most Java teams. Using examples, we'll see that Scala is statically-typed, yet it has a succinct and flexible syntax. Scala _traits_ add _mixin composition_ to Java's object model. Scala fully supports _functional programming_, which is the best approach for robust concurrent applications. All these qualities improve our agility. 90 1307 Dean Wampler Grand Ballroom F 7 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Coaching helps communities produce real value and grow sustainable agility. Successful coaches know the importance and value of treating each community as unique, helping the individuals and the larger community find a “groove” (style) that truly helps them deliver. If you are coaching or getting ready to coach, and you want to learn a pile of pragmatic coaching tools, based on years of coaching agile projects, this session will pass your tests. 180 1319 David Hussman Regency B 5 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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). 45 1326 Andy Slocum Grand Ballroom A 3 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 1335 Jeffrey Fredrick, Paul Julius New Orleans 7 28 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Field-tests about how personal responsibility works in the mind (i.e., how we avoid it and how we take it) now make it possible for coaches to understand and teach the mental processes, language, and keys to personal responsibility. Cool huh? Doing so inspires your charges to demonstrate far greater ownership behavior as individuals, teams, and even as entire enterprises. You add more value as your charges take ownership and learn, correct, and improve more easily, directly, and quickly. Come acquire the basic tools and practices for coaching success with personal responsibility. 180 1377 Christopher Avery, Ashley Johnson Regency B 5 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z One of the core values of the Agile Manifesto is favoring “Customer collaboration over contract negotiation”. Unfortuntely, product companies with thousands (to millions!) of customers can find collaborating with their customers nearly impossible, as few tools exist to explicitly support meaningful customer collaboration. This workshop explores the advantages of including your customers as part of your distributed team and some of the tools that are emerging to enable agilists to better collaborate with their customers. Bring your laptop, as we may be trying out some of these tools. 45 1381 Luke Hohmann Crystal A 8 12 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z I've been on teams with way too little and (heresy) way too much testing. There have been lots of talks about how you should test more, but I'm going to dare to talk about when you should test less. Too much testing can lead to backlash, gridlock, morale problems, and poor velocity. Of course lack of testing can lead to bad design, gridlock, morale problems, and poor velocity. The level of testing a team can support depends on many factors including: team size, developer buy in, managerial approval, company size, IT support, and testing experience. 45 1394 Jake Scruggs Grand Ballroom D North 14 24 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z It is the late-80’s and the U.S. Department of Defense is rolling out a new state-of-the-art system for scheduling satellite tracking stations that uses a text-driven display and communication over serial lines. Now 15 years, 3 failed replacements and over 20 million tax payer dollars later a final attempt at replacing the crippled system gets underway…using Agile. This experience report will cover the challenges faced developing a critical application in iterations while satisfying the customers requirement that deliverables be made using the traditional waterfall lifecycle. 45 1407 David Morgan Atlanta 1 12 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z How's your Behaviour Driven Development? Healthy, sick or new-born? Drop in to the clinic at any point during the session and find out. Bring your code, tests, examples and scenarios in to the experts for a thorough check-up, diagnosis and prescription. We can give your code base a full going-over, from business value through unit tests, mocking, and code. Got problems? Not sure who to talk to? Just making sure everything's all right? Let us help! We are able to work with Java, C# and Ruby, and will consider other species if you can describe them to us. 180 1414 Pat Maddox, Elizabeth Keogh New Orleans 7 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 1417 Daniel Vacanti, Stephen Palmer Grand Ballroom A 3 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 1431 Lisa Moore, Christian Gruber Regency B 5 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In these turbulent times, businesses need people with specific characteristics and attitudes to enable survival and success. It turns out these attitudes and are very similar to what is needed on an Agile project team. This talk examines what attitudes and perspectives team members need to be successful on Agile projects, how these can contribute to overall organisational success and how to encourage and instil these attitudes in a team. 45 1521 Shane Hastie San Francisco 9 24 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 1528 Jeff Sutherland, Guido Schoonheim Crystal A 8 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Admit it. You've always wanted to know how people are actually using that product you spent so much time developing. That can be done more quickly than you've seen before and it can improve your product a lot. If we can include some UX activities into the kind of under-pressure operation that the Obama For America campaign ran, there is hope for any Agile project. We traveled to Obama offices in swing states studying the campaign's operation to help inform the redesign of campaign software. With pictures and video, we will present what we learned, and how you can apply it to your projects. 45 1539 Billy Belchev, Paul Baker Columbus KL 16 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In a large agile organization (more than three teams or 30 team members) with self-organized empowered teams, R&D leadership roles still exist to support these teams through topics including resource management and strategic vision. This talk will highlight these R&D leadership roles, describe several example R&D organization structures, and then describe the behaviors (good and bad) stimulated by these structures, the challenges, and their impact on the teams. The talk concludes by describing the key attributes of leaders who will thrive in a large agile organization. 45 1564 Erik Moore San Francisco 9 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 1574 Rob Myers, James Shore Regency A 9 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z The use of metaphorical games as a strategy for adopting an agile culture has shown to be weak because most of trainers don’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. 90 1587 Luiz Claudio Parzianello, Rafael Prikladnicki Crystal A 5 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 1594 Eric Willeke Toronto 2 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Given the size and scope of Google's code base, and speed of development, typical off-the-shelf continuous integration are unable to meet our needs. So, we decided to create a continuous integration and testing system as a centralized service on an unprecedented scale. When fully completed and operational, it will probably be the world's largest continuous integration and testing system, running millions of tests every single day. In this talk, we will report on our experience running such a program in an agile manner and will also describe the basic design and features of the CI system. 45 1606 Mark Striebeck Crystal B 10 22 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Setting a clear and engaging vision is challenging and critical for successful projects, so we have evolved an approach that allows teams to articulate the vision by telling the story of a customer’s experience with your product. We will show you how to map the journey, identifying areas for technology innovation and key features along the way that will help to create a product that people love to use. Many people can find empathy with a character and their story. This helps in creating a compelling product vision and communicate benefits in order to secure funding. 90 1620 Matt Roadnight, Una Walsh Columbus KL 16 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 45 1650 Keith Voos, Ami Hileman Plaza Ballroom A 8 26 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 ""Project Planning Jam Session"", 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 – it instantly improved the way our teams developed project plans. 90 1690 Alistair Cockburn Grand Ballroom E 10 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Pragmatics is an agile development shop rated at CMMI Maturity Level (CML) 4 and striving to achieve CML 5. By maturing our agile disciplines, we feel we will not only improve the performance of our agile teams, which will ultimately benefit our agile development practices regardless of our appraisal rating, but will also lead to our being appraised at CML 5. We feel that a mature, highly disciplined agile development company rated at CML 5 will be very intriguing to potential customers looking for contractors that can deliver on time quality products. That is, we feel they will flock to us. 45 1704 Sean Cohan, Hillel Glazer Grand Ballroom A 3 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Test Driven Development (TDD) is not just about the tests. Test Driven Development is also a design discipline. In fact, many TDD veterans prefer using the acronym to refer to Test Driven Design. So, how exactly does TDD improve design? TDD improves design by making the developer more aware of fundamental design principles. TDD does not force good design. TDD rewards for good design and punishes for bad design. Through test-first development, design principles are moved from abstract, academic concepts to concrete needs. 90 1708 Eric Anderson Plaza Ballroom B 12 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z To enable the Agile Value “Courage”, 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 90 1793 Thomas Walker, Werner Wild Regency B 5 31 2009-08-13T08:16:47Z 2009-08-13T03:46:00Z We talk about collaborating to get great results from Agile, yet so few teams do it well (if they even try it at all). Sure, they cooperate, but collaborate? That's a different story. My teams couldn’t collaborate, even when they explicitly tried. This failure led to such an epidemic of mediocrity that I turned to a professional for help. I turned to an actor. Come to this session to learn what I learned from the world of theatre and to practice the exercises that helped my teams build their collaboration muscle so that you can do the same with yours. 90 1808 Lyssa Adkins Crystal A 5 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 ""Leading Teams"" 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. 90 1809 Liz Sedley, Rachel Davies Regency B 5 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 1835 Katarina Thomas Regency C 2 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 "gelled" teams, through "Group Pair Programming" -- 6 individuals, 1 workstation. 45 1866 Ken Kolchier New Orleans 7 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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! 90 1898 Xavier Quesada Allue Columbus GH 11 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 1914 Chirag Doshi Regency D 1 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This tutorial focuses on lessons learned from our experiences in implementing Agile in teams across different time zones in large companies. We will share the pleasure and the pain, ideas that worked as well as ideas that didn’t. We will share what we feel are the critical success factors in making program level implementations successful and sustaining. This is more than an experience report - we share templates, pictures, lessons learned for leveraging technology, managing multiple time zones, recommendations for metrics and reporting, and ideas for future program level success. 45 1922 Tamara Sulaiman Crystal A 8 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This tutorial, the "small card game", is a simulation game introducing the concepts of Agile planning, story value, and story cost. Learn to manage scope and optimize return on investment. The students practice planning a project with varying levels of information about the features needed, and experience how "nature" deals with their plan. Again, very appropriate for all team members, in-house customers, marketing, and management, to learn how the process works and what their part in it is. 90 1944 Chet Hendrickson, Ron Jeffries Columbus IJ 6 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z It is unfortunate, but true: for many teams error handling is an afterthought. They design the main flows of their system and then they think about where they need exceptions and logging. However, the error cases are extremely important. When we consider them along with the normal cases, we an often find ways to arrive at better design. In this workshop, we will pursue design a series of solutions to the same problem with the error cases considered early and late. Then we will compare and contrast solutions and see how early consideration of cases can affect the growth of a design. 90 1953 Michael Feathers Grand Ballroom F 7 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This is a highly participative workshop for delegates to learn more about collaborative and organisational storytelling. Personal stories will be told, retold and analysed, to investigate underlying values, through a series of collaborative story-games. Collaborative storytelling will be explored as an activity for team building, coordination and problem-understanding. Attendees will participate in generating ideas for a set of story-cards that could be used to help teams explore their own values, beliefs and concerns through collaborative storytelling around software projects. 90 1989 Johanna Hunt, Rachel Davies Columbus GH 11 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Agility in Action… 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. 90 2001 Tobias Mayer Grand Ballroom A 2 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Transitioning 25,000 developers to agile development processes is a challenge on its own—and making the transition during a global recession is even more ambitious. Join Sue McKinney as she discusses her experiences leading the move to agile at IBM, how their agile teams often struggled, and ways leaders provided support and understanding at many levels. As the global recession set in, Sue looked for tools leaders could use to increase productivity—even after cost cutting—and unleash the talent and innovation agile teams need to continue succeeding. 45 2004 Sue McKinney Regency A 9 20 2009-08-13T08:24:49Z 2009-08-13T03:46:00Z Want to improve your team? Take a drama class! Want to measure how your agile adoption is going, take a business course!! This session explores the often overlooked practices in other industries for inspiration on improving agile practice in software development. From waste management and lean manufacturing to understanding motivational and sustainable development with NLP, I want to help people begin to look at things differently and perhaps find their own fixes from the rich variety of disciplines in everyday life that they can apply to agile software development. 90 2014 Mike Sutton Toronto 2 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Group Coherence (.com): Shared state allowing groups to perform tasks in rhythm and harmony with great energy to overcome obstacles. Evokes memories of fun, success, team bonding, desire to work together on future projects and improved group connection. Group characteristics are invisible and have to be felt. We are not trained to detect them any more than we could detect radio waves without a radio. We will Practice using group inquiry to: -Share your Agile GC experience -Identify GC ingredients and obstacles -Chart GC -Transform Agile practitioners to a coherent Agile group 90 2018 Joanna Zweig, Cesar Idrovo Columbus GH 11 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2021 ElMohanned Ahmed, Ahmed Sidky Toronto 2 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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’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. 90 2024 Amr Elssamadisy, Ashley Johnson Regency A 9 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This tutorial is a detailed look at several Agile practices and the HOWTO of Adopting each practice successfully. We will cover the business value delivered and the context where they are most effective. For each practice you will learn what steps can be done to effectively get from ""I want to do this practice"" to ""I'm doing it and getting obvious value"" and, just as importantly, what happen when things go wrong and how you can diagnose these difficulties. A variety of practices will be covered including: Stand Up Meetings, Iterations, Demos, Automate Developer Tests, and Refactoring. 180 2039 Amr Elssamadisy Toronto 2 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Bad build practices take a hidden toll on teams. It is not uncommon for a new developer to take days or even weeks to establish a functioning workspace. Good build engineers can make all the difference. By treating the build framework with the same respect as other source code they can help prevent these problems. In this clinic we will show how to refactor your build approach to end up with sustainable practices that get new people up and running quickly and set the stage for long term productivity. While the workshops are in Ant, the concepts are portable. 180 2043 Paul Julius, Jeffrey Fredrick Grand Ballroom F 7 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In a quick survey, 17 of 20 programmers said they didn't know how to slice feature requests to the sub-day level. In contrast, top programmers easily take them to 15-30 minute programming episodes. What does it take for people to make the transition? In this workshop, analysts and programmers will pair up, decompose an problem into initial requests, then the programmers will deliver those features in five 10-minute iterations, the analyst adjusting requests on the fly. This workshop works well with experienced programmers. Programming language and environment don't matter. 90 2069 Alistair Cockburn Grand Ballroom B 12 13 2009-08-13T08:27:19Z 2009-08-13T03:46:00Z What do you get when two developers try to implement agile without having experienced it? A 90 minute session on all the mistakes that were made. What can you do to avoid the same fate? We needed an agile coach, but want to help you do without. We'll present techniques you can use immediately. In this session, we examine the problems created by implementing an agile process incompletely and describe solutions to those problems. We offer the perspective of developers who learned what commitment really means and that there's more to agile than TDD and small releases. 90 2080 Brian Victor, Noah Jacobson New Orleans 7 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 2125 Catherine Connor Regency C 4 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 2151 Andrew Shafer, Paul Nasrat Grand Ballroom A 3 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 & 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. 45 2153 Dan Mezick Columbus GH 11 25 2009-08-13T08:21:34Z 2009-08-13T03:46:00Z The study of Group Relations is important to the development of Agile practice. Software development is performed by groups of individuals. When individuals become a members of a group, behavior changes. The group becomes focal & the individuals become background. The group behaves as a system and exhibits system-level behavior. Groups as a system exhibit very primitive emotional behaviors that can derail the group from its stated primary task. Group relations theory says that a group behaves as a system, and that the primary task of the group is...... 45 2154 Dan Mezick Grand Ballroom A 3 16 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z We've spent the past year writing a book about Agile Coaching and that's given us a great opportunity to reflect on what we do as agile coaches. In this talk, we'll present our top ten tips for agile coaches. We'll present this like those TV shows that do a countdown to the Number One tip and illustrate each with a personal coaching story. We also want to hear from people in the audience what their coaching tips are. 45 2224 Rachel Davies, Liz Sedley Regency B 5 12 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2232 Chris Shinkle Atlanta 2 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z How do you become agile with all the constraints surrounding you and your team? This tutorial introduces a new way to approach agile adoption efforts. We will go through important and key concepts related to agile adoption such as adopting values not practices, the difference between education and training, readiness assessments, and the process of organizational change. One of the tangible outcomes from this tutorial is a roadmap to agility that consists of five different levels, or steps, along with the different practices that can help an organization achieve each level of this roadmap. 180 2234 Greg Smith, Ahmed Sidky Toronto 2 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2236 Mads Troels Hansen, Hans Baggesen Crystal A 8 8 2009-08-13T08:28:16Z 2009-08-13T03:46:00Z 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. 180 2237 Robert Biddle Atlanta 1 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 180 2257 Naresh Jain, Michael Feathers Grand Ballroom F 7 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z **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’s learning process by pairing them with other practitioners and peers. 180 2258 Naresh Jain New Orleans 7 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z It is human nature to avoid loss. We make rational decisions to improve our situation and respond to circumstances. But are we always rational? Whether it be the tendency of people to hold stocks that have lost value or teams that continue a death march, this irrational fear of acknowledging a loss can cause people to keep investing in a poor undertaking. This discussion is a brief exploration of how our desire to avoid loss can cause us to irrationally make our situation worse in the hopes of somehow breaking even as well as some techniques to identify and avoid these situations. 45 2270 Brian Bozzuto Columbus GH 11 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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&D at Borland, will address these questions head-on, sharing his experiences in Borland’s Agile transformation. He’ll discuss the challenges that can emerge after the initial phases of transformation give way a new stage in the journey. 45 2272 Chuck Maples Atlanta 1 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Your mind offers two alternate—and generally unconscious—responses when things go wrong. One response solves problems with snap judgment, hasty advice, and evident policy. The alternate response expands the problem space for new awareness and new-found truth. You are completely equipped for both. The first is fast and solves anxiety about the problem. The second is slower, produces learning and growth, and addresses the real problem. In this session you’ll explore a life-long practice developed from 20 years of field studies for choosing the appropriate leadership response. 90 2287 Christopher Avery Regency A 9 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Jean Tabaka passionately believes in highly interactive, collaborative conference experiences for helping people new to Agile embrace its practices. This ½ day tutorial drives a quick-paced set of 8 exercises for attendees working in small groups. From unranked backlog items, to fully tasked out stories, each exercise builds on the work of the previous exercise. Through these series of activities, attendees learn to collaborate and create great user stories that turn into tasks, estimates, and commitments. The tutorial ends with a retrospective of how to apply these practices in real life. 180 2318 Jean Tabaka Grand Ballroom B 12 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In this session, we offer a synthesis of several bodies of thought that address processes, people, technology, change and leadership within the context of a large agile transition. While the competencies of agile development are well developed, the exploration and leveraging of other research on systemic change offers real insight to the complex organizational task of sustaining agile processes. We intend to fuse such research with our own experiences leading substantial agile transformations, to help senior leaders gain powerful new tools for leading their own agile transitions. 180 2319 Bud Phillips, Michael Hamman San Francisco 9 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Agile teams and organizations need to embrace a "See the Whole" mentality as they adopt and adapt Agile practices. Systems thinking is a great guide in how to evaluate this whole from an external perspective. In this tutorial, we will conduct a series of games to help participants understand fundamentals of systems thinking with regard to delayed feedback loops, external pressures, and more, and see how these change our perspective on effective Agile practices. Our goal is to help participants bring guidance back that can improve their cultures. 180 2320 Jean Tabaka, Bill Wake Atlanta 1 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Starting up an Agile team is one of the first things you might be asked to do when a company wants to "go Agile." 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 "go"? 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. 90 2341 Lyssa Adkins Toronto 2 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z According to research almost 85% of today’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 & teams? This presentation will show you a proven and powerful path to develop post-heroic leaders and teams. 90 2344 Gilles Brouillette Columbus GH 9 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 2349 Ken Collier Regency D 1 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 180 2352 Ken Collier Plaza Ballroom B 12 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z System Metaphor was and is an elusive practice of the original XP. It has largely been forgotten over time. Yet in the past few years, my colleagues and I have discovered the stunning power of a genuine System Metaphor on our own shipping product. This makes us wonder why System Metaphor ever went out of vogue. This session will explore why Metaphor matters. We'll examine how our own Music Metaphor reshaped our flagship product, even our company, and how the right metaphor can supply the driving beat that can turn your product into a hit. 90 2356 Joshua Kerievsky, Brian Foote Grand Ballroom F 7 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z What can programmers learn from the thought of Aristotle, Kant, and Mill? More than you might think. Find out what three of the greatest minds in history think about things like craft, art, virtue, and happiness, and how they would run a software project. We'll link philosophical ethics and ideas to the processes, tools, and methodologies of software development as we discuss a critical question: is successful development primarily a matter of finding the right rules, creating the right outcomes, or cultivating the right virtues? 45 2368 Jon Dahl Grand Ballroom A 3 24 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Tim and Tim discuss tools and techniques and observations for remotely pair-programming. Various remote desktop-sharing applications and services are discussed, dissed, and recommended along with pointers and practices for logistics. Learn the downside of distant partners. How do you have a flash architecture meeting? How do you collaborate with the team? When do you take breaks? Is it really just like being there, without the smells? 45 2399 Tim Gifford, Tim Ottinger Plaza Ballroom A 8 24 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z *“Tell me and I'll forget; show me and I may remember; involve me and I'll understand.”* – 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. 90 2402 Declan Whelan Atlanta 1 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z One quality of an effective agile team is its capacity for team learning. Research shows that learning behavior is positively correlated to team effectiveness. And though Agile processes provide powerful mechanisms for team learning, creating the right conditions in large bureaucratic organizations is not always straightforward. In this session, we will leverage research in organizational behavior, as well as the presenter’s years' experience coaching teams, to examine the organizational conditions which managers need to understand if they are to empower team learning behavior. 90 2416 Michael Hamman Regency A 9 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2417 Erik LeBel, Isabelle Therrien Plaza Ballroom A 8 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2419 Jesse Fewell Columbus GH 11 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 ""the most well-known and controversial"" of the new agile processes. This experience report will tell of a ""do-it-yourself"" Agile success story, with changes, challenges and lessons learned along the way. 45 2424 Brian Spears Atlanta 2 4 2009-08-13T08:29:01Z 2009-08-13T03:46:00Z When Marriott began to build its brand management intranet, the tech vendor ran into several problems that jeapardized the whole program. The introduction of Agile began a long recovery process: When should you be be covert/overt with Agile practices? How do you convince stakeholders a daily concall is more efficient than a weekly concall? Why would you pay for the tech vendor's Agile training? How do you structure Firm Fixed pricing to be Agile? This is the story of how applying Agile techniques, first covertly, then out in the open, slowly steered the ship on course. 45 2433 Jesse Fewell Crystal C 4 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 2440 Bill Wake, Jean Tabaka Grand Ballroom A 3 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 2444 Tobias Mayer, Lyssa Adkins Crystal A 5 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Changing the way individuals and teams work is one thing. Changing organizational culture is quite another, especially when so many of us (yes, even us at this conference) have little idea that the assumptions we make, the language we use, the structures we are bound by are the direct antithesis of Agile. Our thinking is locked by the patterns of years and needs to be unleashed in order to make inroads towards cultural change. Using a simple yet effective collaboration game from the Improv tradition this session will challenge our assumptions and open up new neural pathways. It is a beginning. 90 2450 Alan Cyment, Tobias Mayer Atlanta 1 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z It was back in '97 that these presenters first opined that: while much attention had been focused on high-level software architectural patterns, what is, in effect, the de-facto standard software architecture had seldom been discussed: the Big Ball of Mud. Somewhat to our astonishment, since then, no one has ever undertaken to dispute this premise. A Ball of Mud is, of course, a haphazardly structured, sprawling, sloppy, duct-tape and bailing wire, spaghetti code jungle. Is Agility's utilitarian focus on process rather than design its secret weapon, or its Achilles heel? 90 2470 Brian Foote, Joseph Yoder Grand Ballroom A 3 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 2473 Rod Claar, Douglas Shimp Regency C 2 27 2009-08-13T08:20:45Z 2009-08-13T03:46:00Z Peter Coad's Color Modeling method is a simple, effective technique for building robust, elegant object models. One of the best ways to learn the Color Modeling approach is through an interactive demonstration. In this session, Daniel Vacanti and David Anderson will solicit examples from the audience and--with no preparation and using the Color Modeling approach--build a real, working model for each selected problem domain in the short time given. Both David and Daniel have used this demonstration technique with great success at previous conferences, tutorials, and commercial engagements. 45 2506 David Anderson, Daniel Vacanti Columbus IJ 6 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Acceptance Tests elaborate a user story & are essentially behaviour specifications, expressing examples of how the application will actually be used. These should represent customer-intent in terms the customer understands. This session shows developers and testers how to transcribe their understanding of customer intent in a way that makes sense to customers. Using the popular BDD Given/When/Then approach to acceptance tests, participants will learn how to leverage the popular Fit framework to replicate that approach. Alternatives to using Fit, including using code, will also be explored. 90 2522 Antony Marcano, Andy Palmer Grand Ballroom D North 14 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 2535 Amanda Willoughby Columbus KL 16 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 2562 Tom Hume, Johanna Hunt Columbus KL 16 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Agile project teams in any large corporation are put together by drawing resources from various organisational silos where they report to line management. What’s the role of this line management in relation to the Agile project teams? **Who is ultimately responsible for delivery?** This talk is based on the two year Agile journey in a large financial services organization in Australia and will outline the challenges, pitfalls and experiences of positioning line management to add value to Agile teams. *What leadership role do they play and are they the bane or boon of Agile teams.* 45 2575 Philip Abernathy San Francisco 9 21 2009-08-13T08:23:06Z 2009-08-13T03:46:00Z 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. 90 2591 Eric Smith, Eric Meyer Grand Ballroom F 7 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2592 David Rico Regency C 2 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z An Intuit process “Agile Done Right” (ADR) was created to ensure agile is used properly to maximize business results & minimize process problems. It requires an agile coach like those used in Intuit’s successful SEI’s Team Software Process (TSP). Coaches ensure the process is “done right” & help fix any problems. Internal coach training was created to develop project-embedded coaches & to raise the overall level of agile maturity. We look at that training program including the agile syllabus, brief ADR overview, coach’s “dirty dozen” meetings, learning methods, etc. 45 2614 Alan Padula Crystal A 5 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z So much of moving traditional test teams towards agile methods & testing is focused towards the individual tester and testing techniques. As often is the case in agility--directors, managers, team leaders and test-centric project managers are sort of marginalized. But not in this session! Here we want to focus on agile testing from the perspective of the Test Leader. We'll pair off into groups and examine some of the greatest challenges when it comes to leading a testing team from traditional towards agile testing and emerge real-world strategies for surviving and thriving in agile testing. 90 2621 Bob Galen Grand Ballroom D North 14 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z **Summary for Event Guide** A high-performing agile team is tight knit. They have worked hard to become a cohesive unit and have developed a bond. This chemistry can be thrown off balance when someone is added to the team in the middle of a project. It does not matter how flexible, capable, or agile savvy the new team member is. If they have not been involved in the care and nurturing of the team’s culture and is not invested in the same way that the other team members are. When the new team member is not flexible, capable or agile savvy, the effect can be devastating. 90 2622 Mitch Lacey Regency D 1 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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’s leadership when balancing between Agile and traditional methodologies used on Government programs. 45 2669 Min-Gu Lee San Francisco 9 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Because the FBI never stops evolving, High Performance Technologies, Inc (HPTi) found themselves struggling to keep up with the changes and maintain their CMMI III certification. Developers were complaining, clients were getting anxious, releases were slipping; but what was the problem? Was it CMMI? Was it the environment? Was it HPTi? Through a disciplined approach to agile development, we found the answers to our questions above. When you’re dealing with a client who is historically challenged with a continuously changing environment, you better be on your toes. 45 2702 Justin Babuscio Atlanta 1 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2712 Lily Cho Columbus KL 16 32 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2738 Clement "James" Goebel Regency D 1 32 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z As Development VP, Rich Sheridan transformed his organization by adopting radical co-location and XP practices. Rich will share the history of this transformation including the tactics he used in selling this idea to his peers, his CEO, the Directors, and ultimately his team members. Rich now runs a software design and development company that was built from the ground up with an Agile culture and Agile processes. As the CEO of this company, Rich routinely has to sell customer executives on why they will realize business value from practices such as unit testing and paired-programming. 90 2740 Richard Sheridan, Clement "James" Goebel Toronto 2 11 2009-08-13T08:27:52Z 2009-08-13T03:46:00Z Developers on an Agile project depend on fast, accurate user feedback to guarantee that you are solving the user’s problem. But often Agile projects have to operate without real, current customers on the team and need to build up the design and research skills to get good user feedback. This session is for anyone who has the job of getting user feedback. We'll teach best-practice techniques for working with users in the situations that matter to an Agile team: understanding customer needs, getting feedback on design concepts and testing baselevels, and we'll practice key skills. 90 2751 Hugh Beyer Columbus KL 16 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z You create iterations from a backlog of user stories managed via a taskboard with a simple "workflow" from "todo" to "done." You use Continuous Integration. But in your source control system you've just got files and branches. You could create a branch for every story, but that's a lot of branches to manage! How can you ask the source control system which versions/files correspond to the stories that are done in order to build the "done" version and do exploratory testing? This session will show how to manage changes using stories and how to use branches to represent your workflow. 45 2757 Damon Poole Grand Ballroom C North 15 15 2009-08-13T08:26:59Z 2009-08-13T03:46:00Z Aren't code, backlog-items, tests, designs & documents all just different forms of system knowledge at different levels of detail? Why can't the same tools help refactor, browse, search, and provide build/test automation for _non-code_ forms of knowledge *without* requiring a separate tool/repository for each format? This talk is intended as a challenge to tool vendors/developers to see how this simple treatment of all non-code items as part of a single, unified project knowledge-base can be at once both immensely powerful, and imminently practical, without requiring too much added complexity. 45 2762 Brad Appleton, Peter Alfvin Grand Ballroom E 15 16 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Over the life of a product, Product Owners maintain an ever-evolving Product Backlog. As features rise in rank, the PO breaks them down into stories, eventually sized small so the team can deliver increments of valuable functionality in an iteration. In this tutorial, we will explore examples of how to evolve a product backlog from vision to iteration acceptance. Participants will practice breaking stories down, with an emphasis on understanding the considerations that guide that process. We will provide several examples from different types of projects/products. 45 2763 Ronica Roth, Mark Kilby Crystal C 4 18 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In 2007 a large consumer electronics retailer faced significant business challenges. In pursuit of new modes of strategic flexibility and fast execution, the e-commerce division transformed its culture around Agile principles and the user experience team adapted its practices to the new paradigm. How would increased velocity affect the quality of the functionality produced? How would time-intensive activities like usability research be affected? This paper presents a case study describing successes and failures while integrating continuous research into Agile projects. 45 2765 Tom Illmensee, Alyson Muff Columbus KL 16 16 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In “The Fifth Discipline”, 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’ll use a specific dialogue format called World Café to explore the many factors that influence dialogue quality, and how to accelerate agile team learning through the use of dialogue. 90 2794 Eric Babinet Regency A 9 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z In our business and personal lives, many of us know leaders who foster environments with incredible creativity, innovation, and ideas—while other leaders try but fail. So, how do top leaders get it right? This session explores ways that leaders create cultures of trust that fosters the free flow of ideas. While we can’t make people trust each other, a culture of trust gives empowerment and provides a safe place to explore and discover new and innovative solutions and new ways of implementing and reaching results. It also encourages healthy risk taking to fail early and correct faster. 90 2800 Pollyanna Pixton Regency D 1 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 “The Simplest Thing That Could Possibly Work.” 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. 90 2804 Lasse Koskela Columbus KL 16 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Leaders can stifle progress when they unnecessarily interfere with team processes. However, as a leader, you don’t want your project to go over the cliff and fail miserably or deliver the wrong results either. There are times when leaders should stand back and let the team work things out for themselves—and other times when leaders should step up and really lead. How do you know which is which? And what do you do to not stifle the team’s creativity, ownership, integrity, and problem solving ability? Come away with tools to both motivate and guide teams and organizations effectively. 90 2817 Pollyanna Pixton Regency A 9 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Testing can be a complex and thankless task. The technologies change so fast that your tools don't work as they should. Your tests become brittle and are hard to relate to customer requirements. This talk looks at the latest techniques and tools for easing some of these burdens. Topics include behavior driven development (BDD), domain specific testing languages (DSLs), scripting languages (Groovy) and a range of web, SOAP, database, Ajax and performance testing libraries (including EasyB, JUnit 4, WebTest, HtmlUnit, Tellarium, DbUnit, SoapUI, JMeter, AllPairs, model driven and others). 180 2826 Paul King, Craig Smith Grand Ballroom E 15 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z One of the toughest problems facing agile UX designers is keeping the big picture in mind while designing incrementally. This talk builds on prior work at Alias (now Autodesk) that described [successful agile adaptations](http://tiny.cc/agileUCD) of usability testing, contextual inquiry and iterative prototyping. I'll present a framework we used to create and implement multi-sprint designs for a complex product without violating the agile taboo against *big design*. 90 2837 Desiree Sy Columbus KL 16 11 2009-08-13T08:27:40Z 2009-08-13T03:46:00Z As an organization becomes more agile, people often worry about the future of their jobs. If detailed requirements documents aren't needed anymore, what happens to a business analyst? If people aren't constantly shuffling from one project to another, what does a program manager do? If testers are part of scrum teams, how can a QA lead increase quality? In this workshop, participants will explore how different roles change during an agile transition, envision new roles for everyone, and discuss strategies for change that help address the fears that often prevent successful agile adoption. 180 2839 Alex Pukinskis, Mark Kilby Regency C 2 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 2840 Craig Smith, Paul King Grand Ballroom C North 15 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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’ve skimmed some of the books, but don’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’re about to lose control of your baby. You’re about to learn that you’ve created a monster. 45 2844 Michael Marchi Atlanta 1 6 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z We are going to traverse the long and winding history of Agile at Yahoo! – beginning with the period just prior to the introduction of Agile over 5 years ago, to its current (and unfinished) state – all from the viewpoint of the Agilista in the trenches. Whether the adoption is driven from the top down or bottom up, progress hasn't always been in a straight path. We hope that the experiences we share will provide valuable insight for others in their roll-out of Agile in the enterprise, and how the DNA of Agile can survive and even thrive in both supportive and challenging circumstances. 45 2859 Mun-Wai Chung, Brian Drummond Crystal B 10 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2869 Arin Sime Columbus IJ 6 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 & Deliverables - All contribute to the iteration planning meeting A handout will be provided for future reference. 45 2871 Julie Chickering, Ken Clyne Grand Ballroom B 12 32 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2884 Kevin Fisher, arlen bankston Crystal C 4 26 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2898 Harry Koehnemann Plaza Ballroom A 8 28 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2902 Anda Abramovici Regency C 2 30 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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’ll leave with a buffet of useful UX techniques to add to or adapt your agile process. 45 2911 Jeff Patton Columbus KL 16 31 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 180 2921 gabrielle benefield, Tom Poppendieck Crystal B 10 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Leading an Agile adoption? This tutorial will give you guidance, fresh perspectives, and a real deliverable. Distilling 7 years' experience leading large-scale Agile implementations, we will examine patterns, anti-patterns, techniques and case histories from 7 different perspectives (or layers): Individual, Team, Management, Program, Business, Strategic, and Organizational. Using a template, your class team of 5 will help you create your adoption plan covering selection, sequence, sponsorship, culture, org change, job change, role of customers & management, training, methodology and metrics. 180 2957 Michael Spayd Regency C 2 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 2961 Micah Martin New Orleans 7 26 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z How well are we served by our current metrics? Do metrics such as developer and tester productivity, ROI, and on-time / on-budget help us improve results? Or, do such metrics drive us towards negative behaviors? In this workshop, we describe the foundation for meaningful metrics. Workshop participants, via a series of exercises, translate this foundation into metrics that they can immediately use. This workshop results from the response I received during my Agile 2008 presentation on the CIO and agile teams. There was a great deal of interest on the topic of aligned, meaningful metrics. 90 2989 Niel Nickolaisen, Chris Matts Crystal B 10 13 2009-08-13T08:27:10Z 2009-08-13T03:46:00Z Project managers who are new to agile methods often have questions about how to track progress on agile projects. Some of the traditional measures don't line up very naturally with agile thinking and agile practices, especially measures that are concerned with tracking team members' time and comparing estimated and actual task durations. One of the main issues is understanding how to project realistic delivery dates with methods that don't lend themselves to the Gantt approach. 90 3000 Dave Nicolette San Francisco 9 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z W. Edwards Deming identified performance appraisal as one of the Seven Deadly Diseases of Management. But annual appraisals are currently a fact of life in most organizations, in spite of their negative effects. Many companies are reluctant to give them up, because they don't see what to do instead of the annual review. I'll walk through the assumptions behind performance evaluation and review, and share some of the recent research on the efficacy of annual reviews. Then I'll offer alternatives that actually help people improve and build stronger relationships. 45 3001 Esther Derby Crystal B 10 18 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Today’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. 45 3027 Darryl Bowler Columbus KL 15 6 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 3030 Andrew Rendell Toronto 2 6 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z When charting new territory–-enterprise-scale Agile–-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’s Agile transformation. He’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’s Agile transformation. 45 3032 David Wilby Crystal C 4 6 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 3043 Paul Ingalls, Troy Frever Atlanta 1 29 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 3047 Lane Halley, Luke Hohmann Crystal C 4 27 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 “oh well, they’re all adults, they’ll figure it out” 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. 180 3056 Joseph Pelrine Regency B 5 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 3060 Andre Frank San Francisco 9 30 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 3070 Wojciech Seliga, Slawomir Ginter Grand Ballroom E 15 7 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z How do you do sprint planning meetings when you have, for example, 60 people and 8 teams working on the same product? One neat way is to get them all into the same room and do them together. This is a great way to stimulate collaboration and resolve dependencies - but there are some important practical aspects to take into consideration. Having done this with several different companies over the past few years I'd like to share some experiences and lessons learned. I will focus on the practical aspects of getting this to work, with photographs and examples from real cases. 45 3075 Henrik Kniberg Regency A 9 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 3080 Michael Bolton Grand Ballroom D North 14 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Leading an agile development team; what is the role, what’s important, what to do, and how to lead. This is based on my experience in leading a large (600+ people) application development organization that has been practicing Agile since 2001. Over the past eight years I’ve observed, coached, and developed Agile leaders. In my talk I’ll cover the attributes of the successful Agile leader. I will use real life examples that illustrate and validate the attributes that can help or hinder the process of leading an Agile team. Leadership versus management will also be discussed. 45 3085 David Endicott San Francisco 9 23 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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.) 180 3088 Marina Chiovetti, Julian Boot Crystal C 4 29 2009-08-13T08:18:16Z 2009-08-13T03:46:00Z Agile development means self-management, collaboration, and working towards shared goals. Agile practices support much of this, but we can still learn more, both to better understand current practices and to develop new ones. This session is an introduction to cultural-historical activity theory, a psychological framework for understand collaborative behaviour. The framework has shown the role of tools in cognition and collaboration, and understanding structural tension between different activity systems: it can also be used to understand and improve agile software development. 90 3098 Robert Biddle Columbus GH 11 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 3110 Bruce Winegarden, David Ullman San Francisco 9 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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! 45 3122 Anda Abramovici, Tim Brown Toronto 2 32 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 45 3123 Ron Morsicato Atlanta 1 8 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z As agile coaches, we all face impediments when it comes to making agile transformations happen in an organization. Dealing with corporate bureaucracy is most times the hardest part of the transition. So, what about the federal government and all that red tape? Learn how two coaches have made it happen, leading and coaching an enterprise agile adoption (principally Scrum and FDD) at two agencies within the federal government space. Think you’ve dealt with bureaucracy? Come hear what it’s like to deal with the ultimate in corporate bureaucracy! 45 3132 Judy Wankerl, Brandon Raines Regency B 5 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This tutorial focuses on the detailed specifics that will make distributed agile meetings effective. We will demonstrate several key agile meetings, run in a distributed fashion, so teams can immediately improve their projects. To do so, I will highlight specific tools available in the market place to facilitate each of these different kinds of discussions (retrospectives, planning meetings, stand ups). I'll demonstrate the processes to enable more effective communication between remote locations and describe the key roles required on a project to encourage the best exchange of information. 90 3165 Mark Rickmeier Crystal A 8 15 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This is the story of how the Launchpad (https://launchpad.net) development team switched to a continuous integration system to increase several flows in their development process: * flow of changes on trunk; * flow of changes requiring database schema upgrade; * flow of deployed changes to end users. To switch to a buildbot (http://buildbot.net) based system meant violating a very old company taboo: risking a trunk that doesn't pass its test suite. The risk of a broken trunk was offset by allowing each developer to run the full test suite in the Amazon EC2 cloud. 45 3166 Francis Lacoste Grand Ballroom E 15 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z JavaScript has earned a special, dark place in most programmer's hearts as it is a necessary evil for making the web experience dynamic. You are test-driving your JavaScript, aren't you? If not, why not? If the reason is that you don't know how, or haven't taken the time to learn the various testing frameworks, then this session is for you. We will briefly explore the various testing frameworks, build our own lightweight framework, and then test-drive a small bit of functionality using it. 90 3183 James Suchy New Orleans 7 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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. 90 3201 Michael Spayd Crystal A 5 25 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This is a trick question, right? In agile, everyone works on the same items together, at the same time. Yet, the reality is we’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. 90 3205 Abby Fichtner, Nate Oster Grand Ballroom D North 14 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 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 90 3207 Paul Hammant, Mauro Talevi Grand Ballroom E 15 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Not long ago the notion of a tool that hides more of the system than it shows sounded crazy. To some it still does. But hundreds of thousands of Mylyn users have made next big evolution of the IDE clear. Stories and tasks are more central than source code, focus is more important than features, and integration with the agile workflow is the biggest productivity boost since code completion. This talk will demonstrate the concepts of the task-focused interface and look ahead at how we are redefining the "I" of the IDE by personalizing the user experience around the agile process. 90 3210 Mik Kersten Grand Ballroom C North 15 17 2009-08-13T08:26:01Z 2009-08-13T03:46:00Z 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. 45 3223 Rajesh Sharma, Brian Wherry Columbus KL 16 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Persona put the user back into your user stories. While we understand that our users are important we may lack language for talking about them. If you already know about persona you may find your approach for performing research and representing user data as a user persona to be time consuming and, what’s more, the persona you create simply aren’t being used. In this short tutorial you’ll learn to create simple _relevant_ persona for your agile project, how to communicate them to the team, and how to use them generate valuable feature ideas, and design imperatives for your product. 90 3229 Jeff Patton Columbus KL 16 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z With the popularity of Scrum, ScrumMaster has become a de facto role on many agile projects. In this thought-provoking session, we'll explore the ScrumMaster role and its key challenges. We'll discuss why teams end up with dysfunctional ScrumMasters, and how that hurts agile projects. We'll explore common ScrumMaster anti-patterns, and why they occur. We'll challenge the ScrumMaster role, compare it to other models, and address if agile teams really need a ScrumMaster. This promises to be a lively and interactive session that may change your views on how to structure a Scrum team. 45 3231 Paul Hodgetts San Francisco 9 14 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z This hands-on session will cover a number of low cost, yet powerful research methods, like the ""burrito lunch"" 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. 90 5034 Russ Unger, Todd Zaki Warfel Acapulco 16 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 90 5107 Philippe Kruchten Plaza Ballroom A 13 1 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 90 5108 Tore Dybå Plaza Ballroom A 13 3 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 90 5110 Philippe Kruchten Plaza Ballroom A 13 5 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 90 5111 Yael Dubinsky, Philippe Kruchten Plaza Ballroom A 13 7 2009-08-13T08:28:23Z 2009-08-13T03:46:00Z The increasing use of agile methods to develop UI-intensive systems has led to a need to find ways of integrating usability into agile teams—reconciling the convergence and divergent points between the two areas. Agile usability researchers at Virginia Tech have partnered with Meridium to develop and implement an integrated approach known as eXtreme Scenario-based Design (XSBD). Based on an analysis of core values and principles of both areas, and work from other agile usability researchers we identified four requirements that need to be met for an integrated approach to work effectively. 45 5112 Yael Dubinsky Plaza Ballroom A 13 11 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z User Experience (UX) practitioners and agile practitioners need to understand how user-centred design (UCD) and its techniques can be applied in an agile context. We studied the role of UX practitioners on agile projects, as perceived by UX practitioners themselves. Interviewing 10 UX practitioners in a variety of settings, we identified two main themes that they perceive to be highly influential in the success of integrating UCD and agile approaches: UX practitioners’ understanding of their job role, and the need to establish, protect and communicate an overall team vision. 45 5113 Yael Dubinsky Plaza Ballroom A 13 12 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 90 5120 Philippe Kruchten Plaza Ballroom A 13 17 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 90 5121 Orit Hazzan Plaza Ballroom A 13 21 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z 90 5122 Laurie Williams Plaza Ballroom A 13 19 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Mitigating Team Politics in Agile Usability: A Mapping Approach Chair: Yael Dubinsky Featured Participants: Jeremy T Barksdale, Eric D Ragan, D. Scott McCrickard Supporting Program Comprehension in Agile with Links to User Stories Chair: Yael Dubinsky Featured Participants: Sukanya Ratanotayanon, Susan Sim, Rosalva Gallardo-Valencia XP Customer Practices: A Grounded Theory Chair: Tore Dybå Featured Participants: Angela Martin, Robert Biddle, James Noble 90 5142 Yael Dubinsky Plaza Ballroom A 13 13 2009-08-13T03:46:00Z 2009-08-13T03:46:00Z Extreme Product Line Engineering: Managing Variability & Traceability via Executable Specifications Chair: Tore Dybå Featured Participants: Yaser Ghanam, Frank Maurer Building General Knowledge in Agile Software Organizations: Experiences with job rotation in customer support Chair: Tore Dybå Featured Participants: Tor E. Faegri The XP Customer Team: A Grounded Theory Chair: Tore Dybå Featured Participants: Angela Martin, Robert Biddle, James Noble 90 5143 Tore Dybå Plaza Ballroom A 13 15 2009-08-13T03:46:00Z