Published: June 2015
Your team is stressed; priorities are unclear. You’re not sure what your teammates are working on, and management isn’t helping. If your team is struggling with any of these symptoms, these four case studies will guide you to project success. See how Kanban was used to significantly improve time to market and to create a shared focus across marketing, IT, and operations. Each case study comes with illustrations of the Kanban board and diagrams and graphs to help you see behind the scenes.
Learn a Lean approach by seeing how Kanban made a difference in four real-world situations. You’ll explore how four different teams used Kanban to make paradigm-changing improvements in software development. These teams were struggling with overwork, unclear priorities, and lack of direction. As you discover what worked for them, you’ll understand how to make significant changes in real situations.
The four case studies in this book explain how to:
What seems easy in theory can become tangled in practice. Discover why “improving IT” can make you miss your biggest improvement opportunities, and why you should focus on fixing quality and front-end operations before IT. Discover how to keep long-term focus and improve across department borders while dealing with everyday challenges. Find out what happened when using Kanban to find better ways to do work in a well-established company, including running multi-team development without a project office.
You’ll inspire your team and engage management to make it easier to develop better products.
Q: Does Kanban work in real life?
A: Absolutely. One of the strengths of Kanban is that it’s easy to apply to a range of different contexts. The book contains four in-depth case studies where Kanban was used. In one case, Kanban was applied across the full value stream. In another case, Kanban was used in a back office team outside IT. Being able to see the full picture, and getting focus, better collaboration, and teamwork were some of the benefits reported by our teams in all four cases. Kanban won’t solve problems for you. That’s up to you. In the book, you’ll find plenty of tips and tricks our teams used to do just that.
Q: What will I get from this book?
A: You will get an insight into how the different teams set up their Kanban boards, how they interacted with the board and what worked for them. You will find various tips and tricks our teams used to problem solve across organizational borders. You will learn how we trained management to see strategic improvement opportunities, which helped us avoid “plateauing” after the first Kanban implementation. It also helped management to look beyond existing practices—to see, discuss, and replace old and heavy processes with simpler and better ones.
Q: How do I improve with Kanban?
A: Kanban helps greatly by giving you focus if you respect the board. Kanban can also help you visualize bottlenecks, delays, and quality problems such as rework. But it doesn’t solve them for you. That’s up to you! The good news is that you will find plenty of tips and tricks in the book our teams and managers used to address problems.
Kanban does not tell you what decisions to make or what to pay attention to. You have to look for the right indicators in order to see them. In the Introduction chapter, I share the long-term thinking that helped guide our improvement efforts and helped us train managers to see and close the gap between observation and action.
Published: June 2015