Agile, XP programming and Business Collaboration
Performance gains are par for the course when development teams adopt an Agile methodology. But are teams experiencing the "times ten" productivity improvements that Agile advocates project? This track provides insight on how to organize your Agile teams and lead those teams to greater productivity. The foremost agile authorities walking the planet today join forces for the first time ever in the same place at the same time to share their experiences in producing quality deliverables as stakeholders and business users demand more and more from development teams.
Agile sessions confirmed:
- Agile Track Keynote: Agile Schmagile: The Backlash Against Agile
- The Diabolical Developer: What You Need to Do to Become Awesome
- Distributed to the Extreme: The Open Source Development Process
- How to Reap the Benefits of Agile-Based Test-Driven Development
- Test Smells in Your code Base
- Throw Away All The Rules. Now What Process Do You Follow?
Jon Kern, Software Architect, Agile Mentor, and co-author of the Agile Manifesto
It would seem that Agile isn’t the foolproof silver bullet that we said it would be! Oh, wait, we never said that. Okay, so not all groups doing agile succeed in perfect delivery of software. And not all folks trained in two days of Scrum are truly "Masters." The anger against “agile” is palpable in many discussion groups and blogs, but is it misguided?
What should we do? Go back to Waterfall? Train people for four days? Well, Agile Manifesto co-author Jon Kern thinks it is time we do a re-set, and (re)educate folks on what agile is all about. If you are dogmatically following along with a handful of agile practices, but don’t really “get” the intentions behind the agile mindset, you may be disappointed in your results.
Agile is hard to do well despite it being simple. Let’s re-commit to the core principles and practices. Let’s do Agile Like We Mean It -- it isn't easy, but it's worth the effort.
Martijn Verburg, Consultant & Community Leader for Java and Open Source software
After spending the last few years utilizing best practices in Java, following lean/agile techniques, practicing software craftsmanship and listening to Java development "gurus," Martijn Verburg thinks he's discovered that it's all one great big hoax! In this session, Verburg -- development consultant, author and London Java Community Group leader --offers advice on how to free Java developers from what he calls "the chains of the industry" and help them get back to actually doing their jobs. By the end of this talk, Verburg promises, you'll be re-invigorated about your role as a developer and feel like you have the power once more.
Verburg's session will offer several practical suggestions to help Java pros get back to basics in these areas:
- How to get the right attitude, master self learning and effectively work by yourself
- Using only the tools you need, and sticking to what you know is best.
- Maximizing end user testing, which is usually enough to go on.
Emiliano Conde, CEO, jBilling Software Ltd.
Open source development is done in many cases in an extreme environment: with a fully distributed team that has never seen each other’s faces. How could this work, when many agile software development processes start from having the whole team in the same location? As founder and lead developer of a large open source project, Emiliano Conde, explains with concrete examples the processes and tools that need to be in place in order to achieve productivity and quality in a distributed agile environment.
By attending this session, anyone who participates in an agile development environment will:
- Learn what to take, and what to avoid, from standard agile processes like Scrum, XP and Crystal when dealing with a distributed team
- Become familiar with the right tools for communication, change management and version control
- Get a close look behind the scenes on how a large, distributed open source team works
- And more
Jonathan Fullam, Enterprise Content Management Consultant, Micro Strategies
Discover how pairing Agile with Test-Driven Development (TDD) helps Java development teams, QA and test managers and system architects reduce Java project complexity and time spent maintaining software. Veteran Java developer and consultant Jonathan Fullam shows how to reap these benefits using real-world examples of Agile-based TDD projects, including daily TDD and Agile process charts and actual code. Through these examples,
Whether you’re a team lead
s, architect s, manager s or anyone with a vested interest in introducing greater efficiencies to your enterprise without sacrificing a hint of quality, attend and discover:
- TDD methods, best practices and an introduction to Kata
- The true meaning of and ways to optimize unit tests
- Java-based unit testing frameworks such as \JUnit and \TestNG
- Test-driven design
- Why and how to adopt a key Agile methodology
- How to use the popular unit testing frameworks \TestNG and /JUnit and the mocking framework Mockito
- How to deal with common objections to Agile and TDD approaches
Lasse Koskela, Author, Test Driven: Practical TDD and Acceptance TDD for Java Developers
Chances are there are anti-patterns in your project's test code. The problem is, you may not know they’re there.
There is a welcome trend towards better code in enterprises all around. Unfortunately that trend seems to exhibit itself mostly in terms of production code. We know more and more about design patterns, language idioms, and domain driven design, etc. but this attitude and attention is directed almost solely towards production code.
The test code we write frequently fails to live up to the same standards. After all, it's just test code... Wrong! We must treat our tests with the same kind of zeal as we do for our production code.
Join best-selling author Lasse Koskela as he introduces the key test smells to look out for – along with what to do when you spot one.
In this session, developers will learn to diagnose and treat their tests for psychological conditions such as:
- Primitive Obsession
- Split Personality
- Separation Anxiety
- Paranoid Personality Disorder
Jeanne Boyarsky, Developer for a New York City bank
Who isn’t constrained by corporate rules on processes? And what happens when the corporate cloak disappears, and the standard playbook is thrown out the window? When our heavily trafficked site decided to update our infinitely popular software, there was no budget, no deadlines and no development process. Yet by every measure, it was successful. When you do something like this, you find out what parts of the agile process really matter, from requirements gathering, to testing, to cutover.
By attending this session, developers will learn how to get started on a grassroots level within a corporate bureaucracy. Managers will learn what parts of a process can be done cheaply and why your developers value certain parts of the process more than others. Specifically, you learn:
- Why UBB is a goner
- The Agile-based Java view of the Buy vs. Build decision
- Hear about low-cost ways to test and do code reviews
- Why Agile eschews the project manager role.