Over the past couple of years, my colleagues and I have led dozens of implementations in a variety of companies. As we closed the second year of our company we began noticing the problems and costs incurred by the fact that we each worked differently. E.g. miscommunications, differences in outcomes, and rework done between implementations. We decided it was time we go and analyze our past implementations for common goals and methods of operation.

The result of this was a set of goals and implementation building blocks, and following the past year in which we have implemented what we have learned, a wonderful recipe as well! In this presentation, I will show how organizations who aim to improve their predictability and time to market can start their agile journey as focused and painlessly as possible by the use of a recipe we found common to many organizations. At the heart of this presentation is the question “do you need to go “all out” to be agile?” as well as a more pragmatic option to a very big debate going on today in the agile community “do we do a big revolutionary scrum style change or an evolutionary small Kanban style change?”