“Before, we spent at least one hour a week discussing priorities estimating and rescoping. On top of that, the developers were constantly getting into debates about priorities.”

This was due to the production system being used by eight different teams. Each with their own profit and loss accountability. So naturally they would fight to have their problems fixed first or bully developers.

It was very much a case of he who shouts loudest, gets.

The result? A very aggressive unfriendly and uncooperative environment that sucked the life out of the team.

Yet after the implementation of a simple Kanban system, all that wasted effort planning, setting priorities, scoping and estimating were instantly eliminated.

Just with a team of seven people this resulted in a per annum 50’000 CHF saving.

Not only that but the business representative could see where work was and who was working on it without having to ask anybody! It was just so much more efficient.

And remarkably the average fix time was reduced from over 60 days to just 13, within three weeks.

Happy days!

Where there any other benefits? Well, it was clear to see where there were bottlenecks. For example, a lack of skills in a particular technical area especially during the holiday period. Before people knew this implicitly whereas now, these were slowly being visualized and made transparent and were therefore explicit.

The only issue the team themselves could not fix was that of a typical large organization: We wanted the team to sit together which meant moving two people 50m across the room but that would have cost 2500 CHF each, rather than just being able to move desks.

Well we can’t solve everything but we can at least get these challenges open to discussion.

Yet, how does Agile help teams to build trust? Read about that next

Does this Story Sounds familiar to You?

Want to know how we resolved it? If so, then contact us. We can discuss it and just maybe we can help you.