What is the Kata model in software development and how does it relate to Lean?

KATA comes from Japanese, which means "type" or "shape". So Improvement KATA refers to a self-improvement model adopted when implementing Agile.

In martial arts, kata is a choreographed pattern of movements designed to enhance memory and perfect martial art movements, a method of continuous practice until habit is established that has now spread beyond the realm of martial arts and into the commercial realm. Especially under Toyota's continuous practice of improvement and optimization, this technology was named " Improved Kata " and recorded in the business book "Toyota Kata".

1. What is the self-improvement model Kata

Kata is a self-improvement model, which refers to the development and guidance of team leaders and members through continuous practice according to the established model to improve their problem-solving ability. Over time, these practices become habits and solidify. This is a series of practices introduced in the book "Toyota Kata" that break down work into smaller, more immediate tasks to achieve a larger, more complex business goal. The Kata model aims to solve problems in a more creative, focused, and meaningful way. It tries to achieve this with a four-part model:

  1. Learn about directions or challenges
  2. grasp the current situation
  3. define goals or objectives
  4. Continuously iteratively move towards the goal, understanding the obstacles that need to be overcome

These techniques are especially useful when the route to a destination is unclear, as experiments can help us better understand problems and find unique solutions. The Kata model is uncomplicated, and each section consists of simple practice items, which makes the model easier to operate and teach.

2. The benefits of the Kata model

Today's technological environment is changing rapidly, creating more complex challenges than ever before. The Kata Model is a scientific, goal-oriented approach to working that enables individuals and teams to effectively address these challenges, and mastering this technique can provide many benefits beyond a structured how-to approach. include:

1. Make the team work towards a common goal

When teams share the same definition and understanding of success, there is more collaboration, less confusion, and greater productivity. This is because they understand how they can contribute to goals, give team members a greater sense of ownership of their work, reinforce their commitment to the overall vision, and encourage proactive decision-making that prioritizes achievement of the end goal.

2. Keep trying and accumulating results

When we know what the goal is but the path to get there isn't clear, taking the first step is often the greatest challenge. However, making experimentation a regular practice can help mitigate uncertainty and serve as a tool towards the final destination. We can make assumptions about how we will achieve our goals, and experiment to see if the assumptions are correct. If it's not the right path or approach, it doesn't hurt us to be right. At the same time, we have more understanding of the right direction. Experimentation is all about continuous learning, improvement, and problem solving.

3. Reduce waste of resources

Focusing on small, sustainable improvements minimizes wasted time and energy, especially on task items that do not contribute to the goal. For example, when reviewing tasks on your to-do list, ask yourself: Will these tasks bring me closer to the next milestone and overall goal? You can also think a little deeper: Given the time remaining in this phase, is there a capacity to solve the problem and handle other tasks at hand, or should certain tasks be postponed?

This strategy is useful to avoid wasting more time switching back and forth between the blocking task and the work at hand.

In addition, the Kata model also reduces the waste of developers, managers and team resources. For example, developers should not focus on non-essential features in the build. Just as a milestone-oriented process ensures they build with purpose, so a manager or technical leader who follows the principles of the Kata model addresses issues that hold back a team's progress. Finally, by maintaining constant communication, efficient feedback loops, and continuous delivery.

3. Steps to implement the Kata model

At its core, the Kata model is about reconciling what we think will happen with what actually happened, and learning from the differences . While this may seem simple, the challenge is that not everyone is born with this ability. Applying Kata model exercises to your workflow requires constant practice and practice.

1. Find the North Star Indicator

The first step requires a clear understanding of the business direction or challenge, which helps inform the planning and what-if experimentation phases. If it’s difficult to determine what the North Star metric for your business is, consider how your team contributes to the larger purpose of the organization, or how you can leverage your team’s strengths to bring your vision to life.

2. Determine the status quo

Before starting to work towards the North Star Metric, take the time to document the team's current workflow, check the team's work against the appropriate metrics, and assess the team's existing knowledge base. Please be honest about your current team situation so you can take a meaningful step toward your ultimate goal.

3. Select the next target

Once you have a clear understanding of your current systems and processes, you can determine what you need to achieve your next goal, or where you want to be after the next iteration. And, the next goal should be a single, substantial change that can be achieved in a few weeks/iterations, bringing you closer to your North Star.

4. Run what-if experiments until you reach your goal

Now that you have an idea for your next goal, formed a hypothesis about how to get there, have an idea of ​​where to start and try, don’t be afraid to fail!

5. Achieve your goals in the fastest way

