Where available, slides from each speaker’s presentation may be accessed by clicking on the presentation icons below.

The keynote speech given by Jean Tabaka may be viewed here.

Registration, Networking, Breakfast
Sponsor showcase
Welcome and keynote address by Jean Tabaka
Room Forum 1 Expo Forum 3 Forum 2 Main
Map Your Agile Transition Strategy using Kotter’s 8-step Model and the Theory of Constraints
Brad Swanson
Jenkins – Continuous Integration after Hudson, CruiseControl, and home-built
Mark Waite
Viewing a Lean Software Engineering System through a CMMi Lens
Richard Hensley & Michael Robbilard
Productive Joy
Zachary Spencer(No slides)
Open Space session #1
Room Forum 1 Expo Forum 2 Forum 3 Main
User Story Best & Worst Practices
Charles Bradley
Agile the Pivotal Way: Things that Work for Us
Mike Gehard
Customer Development: Learn, then Burn
Kevin Taylor
A Day in the Agile Life at a Financial Services Company
Beth Bleimehl, Paul Quarles, Doug Huffman, Mike Banta
Open Space session #2
Lunch and Sponsor Showcase
Room Forum 1 Expo Forum 2 Forum 3 Main
Reverting to Form – How to Make Sure That Agile “Sticks”
Howard Deiner
Test Driving Front-end Code
Chris Powers
Agile Hardware—What Hardware Developers Are Learning from the Agile Movement
John S. Farnbach
Using Agile Principles to Solve Tough Problems in Your Business
Rachel Weston & Zach Nies
Open Space session #3
Sponsor Showcase
Room Forum 1 Expo Forum 3 Forum 2 Main
Overcoming the 5 Dysfunctions of Agile Teams
Bob Hartman
Strategic Design using DDD
Paul Rayner

Rapid Release Planning – A New & Better Way to Estimate & Validate Stories
V. Lee Henson
Agile Leadership for the Learning Organization Jan Beaver Open Space session #4
Sponsor Showcase
Closing Remarks
Door Prizes, Raffle
Networking & Sponsor Engagement
Adopting & transitioning to agile
Technical practices and tools
Agile product & project practices
Executive and enterprise agility
Open space

Keynote Address

Elevating the Agile Community of Thinkers – Jean Tabaka, Agile Fellow, Rally Software

“I am a member of a community of thinkers.” This is the first line of a statement Liz Keogh, Eric Willeke and I crafted on December 9, 2009 in Boulder. It came about as a result of a day of reflection, introspection, challenge, and “futurespection” about our lives as software professionals. We here today are laying the rockbed of our profession’s contribution to the 21st century. Join me in a journey of how we can and must act as a community of thinkers in creating our future. I would like to explore with you how we are a community of truly indispensable creators with individual strengths and immeasurable collective wisdom. I’ll share some direct professional experiences of my own about this work of community and thinking. I will share the power of collective visioning and I will contrast the destructive nature of a confrontational or escalation approach to thought leadership. I’ll also warn you about the slow death of complacency. As Nelson Mandela said in his Presidential Inaugural address: “You do not serve the world by being small.” I am a member of a community of thinkers. So are you. Together, let us elevate our Agile community of thinkers.

Jean Tabaka, Agile Fellow with Rally Software, is continuing on her 30 year path of learning about software development principles, processes, and practices for people.  She seeks a humane approach to bringing high value to our communities of creators and consumers. This has led her to move into Kanban and Lean approaches that reach beyond traditional Agile frameworks. Jean holds a Masters in Computer Science from Johns Hopkins University. She is the author of “Collaboration Explained” and is a speaker worldwide on Agile, organizational change, team dynamics, systems thinking, Lean thinking, and other associated topics. Jean blogs at and can be followed on twitter as @jeantabaka. When not traveling, she’d invite you over to her home in Boulder for some wine and some music while gazing across her backyard over a Flat Iron Mountains sunset. Meanwhile, you can find her at .

Adopting & Transitioning to Agile Track

Map Your Agile Transition Strategy using Kotter’s 8-step Model and the Theory of Constraints

Brad Swanson

Brad Swanson

