October 1, 2018

Agile IT management

Nowadays companies often try to copy any model that seems successful for another company or even competitors. They try this with things like Scrum, LeSS, SAFe, the Spotify model or Lean startup. The reality is that if you are not that other company there is no reason to believe that these models work out for you. These models will not give you a strategic advantage. They might as well keep you further from it.

Agile product development at its core is a collection of patterns and methods. All these patterns can be applied on different levels. In this workshop you will learn and experience that everything from the strategy to the way work items are being deployed is connected. We look at product development with an holistic view.

During the training the following four subjects are plotted on in the strategic-, business- and operational model:
– strategy,
– product,
– process
– people.

You will learn that a strategy (or the part of a strategy) that is focussed on innovation (example A) has an entirely different approach than the strategy (or the part) that is about maintaining the current landscape (example B). These different approaches all have different patterns, tooling and measurements. During the training you will learn and experiment with the best suited patterns for each situation. You will create an ever expanding toolkit of agile product development patterns.

One crucial part of successful product development is measuring and validating the effectiveness of the four subjects listed above. From an agile management perspective this is the way to be in control: experimenting and validating the results. You will learn about business goal validation.

Summary of subjects:


– Which strategy for what purpose, the effects of a wrong or unknown strategy. Business goal validation.


– Lean startup, Feedback, Experiments & validation, feature teams vs component teams, hypothesis driven development.


– Agile, flow of input, Scrum, Kanban, Lean, continuous integration and delivery, DevOps.


– T-shape, innovation, engineering culture, expectations, roles, shift left.

Please feel free to contact me for possible configurations of this training.