After coming across the same situation a few times, I decided it’s time to write about an approach to software delivery team structure that we have used with great success at a major government organisation around 2018-2021. Since then I have worked with three other organisations that seem to suffer from the very same problem - they find it difficult or slow to execute delivery of features or product increments where there are multiple teams involved in the end to end implementation.

Agile coaching emerged as a key role during the rise of Agile methodologies in the early 2000s. Initially, Agile was intended to transform the way software development was managed, focusing on flexibility, team collaboration, and customer-centric approaches. 

If you know something about Kanban and perhaps a little bit about Portfolio Kanban, you may be aware of the need to know and display two signals for your epics that will help you manage your flow of work better.

When I introduce myself as a kanban consultant I sometimes get a puzzled look back. So here are some thoughts on the subject.
Kanban coaching consultants (or just kanban consultant) play a vital role in helping organisations adopt and implement the Kanban Method effectively.

When a team or organisation have never come across Kanban for knowledge work, it is necessary to take a step back and explain the method and the benefits in simple words. This isn’t always easy!

It happens in our practice to come across teams and individuals who have never experienced the benefits of using a certain method or practice to achieve an improvement of some sort. In this case we are going to explore using Agile Software Delivery.