program selection system

Automated unit testing is the agile software development equivalent of “in-process inspection” in Lean Production systems. xUnit is the generic name given to the family of tools/frameworks used by developers when developing automated unit tests. The community has now had enough experience with using XUnit to start cataloging “best practices” and “not so best practices” as patterns and smells. This tutorial introduces a number of these “test smells”, describes their root causes, and suggests possible solutions expressed in the form of patterns.

Is your agile project buried under a mountain of user stories? As you add stories, does your vision of the product you’re building grow hazier? As story count increases, do business stakeholders become more frustrated with prioritization? Do you find it difficult to communicate the big picture of what your system does?

90 Word Abstract :

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?

As Agile practitioners, we recognize the need for a strong and accurate user voice on the Agile team. And yet, an Agile project leaves little time for elaborate up-front design and lengthy user research. In this session we’ll practice the User Feedback Two-Step, the dance that user representatives on a team have to play to interleave their work with the developers and with end-users. Nimble players can be ready with designed and tested user interfaces at the point where developers need them, while implementing user acceptance testing in parallel.

Congratulations! You’ve just been granted initial funding for your Agile project! As the product manager you understand the market opportunity for your new Beer Miles rewards loyalty program, but how do you go from the business case to a product backlog? Your accountant says return on investment is key, the Marketing Director says user experience and community are key, while the IT says scalability and fault tolerance are high priorities. You have limited time and budget, and the pressure is on to make the product a success.

What’s a mental model? Those in the field of cognitive research have been defining mental models for a few decades. The term “mental model” has come to mean “a mental representation.” The mental models described in this presentation are representations of people’s behavior, philosophies, and emotion around how they accomplish something, regardless of which tools they use. Aligned with the ways you support users, mental models provide a clear roadmap of where your organization should invest its energies, and also where it shouldn’t, allowing you to stretch your limited resources.

Intent
The intent of this session is to expose participants to the challenges faced by distributed agile teams, to allow them to discover ways to mitigate those challenges, and to have fun.

Summary
The Distributed Agile Game is meant to be played by people who are interested in challenges experienced by members of distributed agile teams. The participants may have prior experience in distributed development, but this is not required. In fact, no software development experience is required.

Getting a build system right can set the tone of development for years, and yet teams constantly re-invent wheel over and over. The application of a few key tools, such as Maven and Continuum in a sane ecosystem can provide a solid base for project growth and developer sanity, and can encourage the mature use of Agile practices and processes. Well designed automation of building, testing, and reporting can provide invaluable developer ease and fast feedback to developers and and other stakeholders.

Main Message:

Continuous Integration has put a lot of focus on automation of the build and unit test process. This quest for automation has been expanding to include more and more automated tests and deployments as well. This presentation provides an overview of how to apply automation to activities further within the life-cycle.

Description:

The second great myth of software development training is the notion that most programming most of the time is on new code. In fact, most developers spend most of their time working on CRRAP: Code Requiring Remedial Attention Promptly. In this course, we’ll lay out the five basic patterns for bringing complex legacy code under perfectly tested control. If you’ve ever heard or said “Don’t touch that, you don’t know what it’s connected to,” this class is for you. Each pattern is illustrated with a complete real-world