program selection system

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?

It’s easy to write software. It’s harder to write software that’s simple, elegant, working and important. Examples help to drive conversation, avoid ambiguity, eliminate waste, make estimates more accurate, clarify design and produce software that matters. Participants will develop a small game in a Renga (taking it in turns), adding examples of desired application behaviour at both a system and unit level, while learning BDD concepts.

—— begin 90 word abstract ——
How can we as software professionals and craftsmen know that we are producing the most valuable system at just the right time for our users? The concept of “pull” from lean manufacturing challenges mainstream approaches to software development and reconsiders how value is delivered to the customer by inverting the thought process and focusing first on delivery. In this demonstration participants will experience how a real working system can be constructed from the ground up by employing popular industry “signals” to “pull” the creation of working software.
—— end 90 word abstract ——

Come and take it! Learn how to build the right system where each agent takes just what they need, just in time, to create value for the customer.

How can we as software professionals and craftsmen know that we are producing the most valuable system at just the right time for our users? The kanban method and the concept of “pull” from lean manufacturing, in combination with agile values and practices, provide a powerful guide for how we can improve our profession by employing popular industry “signals” to “pull” the creation of working software.
By inverting the thought process and focusing first on delivery, “pull” challenges mainstream approaches to software development by reconsidering how value is delivered to the customer.

In this demonstration participants will experience how a real working system can be constructed from the ground up through the definition of executable specifications. See how through a series of micro-iterations, requirements can pull the creation of executable specifications, developer tests, production code, and refactorings.

“The process of pulling value from a project injects features into the system”.

Feature Injection is a Tool for Business Analysts. It allows us to identify the minimum marketable features.

This approach is a synthesis of traditional analysis techniques (UML etc.) and TDD / BDD. Feature Injection is a fast, lightweight technique that avoids analysis paralysis. The Business Analyst knows when they are finished in the same way a Developer knows they are finished in TDD / BDD.

Feature Injection is based on Real Options and Kolb’s Model of Learning.