Training: Tweet"Experiment Driven Process Change: Applying Lean and Agile to Tune your Development Process"
However how to drive this highly malleable social system is something we're just not usually taught!
Making changes to a highly complex, people-driven process like software development can be akin to choosing between cutting the red wire or the blue wire on a nuclear bomb - either way there's going to be a mess, how big is the only question. Another alternative is to take on so-called thought-leaders and process experts and to apply their techniques, frameworks (certifications!?) and practices as doctrine. However that's just asking someone else to cut the wires and then blaming them for the boom.
There is a better way. It's time to cut the process-guru apron strings and take ownership of your own software development process. It's your way of delivering value through software development, and so you need the tools and techniques to improve it. No-one else has the magic answer. This tutorial is about giving you the tools to begin to construct a real answer for yourself, to set yourself up for changing and improving your own software development system.
In this tutorial we will start from first principles to (re)discover what a software development system actually is. Attendees will discuss their own contexts against the backdrop of common patterns that will help everyone discover the idiosyncrasies and shared qualities of any software development system. During the morning through exercises you'll learn how to capture your system and how to apply lean and agile thinking to understanding the fundamental question "how do we deliver value through software development".
The afternoon will dive into how to construct meaningful and well-organised process experiments. How to assess those experiments and drive effective change into your own software development process, garnering support and motivating those involved to embrace your well-reasoned improvements as their own. The output of which will be each attendee having taken away not only a number of ideas, tools and techniques to apply to their own software development process, but the knowledge on how to reason and continuously discover more improvements going forward.