program selection system

This experience report describes the challenges and steps taken to move a large development team from traditional waterfall test phases to agile test methods. In 2007, our development team started the transition to incorporate agile practices of user stories, daily scrums and time-boxed iterations for our new project. This paper focuses on the changes in test strategies necessary to support an agile development model. Our product is 20 years old, has millions of lines of code in C/C++ and Java. Our team consists of hundreds of developers and testers located worldwide.

—— 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.