What Kata Gives Agile That Retrospectives Never Could

Дата публикации: 28-06-2026 06:00:00

Image


Watch a team run its retrospective for a few sprints and a pattern shows up. The same two or three sticky notes return every time. Communication could be better. Testing happens too late. We keep getting interrupted. The team talks about each one, picks a couple of action items, assigns them with good intentions, and moves on. Next retrospective, the same notes are back on the wall. Everyone agreed to improve. Almost nothing changed.This is not a motivation problem and it is not a bad facilitator. It is a method problem. Scrum is built on empirical process control, on the loop of inspect and adapt. Teams have gotten reasonably good at the inspect half. They look at the increment, they look at the board, they talk about what went wrong. The adapt half was never given a defined method. "Improve continuously" is an instruction without a routine, and an instruction without a routine becomes a brainstorm that produces a to-do list. That is the gap the Kata fills.Jumping to Solutions Is the Default FailureWhen a team spots a problem, the brain wants to skip straight to the fix. Testing is late, so let's add a testing column. Interruptions are killing us, so let's block Fridays. These are guesses dressed as decisions. Nobody measured where the team actually is, nobody defined where it is trying to get to, and nobody set up a way to learn whether the change worked. The action item gets done or it does not, and either way the team has learned nothing it can build on.Mike Rother named this gap when he studied what made Toyota's improvement durable while other companies copied the tools and got nothing. In Toyota Kata, he argued that the real engine was not the tools at all. It was a practiced way of thinking, a repeating routine that turned vague "get better" energy into disciplined experiments. He called the routine the Improvement Kata, and he paired it with a second routine for the people coaching it. Kata means a pattern you practice until it becomes second nature, the way a musician practices scales. You do not negotiate the pattern each time. You run it until it runs you.The Improvement Kata Is Four Honest StepsThe Improvement Kata is deliberately small. There are four steps. You agree on a direction or challenge, something six to twelve months out that matters to the business. You grasp the current condition with facts, not impressions, because most teams describe where they think they are rather than where they actually are. You set a next target condition, a specific measurable state you want to reach in the next few weeks. Then you run experiments toward that target, one small step at a time, learning from each before taking the next.The hard idea inside this is the threshold of knowledge. You can see the challenge, and you can see the target condition, but the path between where you are now and where you want to be is unclear, and you cannot plan your way across it. You can only discover it by experimenting. Each experiment is a tiny prediction. We think doing X will move the lead time from twelve days to nine. You try it, you compare what happened to what you expected, and the gap between the two is the actual learning. This is the scientific method shrunk down to fit inside a sprint.Notice how different that is from a retrospective action item. An action item is a task you complete. An experiment is a question you answer. One leaves you with a checked box. The other leaves you with knowledge about your own system that you did not have before.The Coaching Kata Is the Part Managers Were Never GivenAgile has talked about the servant leader and the coaching stance for over twenty years. It rarely told anyone what to actually do on a Tuesday morning to coach. The Coaching Kata does. It is a routine of five questions a coach asks the person running the Improvement Kata, and the questions are nearly always these. What is the target condition? What is the actual condition now? What obstacles are in your way, and which one are you tackling now? What is your next step, and what do you expect? When can we go and see what you have learned from that step?Read those again and notice what is missing. The coach never gives the answer. Most managers, when a team is stuck, reach for the solution because they were promoted for having solutions. The five questions break that reflex. The coach owns the thinking process, the learner owns the problem and the solution. A Scrum Master who runs these questions in the Daily Scrum is doing something concrete and repeatable, not performing a vague facilitation role. As a coach myself, this is the part I find most valuable. The questions are simple enough to follow and strict enough that you cannot quietly slip back into telling people what to do.Where It Meets ScrumThis is what brought me to teach the Agile Kata, the version Joe Krebs developed to fit the pattern to agile work. His book Agile Kata keeps Rother's scientific-thinking core and wires it into the way agile teams already work. It runs alongside Scrum rather than replacing it, which is why Jeff Sutherland, who co-created Scrum, endorses it. The cadences line up cleanly. The challenge sits at the product-goal horizon. A target condition spans a sprint or two. Each sprint carries one or two experiments toward it. The daily scrum becomes the coaching cycle. The retrospective stops being a solution brainstorm and becomes the place you design the next experiment and inspect the last one.That single change rewires the retrospective. Instead of "what should we fix," the question becomes "what did our last experiment teach us, and what is the smallest next thing we can test." The sticky notes stop repeating because the team is no longer guessing at fixes. It is running a method that compounds.If you want to try it without buying anything or restructuring anything, do this. Pick one challenge the team genuinely cares about. Measure where you actually are this week. Write down one target condition for two sprints out. Run one experiment, predict the result before you start, and at the next retrospective compare what happened to what you expected. Then have whoever runs your daily scrum ask the five questions, in order, without offering a single answer. The discomfort of not answering is the whole point. That discomfort is the sound of a team learning to think for itself, which is the only kind of improvement that lasts after the coach goes home.Ralph Jocham is Europe's first Professional Scrum Trainer, co-author of "Professional Product Owner," and contributor to the Scrum Guide Expansion Pack. As an ICF ACC certified coach, he works with organizations to build Product Operating Models where strategic clarity, operational excellence, and adaptive learning create measurable competitive advantage. Learn more at effective agile.References[1] Rother, M. (2009) 'Toyota Kata: Managing People for Improvement, Adaptiveness and Superior Results', McGraw-Hill. Available at: https://www.amazon.com/Toyota-Kata-Managing-Improvement-Adaptiveness/dp/0071635238[2] Krebs, J. (2024) 'Agile Kata: Patterns and Practices for Transformative Organizational Agility', Pearson / Addison-Wesley. Available at: https://www.amazon.com/Agile-Kata-Practices-Transformative-Organizational/dp/0138118302[3] Proaction International 'Toyota Kata: A Complete Guide for Successful Implementation'. Available at: https://blog.proactioninternational.com/en/toyota-kata-guide[4] Portman, H. (2025) 'Summary and review Agile Kata', 21 April. Available at: https://hennyportman.wordpress.com/2025/04/21/summary-and-review-agile-kata/[5] Comparative Agility 'Agile Kata Assessment'. Available at: https://www.comparativeagility.com/capabilities/agile-kata-assessment/

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Cognitive Trap: Sprint Commitments Misunderstanding	0	7	29-06-2026
2	Lean Agile Practioner - A Scrum Master Competency No One Talks About	0	5	07-07-2026
3	Stehen sich Scrum Master selbst im Weg? 5 hausgemachte Probleme, die du überwinden musst	0	6	29-06-2026
4	The New AI Operating Model. Start By Using Scrum	0	6	07-07-2026
5	Silos are the Bane of Value Delivery	-5	7	29-06-2026
6	Myth: The Scrum Master has to be at every meeting	0	5	06-07-2026
7	Ordering the Product Backlog with RICE: From Opinion to Evidence	0	5	09-07-2026
8	From Chaos to Control, Part 5 - Goal	2	6	02-07-2026
9	If You Can Facilitate a Retrospective, You Can Audit Your AI	5	7	28-06-2026
10	Your Agile Transformation is a Lie You Wanted to Be True	-6	4	25-06-2026

Классификация: Мнения. Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 6. Источник: scrum.org.