The workshop will start off with the group developing a set of core areas that they want to discuss in detail, and then we will explore the areas in depth.

• Evolve a shared project vision
• Discover key user workflows
• Identify usability requirements
• Employ an appropriate set of agile practices
• Quickly prioritize issues according to business value and return on investment
• Test system effectiveness through collaborative usability reviews

Whilst working with various clients in large and small teams and in large and small enterprises, we have come across a number of behavioural and organisational patterns which in the context of Agile Development we term Enablement Patterns. Some patterns are tactical in their application while others are more strategic.

In the session we will discuss our findings - the 20+ patterns we have catalogued - and attempt to challenge and expand on this base set.

Stakeholders pay for the privilege developers enjoy as a tool-builder.

This is how software teams are paid.

If we sold chickens, we would say, “these chickens are healthy and plump, and therefore worth more than this sickly, scrawny old cow”.

Many Agile projects involving more than one person deliver on time and on schedule with high quality, yet fail to satisfy the project stakeholders. All too often we find ourselves with an unhealthy cow when the market was demanding chicken.

The purpose of this workshop is to explore the topic, “Directly involving developers with customers makes money”.

Perhaps you don't want to be a lobbyist. Now what? We'll explore what one person or a group of coworkers can do to adopt some agile practices without needing anyone else on the team to change their ways. Along the way we'll create a card game (Elbow Room in a Straitjacket) to refine our understanding of the discussion.

The purpose of this Workshop is to create a list of other words, other practices, that can be practiced at intermediate levels by interested agile teams.

The map will be explored to improve our understanding of the practices we do and how they can be improved. Including:

• Which practices provide more value when used in conjunction with other practices.
• How does development background and personal values affect preferred practices.
• How one practice can indirectly support another practice that may have more value to someone else.
• How local regions on the map allow you to investigate practices that may be of direct benefit to you

In this workshop we will:

• explore how their companies make money, and how that relates to the work they do on projects
• practice building a project related business case
• present a project related business case

The goal of this workshop is to discuss and produce a list of practices, rules, patterns (or however we choose to define agile testing techniques) that we (the workshop participants) agree upon. We’ll use a list we’ve compiled as a starting point, but expect many ideas to surface in our discussions.

The insurance industry, telephony, ice-cream manufacture, etc, all have their own vocabulary, constraints and patterns which can be most conveniently expressed in a purpose-made language. With clever engineering, we can design a compiler and runtime framework that can input such definitions and generate an insurance/telephony/ice-cream system.

With such a system at our disposal, creating our next insurance or ice-cream system becomes very rapid: development jobs become small-scale, that would be considered large scale if done from scratch; and consequently much more amenable to agile methodology. This workshop will explore that proposition.

The purpose of this workshop is to create a list of desired attributes of "software testing" graduates, which will help demonstrate to schools that there is a market for such a curriculum.

The aim of this Think Tank is to agree the top five tips we can give to anyone contemplating forming a dispersed team.