Come and Take It! Lean Pull Applied
—— 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.
This session consists of two parts. The first is an exploration of the ideas behind lean “pull” and will run for about 30 minutes. In this part we will explore the idea of pull in lean manufacturing and make the case for how it is both similar and different than software development. The second is a live demonstration of how these ideas can be put into practice in a software development environment and will run for about 45 minutes. The remaining time will be open for a dialog between the presenters and attendees.
In the demonstration portion of the session we will engage in a role-playing demonstration between a product owner and developers. In a series of short iterations we will together create stories, acceptance criteria, and executable specifications which act as signals pulling test, code, design, and conversations. Out of this process a real, working system will be built. Throughout, we will be employing behavior driven development as a better way of capturing requirements and thinking about a system.