Welcome back! Here with another article today and to discuss some of the problems with isolated team level kanban and why you should aim to go as high as possible in the organization. I’ll discuss some of my experiences and go into the downsides of isolated team level kanban vs the organization level. This article isn’t here to downplay the impacts of Kanban and lean principles but show some of the downsides when you’re alone without support. For full context, I think Kanban and Lean are great and have shaped a lot of the background of what I do today.
It’s been a bit busy but I’m back with a requested article. How to calculate cycle time via a formula. This will be a quick article as calculating cycle time is really quick. For more in depth information, make sure you check out my article on DORA metrics and WIP limits. With that said, let’s define cycle time and go from there. What is cycle time? Cycle time in software delivery is a key metric used to measure the efficiency and effectiveness of a development process. It’s the amount of time from when work begins on a piece of software
Back with another article! I’m going to discuss effective ways in reducing cycle time via work in progress limits and other methods for kanban / lean software delivery. These concepts can apply to scrumban as well. Make sure you familiarize yourself with DORA metrics as well as I give a high level overview. What is cycle time? In a software delivery context, cycle time is the period it takes from the moment a team begins work on a new feature, enhancement, or bug fix, until it’s delivered to production. Aka done done. Not dev done. This includes all the stages