In this interactive session, participants will develop a strategy for creating and sustaining a transition to agile methods based on John Kotter’s Eight Steps for implementing organizational change and the Intermediate Objectives Map (a.k.a. Strategy Map) from Theory of Constraints. We’ll introduce John Kotter’s eight-step framework from Leading Change, and then use Eliyahu Goldratt’s IO Map as a systematic tool to flesh out a comprehensive strategy for implementing and sustaining the transition to agile. The presenter will share concrete elements from successful large-scale agile transitions that participants can use to develop their own strategy map. Participants will leave the session with a concrete strategy they can use immediately within their own organization to achieve a sustainable change!

About Brad Swanson

Brad Swanson is Founder and Principal Consultant of Propero Solutions LLC. Brad started programming at age ten on the Apple IIe, and is now a Certified Scrum Coach (CSC), Certified Scrum Practitioner (CSP), and Certified Scrum Master (CSM) with 16 years of experience in project and program leadership, product management, and software development in both start-ups and large companies. Brad has led the adoption and implementation of agile and Scrum methodology at many organizations, leading successful agile projects with teams in the US, Europe, and Asia. He has deep experience with agile software development, starting with eXtreme Programming (XP) in 1999, and also Scrum, Lean and Kanban methods. He is active in the Agile and Scrum communities as a Director of the Agile Denver user group, and as a speaker at Agile user groups and international conferences.

Reverting to Form – How to Make Sure That Agile “Sticks”

Howard Deiner

Howard Deiner

Whether the adoption of Agile takes place in a grass-roots “bottom-up” approach or a mandated “top-down” manner, it takes a change in culture, and a willingness to “give it a chance” that is the biggest determinate in making Agile stick in an organization. In particular, it is the acceptance of using (and perhaps measuring) business value that makes an organization realize that Agile is their friend.

About Howard Deiner

Howard Deiner is an independent software consultant who specializes in Agile process and practices. He has a varied background spanning 36 years in the industry, with extensive domain knowledge in commercial software, aerospace, and financial services. He has played many of the roles in the development arena, such as developer, analyst, team lead, architect, and project manager. When not mentoring and developing organizations, he has also dabbled in the executive office, and wears the battle scars of the DotCom revolution proudly. He has applied the principles of Agile and XP Development in teams both large and small, for in-house as well as commercial environments, both in an organic setting, as well as the ordained setting. Howard has educated dozens of teams, and made Agile principles come to life in many settings. Howard has degrees in Computer Science and Electrical Engineering from SUNY at Stonybrook, as well as a Juris Doctor from Thomas M Cooley School of Law. Howard is a long standing member of the ACM and IEEE. He resides in Northern New Jersey with his wife, and in their spare time, they breed Maine Coon cats as a counterpoint to the world of technology.

Overcoming the 5 Dysfunctions of Agile Teams

Bob Hartman

Bob Hartman

Is your agile team not performing up to the potential you see in them?  If so, they may be suffering from internal dysfunctions that can contribute to less than desirable results. When core dysfunctions are left to fester, the end result will often be project failure and the cause will be chalked up to “that’s just the way agile sometimes works.” Based on his coaching work with hundreds of agile teams, Bob Hartman presents an agile team dysfunction model. Bob shows how he determines which of the five core dysfunctions (“leave me in my silo”, “when we communicate it is in email”, “others make commitments for us”, “don’t blame me because I didn’t do it” and “hero worshipers) the team may suffer from.  He will also demonstrate how he communicates them and most importantly, how he helps teams learn to move past their issues. Learn how teams can achieve greatness once they fully understand their weaknesses and how certain common agile practices can help teams address their weaknesses.

About Bob Hartman

Bob Hartman’s logic-based approach to development and quality was honed early in his now more than thirty-year software development career. He has acquired wide-ranging industry knowledge by working in many roles including software developer, tester, product manager, project manager, development manager, and executive. During the past ten years, Bob has grown from being an early adopter of agile to his current status as a Certified Scrum Coach (CSC) and Certified Scrum Trainer (CST). He remembers the pain of long waterfall development cycles and understands the human and business interactions necessary to achieve success regardless of development methodology. Bob’s holistic view of development can help any team achieve success.

Technical Practices & Tools Track

Jenkins – Continuous Integration after Hudson, CruiseControl, and Home-Built

Hudson is an easy to install, easy to use open source continuous integration server from Kohsuke Kawaguchi of CloudBees (formerly of Sun). The Hudson project has since been forked by Kohsuke to become the Jenkins project. This session will demonstrate installing, configuring, and using Jenkins for continuous integration. We switched about two years ago, after using a home built server, and after using CruiseControl. This presentation will discuss the power of continuous integration as a concept, then will show a live demonstration of Jenkins running with a master on one computer and slaves on other computers. Key concepts will be illustrated including ease of installation and configuration, richness of existing plugins, checkout from source code, building, testing, and viewing results.

