In previous posts, we discussed what you can learn about your team from tracking a minimum of data. We introduced throughput as the most meaningful metric you can get from only the completion time of a work item. In a subsequent post, we explained how you can calculate cycle time and work in progress by tracking the start time of a work item. In this post, we focus solely on how to calculate failure demand and what it tells you about the true delivery capacity of your team.
Today I want to talk about a common digital transformation topic I get asked about, application modernization. More specifically, how everyone is doing it but so few successfully. Typically the conversation starts with one of the following:
“I need to move off my legacy system, how can I use containers to do this?”
“How do we move to a cloud-native microservice architecture?”
“We’ve been told to move everything to the cloud, how do we do that with thousands of applications?”
Often, my initial answer is another question: “Out of curiosity, how did you get to this as your solution?”
Strangely, at that point, it often falls off the rails.
I’ll answer these questions in more specifically at the end, today though I want to talk about complexity and the need to experiment.
One of the biggest problems here is that these are all solutions looking for a problem. While we hope they may be appropriate solutions, hope is not a strategy. On their own, there is not enough information to provide guidance an...
The Unicorn Project from IT Revolution, brings together a number of interesting ideas. In the coming weeks, we are setting up a series of meetups to discuss these ideas from the book and how people look to apply them to their own projects. The first meetup is here.
One of the central themes of the book is around 5 ideals. These are:
Locality and Simplicity
Focus, Flow and Joy
Improvement of Daily Work
Ahead of each of the meetups I plan on writing a blog on the topics we plan on discussing. So first up, I’m diving into the first two ideals and how they might be applied. Let’s go!
Our role at Xodiac in helping organizations with their digital transformations is to create clarity and visibility. Especially as we believe in the importance of creating visibility as the first step in the transformation.
In fact, with seemingly every company undergoing a digital transformation, there are three main requests we are getting from our clients.
Having had some initial success, how do I scale?
What do I need to continue to grow?
How do I know I’m on the right track to achieve my goals?
Below I’ll give an overview of what we’ve seen help with these three concerns and how visibility is so crucial to all of them.
When working with some of our larger customers, we frequently run into common barriers to change. Change is difficult and, no matter how often we say it, there is no silver bullet for how to get there. However, we can say there are commonalities in approaches, things we’d look for and actions we’d take in response to those findings. When we look at the delivery of technology within organizations, we often come across the barriers within how the teams are working, but even more frequently, how the organization is working with technology is the bigger barrier. Developing powerful roadmaps is valuable and greatly helps with generating alignment and a common vision.
In my last two posts, I spoke to blame culture and looking at the whole system. In this post, I’m going to talk through the third of three common organizational problems we encounter, dealing with silos and specialization.
Last Friday I presented a session on outcome based metrics at the Lean Agile Network meetup in Toronto. Based on the popularity of the session and the questions which we didn’t have the time to address, the topic is clearly on many people’s mind. More to come on metrics in future posts, but for now we’ll focus on what you can learn from the simplest metric of them all: throughput.