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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 **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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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