Speed ​​is necessary, even if it means we may take shortcuts and embrace imperfection. Because we need to confirm the feasibility of this method as early as possible, or discover what unforeseen challenges will be encountered under this method that need to be resolved. Even failure is our rare learning opportunity.

6. Continuous polishing and optimization

After verifying the feasibility, continue to review and improve.

4. Example of Kata model

Say we want to build a new product or service based on an idea, but aren't sure if it will work. At this point, instead of trying to build each step perfectly and gradually expand until its functionality is complete, try to choose a simple goal that can provide some value, which can bring us closer to the envisioned system. There may be many unknowns in this process, but we can learn a lot from the challenges and try different ideas to finally find a way that works. Once the first step is done, reassess where you are now, choose the next goal to iterate on , and continue to reflect on improvements.

As another example, if we are maintaining an internal system that needs improvement, we can choose a problem to be solved and brainstorm some solutions. Different approaches need to be tried and practiced as quickly as possible to get feedback. Once the problem is solved, we can move on to the next problem.

5. The difference between the Kata model and the lean method

Kata and Lean methods differ in many ways, yet complement each other . Lean is the methodology that guides the implementation process, and Kata is the technique that guides the practice. So when Toyota introduced Kata into their lean manufacturing system, Kata became a mainstream business practice. Better practical results can be achieved when these concepts are combined in a unified approach.

Both Kata and Lean principles focus on achieving faster progress, but have slightly different approaches. Kata is a set of methods that can be practiced on a personal level, focusing on continuous improvement and learning through experimentation. This is great for solving non-deterministic problems while learning and developing skills through rapid and repeated practice. It helps to embrace the unknown and teaches people not to be afraid of challenges and obstacles.

Lean principles, such as Lean Portfolio Management, help organizations and teams improve work processes to achieve maximum value with minimum resources. Once an improvement process is established, the next focus is on optimizing the process to make it as fast and efficient as possible.

6. How to use the Kata model

The Kata model is a method teams can use to reinforce Lean principles. While the two focus on different things, they both originally came from Toyota and work well together. For example, Lean philosophy is about eliminating wasteful activities so teams can deliver maximum value. The Kata model supports this goal by hypothesizing that experiments minimize waste. If a method does not produce the expected results, it can be removed from the process.

The Kata model is goal oriented and encourages one thing to be done before moving on to the next, the process is refined until it achieves the desired outcome, leading to greater organizational efficiency, another key point of the Lean philosophy. Most importantly, the Kata model provides a tool approach that can be used in the current state to achieve a lean future state. Breaking down larger goals into smaller task items means that all processes and jobs can be optimized in a targeted manner. In the end, the entire system can generate the greatest value.

Summarize

The Kata model is an excellent tooling approach to support lean goals. When employees and teams adopt a purpose-driven approach, they can easily drive incremental change that maximizes limited resources while reducing waste. Together, the Kata model and Lean can help organizations become more efficient and develop a culture of innovation.

Further reading: Guide to Agile Development

Scrum Development Guide:  Detailed Explanation of Scrum Framework  |  Four Scrum Meetings and Correct Ways to Hold   |  Correct Way to Plan and Execute Sprint   |  4 Key Points for Doing Iterative Planning  |  Do these 4 points to make daily stand-up meetings more suitable for agile Team  |  3 Key Steps to Opening a Good Iteration Review  |  Why Hold an Iteration Review  |  The 3 Scrum Roles and Their Specific Responsibilities  |  The Role of the Scrum Three Artifacts in Agile Development  |  14 Best Scrums in 2022 Agile Project Management Software  |  More 

Kanban Agile Guide:  5 Benefits of Using Kanban (Kanban) Management Method  |  Kanban VS Scrum: How to choose? |  Which scenarios are suitable for the mixed mode of Kanban and Scrum  |  More 

Scaled Agile:  The Value of Scaled Agile and Five Large-scale Agile Frameworks  |  Spotify Model of Scaled Agile  |  LeSS Framework of Scaled Agile Framework  |  SAFe Scaled Agile Framework  |  Scrum@Scale Model  |  Agile Project Portfolio Management  |  OKR and Agile Development  |   More 

Product Management:  How to Build a Qualified Product Roadmap  |  How to Become a Good Product Manager  |  The Importance of Agile Roadmaps and Construction  |  How to Build Simple and Effective Product Requirements Documents  |  Use NPS to Determine Functional Priority  |  Every Product Manager Needs Learn Product Analysis Skills  |  More 

Guess you like

Origin blog.csdn.net/weixin_44280696/article/details/130130871