Slides from my upcoming LSSC11 talk:
More and more organizations want to become more agile these days. When the theory hits the shores of reality, few organizations can get to an idealistic agile feature team that does all testing within sprints, has no need for release-level processes, and where everything is fully automated continuous deployment style. Usually the testing organization is in the eye of the storm when talking about Big Batches, Wastes, ineffective handoffs and mountains of rework, as well as high transaction costs. I’ve recently been using Lean/Kanban flow based approaches to provide a way to evolve testing organizations to a more effective way of working, so that they can better support earlier feedback and higher flexibility. I will present this work as well as case studies from enterprise-level product development companies that are starting to use these approaches.
We will deal with the following challenges:
* Complex environments when it is not realistic to finish all required work within a sprint
* How to visualize and reduce testing batch sizes within sprints/releases using CFD
* How to deal with the testing bottleneck so common in product development organizations – practical suggestions and how to deal with the mindset issues
* How to run stabilization/hardening periods using Flow-based thinking