About Mark Waite

Mark Waite is a director of software development at Parametric Technology Corporation. He lead a development team of programmers and testers through the transition from waterfall to agile beginning in 2003 as part of a small company, CoCreate Software. CoCreate was purchased by a much larger company, Parametric Technology Corporation in 2007. Mark has integrated the development team into the larger scrum team at PTC, and has managed team members in other locations.

Agile the Pivotal Way: Things that Work for Us

If you ask 5 people what Agile development is, you will get 5 different answers. In this talk, Mike Gehard from Pivotal Labs ( will share some insight into how Pivotal has tailored XP style Agile development and their corporate culture over the past 20 years to successfully serve their clients and their employees.

Some questions that will be discussed:
Why does Pivotal serve breakfast every morning? How does Pivotal do meaningful standups for 50 people every morning? Why does Pivotal believe so much in pairing that they do it 8 hours a day? How deeply rooted is test driven development is Pivotal and what benefits do they see from that? How does Pivotal find and hire good developers in a tight Ruby/Rails market? How does Pivotal interact with their clients to provide high quality software in a short time frame? Beware, some of the ideas expressed in this talk might make you a little uncomfortable.

About Mike Gehard

Mike Gehard is a software engineer at Pivotal Labs in Boulder, Colorado. He spends his days test driving the writing of code, pair programming style. He spends his evenings and weekends enjoying life in Boulder, CO. He believes strongly in the philosophies of Agile development and works to integrate them into both his professional world as well as his personal world.

Test Driving Front-end Code

Chris Powers

Chris Powers

Test driven development (TDD) has proven to be a cornerstone of Agile software development. From Java to Ruby, C to Python, development communities are swiftly accepting TDD as the de facto standard of quality software development. The Javascript community, on the other hand, has yet to embrace TDD. In this talk I will discuss the benefits that Javascripters can gain from TDD and examine the hurdles that have  prevented its early adoption. I will present the Jasmine testing framework as a solution and use it to build a live demo application using TDD.

About Chris Powers

Chris Powers has been developing Web applications for the last six years, now specializing in Ruby and Javascript development. Currently he is enjoying working as a software consultant with Obtiva, where he partners with clients to build and improve Web applications. Chris strongly believes in the power technology has to bring people together and enjoys developing platforms that empower the user. Living in the northern Chicago suburbs with his wife, dog and cats, Chris stays active in the Web development community both online and off. In his free time he enjoys playing the drum kit and writing music.

Strategic Design using DDD

Paul Rayner

Paul Rayner

Not every part of a software system will be well-designed. How do you know where to put the time and effort to refine the design, or refactor existing code? Learn how strategic Domain-Driven Design (DDD) patterns can show you how to know which parts of your system matter most to your business and how to focus your team’s design efforts most effectively.

Context mapping and Core Domain are key concepts in DDD, providing valuable techniques and insights into where to focus your design attention, yet most developers have never heard of them. This session will introduce the tools of strategic DDD and show you how they can shine a light on your design challenges.

About Paul Rayner

Paul Rayner is a Denver-based independent consultant with more than twenty years of software development and consulting experience. His company, Virtual Genius LLC, provides organizations with the tools and practices needed to succeed at agile software development, from portfolio management through to customer delivery. He specializes in helping organizations struggling with their transition to agile software development, or in need of external agile custom development and architectural expertise.

Paul is an active member of the Colorado developer and agile communities, a member of the Agile Denver leadership, one of handful of certified Domain-Driven Design instructors, a member of the Agile Cooperative, a regular speaker at user groups and conferences. He writes with an Australian accent about software development at .

Agile Project & Product Practices Track

Viewing a Lean Software Engineering System through a CMMi Lens

Two years ago the ADM Engineering organization within McKesson Corp. proposed and succeeded in using kanban as a tool to express our software development process. The McKesson office of the CTO is now studying the ADM engineering system with the hypothesis that the system, processes, and practices can scale to other technology development businesses within McKesson. As part of the scaling evaluation, the CMMi model, a well known model to McKesson, is being used to evaluate the practices of the ADM engineering group. Our story of evaluating the engineering system in the context of CMMi and expressing our processes and practices using the model is told in this presentation. The most promising part of this evaluation is that aligning the ADM engineering system with the CMMi model was a low effort initiative. The rewards for the CMMi initiative are credibility within the McKesson engineering management, experience for the McKesson CMMi process maturity team with model interpretation in a lean software shop, and validation of value of systems-thinking in process assessment and improvement initiatives.

About Richard Hensley and Michael Robbilard

Richard Hensley is a 25 year veteran of the healthcare information technology industry. Richard has built systems to support the healthcare industry including retail and hospital pharmacies, prescription insurance claims, hospital based and ambulatory clinical laboratories, insurance utilization and authorization management, hospital patient accounting, and hospital clinical documentation. Richard’s role in these products has progressed along the software engineering career path. For the last 15 years, Richard has been in technical leadership roles on various products. Richard’s latest endeavor is to guide McKesson along the path of being a better software product development organization. Richard is the engineering director for the ADM business. Richard is also involved with the McKesson office of the CTO. In that role, he is involved McKesson-wide activities including technical due diligence for merges and acquisitions, technology convergence initiatives, technology adoption initiatives, technology acquisition initiatives, and process adoption initiatives.

Michael Robbilard is coming up on 20 years in software development, primarily commercial enterprise software. His roles have included software developer, architect, analyst, and several leadership roles including leading the Definition and Design organization within McKesson. In his current role, Michael works for the Office of the CTO at McKesson with a focus on using process improvement as a tool to improve the business performance of the various business units within McKesson. He is also a member of the Software Engineering Institute and will be chair of the People, Teams, and Workforce track in the upcoming North American SEPG conference in Portland.

User Story Best & Worst Practices

Charles Bradley

Charles Bradley

Charles Bradley has coached several teams on how to get the most out of their User Stories and Scrum practices. In this session, we’ll explore some of the Best and Worst Practices when developing User Stories. We’re not talking the “INVEST” acronym here, we’re talking real life experiences of using and abusing User Stories. Each User Story abuse results in a negative consequence, which usually means process waste, or maybe a lack of confidence in User Story practice altogether. We’ll also focus on the positive as well, discussing some User Story best practices, and how to encourage teams to move speedily from Worst Practice to Best Practice.

About Charles Bradley

Mr Bradley is the author of the “Scrum Crazy” blog at He is an experienced Scrum Coach, Certified ScrumMaster, and Certified Professional ScrumMaster I. In addition to his Scrum credentials, Mr. Bradley is also a highly capable, full lifecycle experienced, software development team lead that prefers XP for good engineering practices. He is Sun Certified in Java, and has 13 years of experience in J2EE application development across all tiers. More recently he has also picked up some good C# experience as well. In his spare time, he enjoys driving his wife crazy by talking about Scrum, especially when he refers to his “honey do” list as his “personal backlog” and asks his wife to prioritize her backlog requests. He lives in Denver, Colorado, and he is easily found on LinkedIn.

Customer Development: Learn, then Burn

In the world of technology startups, there are winners and losers. Winning startups  discover the right product to develop before running out of money. In this workshop, attendees will get hands-on experience with techniques that will ensure their product and their business model are hitting the right sweet spots before they crank up their sales and marketing burn rate. This entails iteratively learning what customers are willing to pay for, i.e. Minimum Viable Product (MVP) and applying Agile practices to building the MVP. Kevin leverages his experiences running and mentoring technology startups.

About Kevin Taylor

Kevin is passionate about discovering interesting market opportunities and building technology and fledgling organizations to pursue them. He is also active in the agile and software craftsmanship communities. Kevin is founder and president of Obtiva , CEO of EventWax, and a technology entrepreneurship lecturer at DePaul.

Agile Hardware—What Hardware Developers Are Learning from the Agile Movement

John Farnbach

John Farnbach

For engineers whose projects involve hardware development, this session presents tools to strengthen financial results by adapting quickly to changing customer requirements and technical innovations.  Whereas “best practices” for hardware development require plans to be frozen before starting a project, Agile hardware development frees engineers from the yoke of frozen plans without slipping the schedule or blowing the budget. Commonly called Flexible Product Development (FPD), these methods add critical capabilities to a company’s phase-gate processes to support swift delivery of innovative solutions for today’s fast moving markets.

About John Farnbach

John Farnbach is Principal of Silver Streak Partners LLC, helping companies improve the business value of product innovation.  He works with leadership teams to create a new product operation that produces higher returns, reduces fire fighting, and fits their culture and vision.  John holds a Ph.D. (EE) and has 35 years’ experience in product development at large and small companies in a variety of industries.

Rapid Release Planning – A New & Better Way to Estimate & Validate Stories

One of the greatest pitfalls in the Agile world is coming to the table at sprint or iteration planning meeting without having stories prepared with the correct level of detail. Proper release planning can help fix this situation. In addition, one of the most dreaded parts of great planning is effective estimation. This hands-on tutorial/workshop will allow participants to learn the process of rapid release planning and allow them to give it a shot in a mock planning simulation. LEARN TO PLAN FOR ESTIMATE AND VALIDATE OVER 300 STORIES IN UNDER SIXTY MINUTES WITH TRIPLE VALIDATION ON THE ESTIMATES!

About Lee Henson

Lee’s 12 years of experience spans a broad array of software production roles and responsibilities. He is currently one of just over 100 Certified Scrum Trainers worldwide and has Certified well over 1000 ScrumMasters and Product Owners. Lee has worked hands on as a GUI web developer, quality assurance analyst, automated test engineer, senior product manager, senior project manager, ScrumMaster, agile coach, consultant, and ADDIE training professional. He has worked with hundreds of teams to assist them in successful implementation of thousands of projects. His client list includes over 25 of the Fortune 100 companies, Government sector projects, small and large software production facilities, and multiple successful large-scale e-commerce implementations. Lee is a graduate of the Disney Management Institute and has served as Chairperson for the Scrum Alliance Certification Advisory Board. He is the author of the Definitive Agile Checklist and publishes the Agile Mentor monthly newsletter. He is the inventor of Rapid Release Planning and is continually looking for ways to advance the Agile and Scrum community.

Executive & Enterprise Agility Track

Productive Joy

We are naturally creative, intelligent, and passionate. How many kids do you see who aren’t curious? That sit quietly when left to their own devices? We explore, create, and delight! Then it is beaten out of us by a society which believes that such things are disruptive to the state of the universe. In order to have joy at work we must examine
times when we naturally slip into states of joy.

● While collaborating
● While self directed
● While purposeful
● While Challenged
This list is not conclusive. It is a starting point for a discussion on bringing joy to our workplaces.

About Zachary Spencer

Zachary Spencer is an organization development coach who focuses on building trusting relationships between business units. He specializes in product companies and other IT organizations.

A Day in the Agile Life at a Financial Services Company

Beth Bleimehl, Mike Banta, Doug Huffman, & Paul Quarles

A panel of Agile practitioners from a Denver-based Financial Services Corporation discusses key elements of their Agile practice.

Topics include:

  • Experience with Agile Roles and Engagement of Coaches
  • Initiation of Agile process for legacy systems with off-shore partners
  • Quality practices in an Agile environment: embedded system testing, centralized Quality Control
  • Organizational Stumbling Blocks as Agile Expands

A question & answer session follows.

Speakers: Beth Bleimehl, Mike Banta, Doug Huffman, & Paul Quarles

About the Panel

Mike Banta is a 30 year veteran of application software development, with 27 years at OppenheimerFunds. Working with many platforms, with an emphasis on legacy mainframe applications, Mike plays many roles at the firm including leadership, application development, offshore team mentoring and coaching, business analysis and liaison, and training. His current focus for over two years has been the growth of the Agile program at OppenheimerFunds, working as a team member, subject matter expert and Agile coach.

Doug Huffman is a Software Delivery Professional with over 20 years of experience across multiple industries. Doug is currently providing program leadership for OppenheimerFunds Delivery Services with a focus on Agile practices. Prior to his program leadership role, he served for two years as Agile Delivery Manager for two Scrum teams at OppenheimerFunds.
Paul Quarles currently serves as a Product Owner at OppenheimerFunds and has been in that role for the past two years. Prior to that, he was the department head for Oppenheimer’s Back Office group which interacts with the dealers in the mutual funds and personal financial planning space. Paul is a Certified Product Owner and currently mentors the other PO’s in our Agile program.

John Nicol has been in the software development arena for 25 years working in a range of industries from startups to Fortune 100 companies. He has held positions at various levels including executive management, project and program management, software development, and consultant. John has been in the Agile space since 2001 and has trained and/or coached over 60 teams in Scrum and eXtreme Programming (XP). He works with managers, executives, project managers, and directly with development teams. John is currently the Agile Program Manager at OppenheimerFunds, and is a Certified Scrum Professional (CSP), Certified Scrum Master (CSM), Certified Scrum Product Owner (CSPO), and Project Management Professional (PMP).

Beth Bleimehl has been in the software development and delivery industry for 21 years (first career was accounting and finance for 12 years). She has worked in a variety of industries serving many different roles to include consulting, development and QA leadership, customer account management, program management over several sub consulting firms, and project management. Most recently she has been developing a Quality Program at OppenheimerFunds, which includes liaison responsibilities between the various software delivery teams, infrastructure, Internal Audit, PMO, and other compliance groups within the firm.

Using Agile Principles to Solve Tough Problems in Your Business

We believe Agile is the best way to solve hard problems as a team and that we need teams to solve hard problems. Agile practices have historically focused on software but the principles underlying these practices can be applied to any hard problems. You are all working on hard problems in your business and are guiding teams that are helping to solve these problems. The concepts in this talk will give you insights into how to make your work and your teams’ work more effective. Learn how others have made 4x improvements in visibility, productivity, quality, or time to market for their solutions to hard problems. We will look at several models underlying Agile practices including:

  • Conditions in which hard problems exist (Cynefin, Lean Startup)
  • How humans respond effectively in these situations (Systems thinking, Tuckman team model)
  • Tools humans can use to make sense of the problems and situations (Lean models, divergent-­‐convergent thinking model, consensus checks, change models)

About Rachel Weston and Zach Nies

Rachel Weston is the Director of Services at Rally Software in Boulder, Colorado. She has over 10 years of experience in the software development industry working with both in-­‐house IT and product development teams and as a consultant working on software and strategic initiatives. Rachel has held many functional roles
within software teams, including IT Manager and Director, Project Manager, Business
Analyst, Tech Writer and QA. Throughout her career, she has worked actively to improve
processes in order to create a more collaborative, successful and therefore satisfying working environment. She is passionate about the positive changes Agile methods can enable for software development teams and their customers. Rachel holds a Masters in
Linguistics with a specialization in Computational Linguistics from the University of Colorado at Boulder, and received her Bachelor’s degree in Mass Communications
from  the University of California Berkeley.

Zach Nies brings close to 20 years of engineering and product development experience
to Rally’s innovative products. Prior to joining Rally, Zach served as Principal Architect and
Director of Systems Architecture for Level 3 Communications and founded a small start  up which was quickly acquired by the publicly traded Creo, Inc, now a division of Kodak. He also served as Chief Software Architect at Quark, where he provided the overarching technological vision for the company. Zach’s product vision has won numerous industry awards, including Jolt Product Excellence awards, Seybold HotPicks and the prized MacWorld Best of Show. Zach has served on standards bodies such as the W3C’s HTML working group and on the board of directors for Agile Denver.

Agile Leadership for the Learning Organization

Jan Beaver

Jan Beaver

Organizations adopting agile need to move away from traditional management and embrace leadership at all levels. But what is leadership? And how do we transform a culture of management into a culture of leadership? This talk examines the origins of traditional management and its limitations when applied to creative knowledge work; the emergence of servant-leadership; the importance of self-organization for motivation, innovation, and creativity; and provides guidance for building a culture of leadership.

About Jan Beaver

Jan Beaver is a Ph.D. educator with over 25 years’ experience in the software industry. His experience covers the gamut of functional management, development using many different languages and environments, QA, technical writing, and beyond. Drawing upon this long and varied experience, he brings a depth and breadth of knowledge to every endeavor as well as a passion for the power of agile to create an environment in which creative knowledge work thrives. Jan is currently a senior agile trainer and coach with RippleRock.

Open Space Track

The Open Space track of this conference will be completely self-organizing.  Attendees will have the opportunity to propose topics throughout the day by adding 3 x 5 cards to the wall where they will be grouped into like areas by track facilitators.  The main hall will offer multiple breakout tables and flip charts where small groups can gather to discuss these topics.  There is no time limit or agenda for these discussions, in fact, hopping from table to table based on your interest is encouraged.  Use the “Law of two feet”: if you feel that you are not contributing or benefiting from a presentation, please feel free to move on to something else. It’s agility in action!