You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but nothing seems to really improve. Stop doing retrospectives! You should shift your focus form collecting problems and start improving! It is time to take your improvement work to a whole new level!
It is time to create the habits of continuous improvement. It is time to start using Toyota Kata!
Toyota Kata is two behavior patterns, or Kata:s, that is the foundation in Toyota?s continuous improvement work. In this session you will get a practical introduction to Toyota Kata. You will see how a team goes through the two Kata's and improves its way of working.
Presented together with @hakanforss slideshare.net/hkanforss
Toyota kata – Agile saturday x 2014 02-15Håkan Forss
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” – Aristotle
What are the habits, routines, behavior patterns, needed to strive for excellence every day? How do we create a culture of continuous learning and improvement?
Building on the power of habits, Toyota Kata will help you build a culture of continuous learning and improvement, a kaizen culture.
In this session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. You will learn how the Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive towards your vision, your state of awesomeness, in small experiments focused on learning. The Improvement Kata will form the habits of doing small daily experiments focused on learning and improving. The Coaching Kata will form the habits of the leaders of the organization to help the learners learn and improve.
In this session, we will take Toyota Kata out of the manufacturing context and put it into the knowledge work context. You will learn how you can start applying the Improvement Kata and Coaching Kata in a software development context tomorrow.
Time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
The document describes a presentation on sed and awk given by Joshua Thijssen. It begins with biographical information about Joshua, who works as a senior software engineer. It then discusses expanding one's "comfort zone" by learning tools like sed and awk that may be better suited than PHP for certain data manipulation tasks. The remainder of the document outlines why sed and awk are useful and previews the topics to be covered in the presentation, including an introduction to sed.
The red brick cancer Lean Agile Scotland 2013-09-19Håkan Forss
Time is valuable, and when it is gone, it is gone. Are you focusing on flow or just keeping yourself busy? How much has the red brick cancer spread in your processes?
In this session we will talk about time. We will explore the differences between systems with high resource efficiency and systems focused on flow efficiency. We take a look at how to remove the red brick cancer in your processes. You will learn how to understand and improve the end to end flow in your system.
The Busy Bee Paradox Agile Tour Lille 2014Håkan Forss
The document is a collection of slides created by Håkan Forss on various topics including agile/scrum, lean, kanban and flow. Some key points discussed are:
- King.com is a gaming company with over 200 titles played worldwide and hundreds of millions of average users.
- Flow efficiency measures the percentage of value-added time versus total lead time, which is typically only 1-5% in many processes.
- Improving flow involves reducing wait times and waste, such as queues, unnecessary processing, defects and long feedback cycles.
- Focusing only on local optimizations can undermine the system as a whole; a shared view of end-to-end flow is needed
How to improve flow efficiency, remove the red bricks Agile2014Håkan Forss
Do you want to improve end-to-end feature lead-time? It is not a question of working harder. It is a question of first removing the feature wait time, the red bricks.
If you would build an end-to-end timeline for your features using red, yellow and green LEGO bricks. Where:
* Red = Non value adding waiting time
* Yellow = Non value adding activates required due to how work is organized
* Green = Value adding activities of real customer value
How would your feature end-to-end timeline look like? In most cases, you will have less than 20% green and yellow bricks and more the 80% red bricks.
In this session, you will be see how flow efficiency can be drastically improve in two concrete examples from two different domains.
First, you will see how a Swedish Breast Cancer Clinic drastically improved flow efficiency and reduced patient wait time by focusing on removing the red and yellow bricks.
In the second example, you will see how a Product Development Test Organization reduced lead-time and created time for improvements by focusing on improving flow efficiency.
We will take a close look at the three laws that define the performance of all processes:
* Little’s Law
* Law of bottlenecks
* Law of variation
By understanding how the three laws governs the performance of your processes, we can look at ways to improve your flow efficiency.
When time is gone, it is gone. Time to start removing the red and yellow bricks
Toyota Kata – habits for continuous improvements Lean IT Summit 2013Håkan Forss
Toyota Kata – habits for continuous improvements
Description:
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle
What are the habits, or routines, you need to put in place to continuously strive for excellence? How do we create a culture of continuous improvement?
In this session you will learn about continuous improvement routines that help you close the gap between your current condition and you desired future state. You will learn how you can probe through the unknown in small deliberate steps. You will also be introduced to the leadership routines to build a continuous improvement culture. These routines are what we call Toyota Kata.
How we made three very important mental leaps to make the transition to Agile and Lean stick at Ericsson 3G including examples of what we have tried
* From methods & tools to principles & mindset;
* From resource efficiency to flow efficiency;
* From scattered experiences to continuous innovation
Experimentation is King Lean Kanban Central Europe 2015Håkan Forss
The document discusses experimentation and an agile approach at King, a mobile game development company. It provides an overview of King, including its history, games, employees and offices around the world. It then discusses the importance of experimentation, describing the typical process of coming up with an idea, building it, releasing it, measuring results, analyzing feedback, and learning. It provides examples of experiments at King and how they iterate based on results. The document also discusses King's values, recruitment process, training programs, and efforts to create an innovative culture through practices like game jams and autonomy.
Toyota kata – Agile saturday x 2014 02-15Håkan Forss
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” – Aristotle
What are the habits, routines, behavior patterns, needed to strive for excellence every day? How do we create a culture of continuous learning and improvement?
Building on the power of habits, Toyota Kata will help you build a culture of continuous learning and improvement, a kaizen culture.
In this session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. You will learn how the Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive towards your vision, your state of awesomeness, in small experiments focused on learning. The Improvement Kata will form the habits of doing small daily experiments focused on learning and improving. The Coaching Kata will form the habits of the leaders of the organization to help the learners learn and improve.
In this session, we will take Toyota Kata out of the manufacturing context and put it into the knowledge work context. You will learn how you can start applying the Improvement Kata and Coaching Kata in a software development context tomorrow.
Time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
The document describes a presentation on sed and awk given by Joshua Thijssen. It begins with biographical information about Joshua, who works as a senior software engineer. It then discusses expanding one's "comfort zone" by learning tools like sed and awk that may be better suited than PHP for certain data manipulation tasks. The remainder of the document outlines why sed and awk are useful and previews the topics to be covered in the presentation, including an introduction to sed.
The red brick cancer Lean Agile Scotland 2013-09-19Håkan Forss
Time is valuable, and when it is gone, it is gone. Are you focusing on flow or just keeping yourself busy? How much has the red brick cancer spread in your processes?
In this session we will talk about time. We will explore the differences between systems with high resource efficiency and systems focused on flow efficiency. We take a look at how to remove the red brick cancer in your processes. You will learn how to understand and improve the end to end flow in your system.
The Busy Bee Paradox Agile Tour Lille 2014Håkan Forss
The document is a collection of slides created by Håkan Forss on various topics including agile/scrum, lean, kanban and flow. Some key points discussed are:
- King.com is a gaming company with over 200 titles played worldwide and hundreds of millions of average users.
- Flow efficiency measures the percentage of value-added time versus total lead time, which is typically only 1-5% in many processes.
- Improving flow involves reducing wait times and waste, such as queues, unnecessary processing, defects and long feedback cycles.
- Focusing only on local optimizations can undermine the system as a whole; a shared view of end-to-end flow is needed
How to improve flow efficiency, remove the red bricks Agile2014Håkan Forss
Do you want to improve end-to-end feature lead-time? It is not a question of working harder. It is a question of first removing the feature wait time, the red bricks.
If you would build an end-to-end timeline for your features using red, yellow and green LEGO bricks. Where:
* Red = Non value adding waiting time
* Yellow = Non value adding activates required due to how work is organized
* Green = Value adding activities of real customer value
How would your feature end-to-end timeline look like? In most cases, you will have less than 20% green and yellow bricks and more the 80% red bricks.
In this session, you will be see how flow efficiency can be drastically improve in two concrete examples from two different domains.
First, you will see how a Swedish Breast Cancer Clinic drastically improved flow efficiency and reduced patient wait time by focusing on removing the red and yellow bricks.
In the second example, you will see how a Product Development Test Organization reduced lead-time and created time for improvements by focusing on improving flow efficiency.
We will take a close look at the three laws that define the performance of all processes:
* Little’s Law
* Law of bottlenecks
* Law of variation
By understanding how the three laws governs the performance of your processes, we can look at ways to improve your flow efficiency.
When time is gone, it is gone. Time to start removing the red and yellow bricks
Toyota Kata – habits for continuous improvements Lean IT Summit 2013Håkan Forss
Toyota Kata – habits for continuous improvements
Description:
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle
What are the habits, or routines, you need to put in place to continuously strive for excellence? How do we create a culture of continuous improvement?
In this session you will learn about continuous improvement routines that help you close the gap between your current condition and you desired future state. You will learn how you can probe through the unknown in small deliberate steps. You will also be introduced to the leadership routines to build a continuous improvement culture. These routines are what we call Toyota Kata.
How we made three very important mental leaps to make the transition to Agile and Lean stick at Ericsson 3G including examples of what we have tried
* From methods & tools to principles & mindset;
* From resource efficiency to flow efficiency;
* From scattered experiences to continuous innovation
Experimentation is King Lean Kanban Central Europe 2015Håkan Forss
The document discusses experimentation and an agile approach at King, a mobile game development company. It provides an overview of King, including its history, games, employees and offices around the world. It then discusses the importance of experimentation, describing the typical process of coming up with an idea, building it, releasing it, measuring results, analyzing feedback, and learning. It provides examples of experiments at King and how they iterate based on results. The document also discusses King's values, recruitment process, training programs, and efforts to create an innovative culture through practices like game jams and autonomy.
Toyota kata – habits for continuous improvements MIX IT 2014-04-29Håkan Forss
Building on the power of habits, Toyota Kata will help you build a culture of continuous learning and improvement, a kaizen culture.
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle
What are the habits, routines, behavior patterns, needed to strive for excellence every day? How do we create a culture of continuous learning and improvement?
Building on the power of habits, Toyota Kata will help you build a culture of continuous learning and improvement, a kaizen culture.
In this session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. You will learn how the Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive towards your vision, your state of awesomeness, in small experiments focused on learning. The Improvement Kata will form the habits of doing small daily experiments focused on learning and improving. The Coaching Kata will form the habits of the leaders of the organization to help the learners learn and improve.
In this session, we will take Toyota Kata out of the manufacturing context and put it into the knowledge work context. You will learn how you can start applying the Improvement Kata and Coaching Kata in a software development context tomorrow.
Time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
Ideas for now
•How Toyota Kata can become the catalyst for creating a culture of continuous learning and improvement, a kaizen culture.
•How Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization.
•How the Coaching Kata will form the habits of the leaders of the organization to help the learners learn and improve.
•How small daily experiments lower the resistance to change and builds a kaizen culture.
•How to use the great power of habits to build a new culture.
•How to apply the Improvement Kata and Coaching Kata in a software development context
Read more at http://hakanforss.wordpress.com/tag/toyota-kata/
Stop doing Retrospective and Start your Toyota KataHåkan Forss
You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but nothing seems to really improve. Stop doing retrospectives!
You should shift your focus form collecting problems and start improving! It is time to take your improvement work to a whole new level! It is time to create the habits of continuous improvement. It is time to start using Toyota Kata!
Toyota Kata is two behavior patterns, or Kata’s, that is the foundation in Toyota’s continuous improvement work. In this session you will get a practical introduction to Toyota Kata. You will see how a team goes through the two Kata’s and improves its way of working.
Do or do not. There is no try. —Yoda
Kanban Kata - Lean Kanban European Conference Tour 2012Håkan Forss
This document contains slides from a presentation on Kanban and the Improvement Kata. It discusses using daily meetings, improvement experiments, and operations reviews to continuously improve processes according to the Kanban method. The slides cover establishing a target condition to work towards, removing obstacles to workflow, conducting small experiments, and reviewing data regularly to drive incremental improvements. The goal is to develop "muscle memory" for continuous learning and adaptation through established routines.
Toyota kata – habits for continuous improvements by Hakan ForssInstitut Lean France
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle.
What are the habits, or routines, you need to put in place to continuously strive for excellence? How do we create a culture of continuous improvement? In this session you will learn about continuous improvement routines that help you close the gap between your current condition and you desired future state. You will learn how you can probe through the unknown in small deliberate steps. You will also be introduced to the leadership routines to build a continuous improvement culture. These routines are what we call Toyota Kata. Watch the video of the presentation here: http://youtu.be/MT3qgwzj5nY
More Lean IT videos and presentations on: www.lean-it-summit.com
Retrospective on steroids - Toyota KataHåkan Forss
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle
You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but you don't seem to really improve. Let us put your retrospectives on steroids. Start using Toyota Kata!
Building on the power of habits, Toyota Kata will help you build a daily continuous learning and improvement culture, a kaizen culture.
In this session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. You will learn how the Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive towards your state of awesomeness in small experiments focused on learning. The Improvement Kata will form the habits of doing small daily experiments focused on learning and improving. The Coaching Kata will form the habits of the agile leaders for creating a culture of continuous improvement, adaption, and innovation.
In this session, Toyota Kata will be taken out of the manufacturing context and put it into the knowledge work context. You will learn how you can start applying the Improvement Kata and Coaching Kata in a software development context as a compliment or a replacement of the agile retrospective.
Time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
Make strategy happen with Hoshin Kanri and Toyota Kata Agile AustraliaHåkan Forss
The document is a presentation by Håkan Forss on strategy execution. It discusses three parts of strategy execution: the stroke of the pen involving controllable actions, the whirlwind of everyday operational work, and behavioral change. It emphasizes the importance of establishing daily habits through experiments to drive behavioral change and achieve strategic goals. It also stresses the need for alignment across the organization using approaches like Hoshin Kanri to clarify challenges and ensure resources are focused in the same direction.
Toyota Kata - habits for continous learning. Shingo Institue European Confere...Håkan Forss
Aristotle said, “We are what we repeatedly do. Excellence, then, is not an act, but a habit.” Building on the power of habits, Toyota Kata helps build a daily continuous learning and improvement culture – a kaizen culture.
In this session, Håkan Forss will introduce two main kata* of Toyota Kata – improvement kata and coaching kata. You will learn how the improvement kata and coaching kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive toward your state of awesomeness in small experiments focused on learning. The improvement kata will form the habits of doing small daily experiments focused on learning and improving. The coaching kata will form the habits of leaders in an organization to help the learners learn and improve.
It’s time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A kata is something you practice over and over, while striving for perfection. If the kata itself is relatively static, the content of the kata, as we execute it, is modified based on the situation and context in real-time as it happens. A kata is different from a routine in that it contains a continuous self-renewal process.
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” – Aristotle You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but you don’t seem to really improve. Let us put your retrospectives on steroids. Start using Toyota Kata! Building on the power of habits, Toyota Kata will help you build a daily continuous learning and improvement culture, a kaizen culture. In this intense and interactive 90 min session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. We will experience the fundamental behavior patterns at the core of the Toyota Kata methodology: the rapid experimental cycles and the Coaching Dialog. You will gain direct insight into the power of the Improvement Kata and Coaching Kata through repeated personal practice. You will experience how these daily habits or routines will help you to strive towards a state of awesomeness in small experiments focused on learning. Small teams will work together striving to achieve ever higher levels of awesomeness using the Improvement Kata and Coaching Kata, thereby gaining practical hands-on familiarity with Toyota Kata. Learning outcomes: · Provide an introduction to the core routines, mindset, and behavioral practices of Improvement Kata and Coaching Kata. · Allow you to experience the core routines of the of the Improvement Kata and Coaching Kata through interactive, hands-on exercises Who should attend? The target audience are Lean/Agile Coaches, Scrum Masters, managers and anyone interested in continuous learning and improvement methods. Anyone can attend. Prerequisites No prior knowledge needed. If you want to prepare the following two books are highly recommended: Toyota Kata: Managing People for Improvement, Adaptiveness and Superior Results by Mike Rother and Lean Enterprise: How High Performance Organizations Innovate at Scale by Jez Humble, Joanne Molesky, Barry O’Reilly Time to stop collecting problems and start forming new habits of learning and improving! (*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
KATA - Habits for lean learning Agile Australia 2016Håkan Forss
Learn how to build a Lean learning culture at every level of your organisation. In this presentation from the LEGO enthusiast and Agile Coach at King Hakan Forss, you will discover how the Improvement Kata and Coaching Kata can form the foundational habits of a Lean learning organisation. You will be introduced to two core habits and how they will help you to create an organisation of learners that will improve your business.
From Scooter to Race bike - A Toyota Kata story
This is a story of a teams Improvement Kata journey. You will see how they transitioned from a scooter to a race bike.
This presentation was given as part of the KataSummit 2015 Software Practitioners Panel in Fort Lauderdale 2015-02-19
Toyota kata in knowledge work - European Lean Educator Conference 2014Håkan Forss
* What are the habits, routines, behavior patterns, needed to strive for excellence every day?
* How do we create a culture of continuous learning and improvement?
* The Improvement KATA and the Coaching KATA
* The KATA in knowledge work context
* How to start applying the Improvement KATA and Coaching KATA tomorrow
Make strategy happen with hoshin kanri and toyota kata lean agile brighton 20...Håkan Forss
Lean and Agile software development can help your organization deliver early and often, but that is not sufficient. Without clear and transparent alignment on a strategy, the organization might still end up just keeping itself busy and not achieving the desired results.
Making your strategy happen have two major components that lives in symbiosis; strategy alignment and strategy execution.
Aligning on the right strategy can be a challenge in today’s complex world. Hoshin Kanri is an approach to meeting this challenge by drawing for the collective brain trust in your organization.
Organizations also need to become laboratories, in which they are constantly running experiments, generating learning, and applying that learning to continually progress towards their strategy.
In this session you will learn how to create this symbiosis of strategy alignment and strategy execution using Hoshin Kanri and Toyota Kata as one system.
The red brick cancer ACE! Conf 2013-04-16Håkan Forss
We will explore the differences between systems with high resource efficiency and systems focused on flow efficiency. You will learn how to understand and improve the end to end flow in your system.
Natalie MacLees' presentation on Progressively Enhancing WordPress themes from WordCamp Las Vegas 2011. Covers how to implement HTML5, CSS3, ARIA, SVG, and Responsive Design without breaking your theme for anybody.
The document discusses caring for others and provides tips for designers on caring for clients and projects. It suggests getting the brief and starting work (step 1), designing and building the project (step 2), and getting ready to complete it (step 3). It warns that projects can go well or badly depending on technical limitations, client demands, and how well the final build matches the original design. It advises designers to do quality work and avoid cutting corners.
Don’t we all think that we get more done if we stay busy? We feel good and efficient. We may even get a pat on the back or even a promotion.
But is this good for the company? Is it good for our customers? Are we really optimizing for the whole or are we just keeping ourselves busy?
Learn how to shift your focus from keeping people and equipment busy to having work flowing to your customers without unwanted waiting time and how that new focus will affect your meetings, process management, and metrics.
Improve productivity, focus on flow - Remove the RED bricks Håkan Forss
Do you want to improve end-to-end feature lead-time? It is not a question of working harder. It is a question of first removing the feature wait time, the red bricks.
If you would build an end-to-end timeline for your features using red, yellow and green LEGO bricks. Where:
• Red = Non value adding waiting time
• Yellow = Non value adding activates required due to how work is organized
• Green = Value adding activities of real customer value
How would your feature end-to-end timeline look like? In most cases, you will have less than 20% green and yellow bricks and more the 80% red bricks.
In this session, you will be learn how flow efficiency can be drastically improved in a concrete example.
You will see how a Swedish Breast Cancer Clinic drastically improved flow efficiency and reduced patient wait time by focusing on removing the red and yellow bricks.
We will take a close look at the three laws that define the performance of all processes:
• Little’s Law
• Law of bottlenecks
• Law of variation
By understanding how the three laws governs the performance of your processes, we can look at ways to improve your flow efficiency.
When time is gone, it is gone. Time to start removing the red and yellow bricks
Chitradip Mukherjee is a front end developer with over 6 years of experience developing websites using HTML, CSS, JavaScript, jQuery, and WordPress. He has extensive experience designing and developing responsive websites for clients in various industries. Some of the notable projects he has worked on include websites for marketing agencies, consulting firms, and property management companies. He is proficient in Photoshop, Dreamweaver and content management systems like WordPress.
Microsoft Teams, OneDrive and Office - the ideal threesome for co-authoring d...Sasja Beerendonk
Use Microsoft Office 365 tools and features to effectively collaborate on files together. Using Teams, OneDrive and MS Office applications Word, Excel and PowerPoint. Whether on your desktop, in a browser or on mobile devices, you never have email and version chaos again when embracing this new way of working in the co-authoring documents productivity scenario.
Toyota kata – habits for continuous improvements MIX IT 2014-04-29Håkan Forss
Building on the power of habits, Toyota Kata will help you build a culture of continuous learning and improvement, a kaizen culture.
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle
What are the habits, routines, behavior patterns, needed to strive for excellence every day? How do we create a culture of continuous learning and improvement?
Building on the power of habits, Toyota Kata will help you build a culture of continuous learning and improvement, a kaizen culture.
In this session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. You will learn how the Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive towards your vision, your state of awesomeness, in small experiments focused on learning. The Improvement Kata will form the habits of doing small daily experiments focused on learning and improving. The Coaching Kata will form the habits of the leaders of the organization to help the learners learn and improve.
In this session, we will take Toyota Kata out of the manufacturing context and put it into the knowledge work context. You will learn how you can start applying the Improvement Kata and Coaching Kata in a software development context tomorrow.
Time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
Ideas for now
•How Toyota Kata can become the catalyst for creating a culture of continuous learning and improvement, a kaizen culture.
•How Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization.
•How the Coaching Kata will form the habits of the leaders of the organization to help the learners learn and improve.
•How small daily experiments lower the resistance to change and builds a kaizen culture.
•How to use the great power of habits to build a new culture.
•How to apply the Improvement Kata and Coaching Kata in a software development context
Read more at http://hakanforss.wordpress.com/tag/toyota-kata/
Stop doing Retrospective and Start your Toyota KataHåkan Forss
You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but nothing seems to really improve. Stop doing retrospectives!
You should shift your focus form collecting problems and start improving! It is time to take your improvement work to a whole new level! It is time to create the habits of continuous improvement. It is time to start using Toyota Kata!
Toyota Kata is two behavior patterns, or Kata’s, that is the foundation in Toyota’s continuous improvement work. In this session you will get a practical introduction to Toyota Kata. You will see how a team goes through the two Kata’s and improves its way of working.
Do or do not. There is no try. —Yoda
Kanban Kata - Lean Kanban European Conference Tour 2012Håkan Forss
This document contains slides from a presentation on Kanban and the Improvement Kata. It discusses using daily meetings, improvement experiments, and operations reviews to continuously improve processes according to the Kanban method. The slides cover establishing a target condition to work towards, removing obstacles to workflow, conducting small experiments, and reviewing data regularly to drive incremental improvements. The goal is to develop "muscle memory" for continuous learning and adaptation through established routines.
Toyota kata – habits for continuous improvements by Hakan ForssInstitut Lean France
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle.
What are the habits, or routines, you need to put in place to continuously strive for excellence? How do we create a culture of continuous improvement? In this session you will learn about continuous improvement routines that help you close the gap between your current condition and you desired future state. You will learn how you can probe through the unknown in small deliberate steps. You will also be introduced to the leadership routines to build a continuous improvement culture. These routines are what we call Toyota Kata. Watch the video of the presentation here: http://youtu.be/MT3qgwzj5nY
More Lean IT videos and presentations on: www.lean-it-summit.com
Retrospective on steroids - Toyota KataHåkan Forss
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle
You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but you don't seem to really improve. Let us put your retrospectives on steroids. Start using Toyota Kata!
Building on the power of habits, Toyota Kata will help you build a daily continuous learning and improvement culture, a kaizen culture.
In this session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. You will learn how the Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive towards your state of awesomeness in small experiments focused on learning. The Improvement Kata will form the habits of doing small daily experiments focused on learning and improving. The Coaching Kata will form the habits of the agile leaders for creating a culture of continuous improvement, adaption, and innovation.
In this session, Toyota Kata will be taken out of the manufacturing context and put it into the knowledge work context. You will learn how you can start applying the Improvement Kata and Coaching Kata in a software development context as a compliment or a replacement of the agile retrospective.
Time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
Make strategy happen with Hoshin Kanri and Toyota Kata Agile AustraliaHåkan Forss
The document is a presentation by Håkan Forss on strategy execution. It discusses three parts of strategy execution: the stroke of the pen involving controllable actions, the whirlwind of everyday operational work, and behavioral change. It emphasizes the importance of establishing daily habits through experiments to drive behavioral change and achieve strategic goals. It also stresses the need for alignment across the organization using approaches like Hoshin Kanri to clarify challenges and ensure resources are focused in the same direction.
Toyota Kata - habits for continous learning. Shingo Institue European Confere...Håkan Forss
Aristotle said, “We are what we repeatedly do. Excellence, then, is not an act, but a habit.” Building on the power of habits, Toyota Kata helps build a daily continuous learning and improvement culture – a kaizen culture.
In this session, Håkan Forss will introduce two main kata* of Toyota Kata – improvement kata and coaching kata. You will learn how the improvement kata and coaching kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive toward your state of awesomeness in small experiments focused on learning. The improvement kata will form the habits of doing small daily experiments focused on learning and improving. The coaching kata will form the habits of leaders in an organization to help the learners learn and improve.
It’s time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A kata is something you practice over and over, while striving for perfection. If the kata itself is relatively static, the content of the kata, as we execute it, is modified based on the situation and context in real-time as it happens. A kata is different from a routine in that it contains a continuous self-renewal process.
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” – Aristotle You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but you don’t seem to really improve. Let us put your retrospectives on steroids. Start using Toyota Kata! Building on the power of habits, Toyota Kata will help you build a daily continuous learning and improvement culture, a kaizen culture. In this intense and interactive 90 min session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. We will experience the fundamental behavior patterns at the core of the Toyota Kata methodology: the rapid experimental cycles and the Coaching Dialog. You will gain direct insight into the power of the Improvement Kata and Coaching Kata through repeated personal practice. You will experience how these daily habits or routines will help you to strive towards a state of awesomeness in small experiments focused on learning. Small teams will work together striving to achieve ever higher levels of awesomeness using the Improvement Kata and Coaching Kata, thereby gaining practical hands-on familiarity with Toyota Kata. Learning outcomes: · Provide an introduction to the core routines, mindset, and behavioral practices of Improvement Kata and Coaching Kata. · Allow you to experience the core routines of the of the Improvement Kata and Coaching Kata through interactive, hands-on exercises Who should attend? The target audience are Lean/Agile Coaches, Scrum Masters, managers and anyone interested in continuous learning and improvement methods. Anyone can attend. Prerequisites No prior knowledge needed. If you want to prepare the following two books are highly recommended: Toyota Kata: Managing People for Improvement, Adaptiveness and Superior Results by Mike Rother and Lean Enterprise: How High Performance Organizations Innovate at Scale by Jez Humble, Joanne Molesky, Barry O’Reilly Time to stop collecting problems and start forming new habits of learning and improving! (*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
KATA - Habits for lean learning Agile Australia 2016Håkan Forss
Learn how to build a Lean learning culture at every level of your organisation. In this presentation from the LEGO enthusiast and Agile Coach at King Hakan Forss, you will discover how the Improvement Kata and Coaching Kata can form the foundational habits of a Lean learning organisation. You will be introduced to two core habits and how they will help you to create an organisation of learners that will improve your business.
From Scooter to Race bike - A Toyota Kata story
This is a story of a teams Improvement Kata journey. You will see how they transitioned from a scooter to a race bike.
This presentation was given as part of the KataSummit 2015 Software Practitioners Panel in Fort Lauderdale 2015-02-19
Toyota kata in knowledge work - European Lean Educator Conference 2014Håkan Forss
* What are the habits, routines, behavior patterns, needed to strive for excellence every day?
* How do we create a culture of continuous learning and improvement?
* The Improvement KATA and the Coaching KATA
* The KATA in knowledge work context
* How to start applying the Improvement KATA and Coaching KATA tomorrow
Make strategy happen with hoshin kanri and toyota kata lean agile brighton 20...Håkan Forss
Lean and Agile software development can help your organization deliver early and often, but that is not sufficient. Without clear and transparent alignment on a strategy, the organization might still end up just keeping itself busy and not achieving the desired results.
Making your strategy happen have two major components that lives in symbiosis; strategy alignment and strategy execution.
Aligning on the right strategy can be a challenge in today’s complex world. Hoshin Kanri is an approach to meeting this challenge by drawing for the collective brain trust in your organization.
Organizations also need to become laboratories, in which they are constantly running experiments, generating learning, and applying that learning to continually progress towards their strategy.
In this session you will learn how to create this symbiosis of strategy alignment and strategy execution using Hoshin Kanri and Toyota Kata as one system.
The red brick cancer ACE! Conf 2013-04-16Håkan Forss
We will explore the differences between systems with high resource efficiency and systems focused on flow efficiency. You will learn how to understand and improve the end to end flow in your system.
Natalie MacLees' presentation on Progressively Enhancing WordPress themes from WordCamp Las Vegas 2011. Covers how to implement HTML5, CSS3, ARIA, SVG, and Responsive Design without breaking your theme for anybody.
The document discusses caring for others and provides tips for designers on caring for clients and projects. It suggests getting the brief and starting work (step 1), designing and building the project (step 2), and getting ready to complete it (step 3). It warns that projects can go well or badly depending on technical limitations, client demands, and how well the final build matches the original design. It advises designers to do quality work and avoid cutting corners.
Don’t we all think that we get more done if we stay busy? We feel good and efficient. We may even get a pat on the back or even a promotion.
But is this good for the company? Is it good for our customers? Are we really optimizing for the whole or are we just keeping ourselves busy?
Learn how to shift your focus from keeping people and equipment busy to having work flowing to your customers without unwanted waiting time and how that new focus will affect your meetings, process management, and metrics.
Improve productivity, focus on flow - Remove the RED bricks Håkan Forss
Do you want to improve end-to-end feature lead-time? It is not a question of working harder. It is a question of first removing the feature wait time, the red bricks.
If you would build an end-to-end timeline for your features using red, yellow and green LEGO bricks. Where:
• Red = Non value adding waiting time
• Yellow = Non value adding activates required due to how work is organized
• Green = Value adding activities of real customer value
How would your feature end-to-end timeline look like? In most cases, you will have less than 20% green and yellow bricks and more the 80% red bricks.
In this session, you will be learn how flow efficiency can be drastically improved in a concrete example.
You will see how a Swedish Breast Cancer Clinic drastically improved flow efficiency and reduced patient wait time by focusing on removing the red and yellow bricks.
We will take a close look at the three laws that define the performance of all processes:
• Little’s Law
• Law of bottlenecks
• Law of variation
By understanding how the three laws governs the performance of your processes, we can look at ways to improve your flow efficiency.
When time is gone, it is gone. Time to start removing the red and yellow bricks
Chitradip Mukherjee is a front end developer with over 6 years of experience developing websites using HTML, CSS, JavaScript, jQuery, and WordPress. He has extensive experience designing and developing responsive websites for clients in various industries. Some of the notable projects he has worked on include websites for marketing agencies, consulting firms, and property management companies. He is proficient in Photoshop, Dreamweaver and content management systems like WordPress.
Microsoft Teams, OneDrive and Office - the ideal threesome for co-authoring d...Sasja Beerendonk
Use Microsoft Office 365 tools and features to effectively collaborate on files together. Using Teams, OneDrive and MS Office applications Word, Excel and PowerPoint. Whether on your desktop, in a browser or on mobile devices, you never have email and version chaos again when embracing this new way of working in the co-authoring documents productivity scenario.
Similar to Toyota Kata presented at DevoxxUK 2013 (20)
Walmart Business+ and Spark Good for Nonprofits.pdfTechSoup
"Learn about all the ways Walmart supports nonprofit organizations.
You will hear from Liz Willett, the Head of Nonprofits, and hear about what Walmart is doing to help nonprofits, including Walmart Business and Spark Good. Walmart Business+ is a new offer for nonprofits that offers discounts and also streamlines nonprofits order and expense tracking, saving time and money.
The webinar may also give some examples on how nonprofits can best leverage Walmart Business+.
The event will cover the following::
Walmart Business + (https://business.walmart.com/plus) is a new shopping experience for nonprofits, schools, and local business customers that connects an exclusive online shopping experience to stores. Benefits include free delivery and shipping, a 'Spend Analytics” feature, special discounts, deals and tax-exempt shopping.
Special TechSoup offer for a free 180 days membership, and up to $150 in discounts on eligible orders.
Spark Good (walmart.com/sparkgood) is a charitable platform that enables nonprofits to receive donations directly from customers and associates.
Answers about how you can do more with Walmart!"
LAND USE LAND COVER AND NDVI OF MIRZAPUR DISTRICT, UPRAHUL
This Dissertation explores the particular circumstances of Mirzapur, a region located in the
core of India. Mirzapur, with its varied terrains and abundant biodiversity, offers an optimal
environment for investigating the changes in vegetation cover dynamics. Our study utilizes
advanced technologies such as GIS (Geographic Information Systems) and Remote sensing to
analyze the transformations that have taken place over the course of a decade.
The complex relationship between human activities and the environment has been the focus
of extensive research and worry. As the global community grapples with swift urbanization,
population expansion, and economic progress, the effects on natural ecosystems are becoming
more evident. A crucial element of this impact is the alteration of vegetation cover, which plays a
significant role in maintaining the ecological equilibrium of our planet.Land serves as the foundation for all human activities and provides the necessary materials for
these activities. As the most crucial natural resource, its utilization by humans results in different
'Land uses,' which are determined by both human activities and the physical characteristics of the
land.
The utilization of land is impacted by human needs and environmental factors. In countries
like India, rapid population growth and the emphasis on extensive resource exploitation can lead
to significant land degradation, adversely affecting the region's land cover.
Therefore, human intervention has significantly influenced land use patterns over many
centuries, evolving its structure over time and space. In the present era, these changes have
accelerated due to factors such as agriculture and urbanization. Information regarding land use and
cover is essential for various planning and management tasks related to the Earth's surface,
providing crucial environmental data for scientific, resource management, policy purposes, and
diverse human activities.
Accurate understanding of land use and cover is imperative for the development planning
of any area. Consequently, a wide range of professionals, including earth system scientists, land
and water managers, and urban planners, are interested in obtaining data on land use and cover
changes, conversion trends, and other related patterns. The spatial dimensions of land use and
cover support policymakers and scientists in making well-informed decisions, as alterations in
these patterns indicate shifts in economic and social conditions. Monitoring such changes with the
help of Advanced technologies like Remote Sensing and Geographic Information Systems is
crucial for coordinated efforts across different administrative levels. Advanced technologies like
Remote Sensing and Geographic Information Systems
9
Changes in vegetation cover refer to variations in the distribution, composition, and overall
structure of plant communities across different temporal and spatial scales. These changes can
occur natural.
Gender and Mental Health - Counselling and Family Therapy Applications and In...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
This document provides an overview of wound healing, its functions, stages, mechanisms, factors affecting it, and complications.
A wound is a break in the integrity of the skin or tissues, which may be associated with disruption of the structure and function.
Healing is the body’s response to injury in an attempt to restore normal structure and functions.
Healing can occur in two ways: Regeneration and Repair
There are 4 phases of wound healing: hemostasis, inflammation, proliferation, and remodeling. This document also describes the mechanism of wound healing. Factors that affect healing include infection, uncontrolled diabetes, poor nutrition, age, anemia, the presence of foreign bodies, etc.
Complications of wound healing like infection, hyperpigmentation of scar, contractures, and keloid formation.
Leveraging Generative AI to Drive Nonprofit InnovationTechSoup
In this webinar, participants learned how to utilize Generative AI to streamline operations and elevate member engagement. Amazon Web Service experts provided a customer specific use cases and dived into low/no-code tools that are quick and easy to deploy through Amazon Web Service (AWS.)
Chapter wise All Notes of First year Basic Civil Engineering.pptxDenish Jangid
Chapter wise All Notes of First year Basic Civil Engineering
Syllabus
Chapter-1
Introduction to objective, scope and outcome the subject
Chapter 2
Introduction: Scope and Specialization of Civil Engineering, Role of civil Engineer in Society, Impact of infrastructural development on economy of country.
Chapter 3
Surveying: Object Principles & Types of Surveying; Site Plans, Plans & Maps; Scales & Unit of different Measurements.
Linear Measurements: Instruments used. Linear Measurement by Tape, Ranging out Survey Lines and overcoming Obstructions; Measurements on sloping ground; Tape corrections, conventional symbols. Angular Measurements: Instruments used; Introduction to Compass Surveying, Bearings and Longitude & Latitude of a Line, Introduction to total station.
Levelling: Instrument used Object of levelling, Methods of levelling in brief, and Contour maps.
Chapter 4
Buildings: Selection of site for Buildings, Layout of Building Plan, Types of buildings, Plinth area, carpet area, floor space index, Introduction to building byelaws, concept of sun light & ventilation. Components of Buildings & their functions, Basic concept of R.C.C., Introduction to types of foundation
Chapter 5
Transportation: Introduction to Transportation Engineering; Traffic and Road Safety: Types and Characteristics of Various Modes of Transportation; Various Road Traffic Signs, Causes of Accidents and Road Safety Measures.
Chapter 6
Environmental Engineering: Environmental Pollution, Environmental Acts and Regulations, Functional Concepts of Ecology, Basics of Species, Biodiversity, Ecosystem, Hydrological Cycle; Chemical Cycles: Carbon, Nitrogen & Phosphorus; Energy Flow in Ecosystems.
Water Pollution: Water Quality standards, Introduction to Treatment & Disposal of Waste Water. Reuse and Saving of Water, Rain Water Harvesting. Solid Waste Management: Classification of Solid Waste, Collection, Transportation and Disposal of Solid. Recycling of Solid Waste: Energy Recovery, Sanitary Landfill, On-Site Sanitation. Air & Noise Pollution: Primary and Secondary air pollutants, Harmful effects of Air Pollution, Control of Air Pollution. . Noise Pollution Harmful Effects of noise pollution, control of noise pollution, Global warming & Climate Change, Ozone depletion, Greenhouse effect
Text Books:
1. Palancharmy, Basic Civil Engineering, McGraw Hill publishers.
2. Satheesh Gopi, Basic Civil Engineering, Pearson Publishers.
3. Ketki Rangwala Dalal, Essentials of Civil Engineering, Charotar Publishing House.
4. BCP, Surveying volume 1
1. Your
Title here
Håkan Forss Mattias Karlsson
Lean/Agile Coach Java Champion,
Your Logo Here Agile Coach
@hakanforss @matkar
Speaker Name
Your title
Company Name
@twitter
2. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
3. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
4. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
5. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
6. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
7. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
8. Daily work
Improving
Delivering value
the work
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
9. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
10. What is a Kata?
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
11. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
12. Create ”muscle memory”
for continuous improvements
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
13. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
14. Vision
Challenge
Target
Target
Target
Target Condition
Condition
Condition
Condition
Current
Condition
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
16. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
17. The Vision
• Process focused
• Not outcome focused
• Not a business or company vision
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
18. Toyota’s Vision for Its
Production Operations
• Zero defects
• 100 percent value added
• One-piece flow, in sequence, on demand
• Security for people
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
20. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
21. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
22. What to collect
• Data and facts, not gut feel
• Process metrics
• Outcome metrics
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
24. Our next target condition is…
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
25. What is a Target Condition
• Starting with the end in mind
• Defining the destination
• Not the steps to get there
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
26. Beyond the knowledge threshold
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
27. Put a square peg in a round hole
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
28. Setting a target condition
• Hypothesis on the journey towards the next
Challenge and Vision
• Based on your business strategy and model for
process improvement
• Follow the Goldilocks rule
– Not too hard, Not too easy, Just Right
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
29. Challenge
Target
Target Condition
Target Condition
Target Condition
Condition
Current
Condition
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
30. Challenge
Current
Condition
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
31. Target Condition examples
• All work visible
• Lead time 40 days (from 80 days)
• Work-in-process 15 (from 20)
• Deploy to production every 2 weeks
• Specification by Example is used for 80% of the features
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
36. Hypothesis
Learning
Observation Prediction
Experiment
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
37. Expect at least 50% of the experiments
will not give the expected result
This is when we REALLY learn!
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
38. Target
Condition
Current
Condition
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
39. Target
Condition
A P
Current C D
Condition
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
40. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
41. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
42. Vision
• Zero defects, in production
• 100 percent value added
• Highest value first, on demand
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
43. Challenge
• No recurring defects
• Same environment in all stages
• Concept to Cash in weeks rather than months
• Continuous delivery. In days rather than weeks
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
44. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
45. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
47. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
48. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
49. Lead time Throughput
Frontend Half the lead time 12th April
50. Lead time Throughput
Frontend Half the lead time 12th April
MPNet Development Process
Release Release
Create request Business proposal Approvals Technical design Development Test Release
planning management
Market & BD
Heat ticket BRD Approval UAT Sign-off
3 days 7 days
5 min 5h 1h 2h 5 min
5 days
4 days
PMO
Approval 7 days
1 day
6 min
1 day
Functional and
Release planing Test Case Status report
FDD Guesstimateing systems test Validation
FA
7 days 2 h (8 h) 4h 5 min
10 h 2h 12 h(60 h)
7 days
2 days
Developer
Development,
1 day 7 days documentation Packeting
Guesstimateing TDD 1 day
and test Clearrity ticket
4h 4h
13 h 1,5 h
15 days
manager
Release
Release to test
env. 4 days
1 h (4 h)
GTS
Send Approval Release to prod.
5 min 2 h (9 h)
1 day
Management
Approval
20 min
Lead time
S = 12 days
M = 20 days
L = 40 days
Escaped defects
Level 1: 1
Level 2: 2
Level 3: 0
Customer satisfaction
NPS: 20%
51. Lead time Throughput
Frontend Half the lead time 12th April
MPNet Development Process MPNet Development Process
Release Release Release Release
Create request Business proposal Approvals Technical design Development Test Release Create request Business proposal Approvals Technical design Development Test Release
planning management planning management
Market & BD
Market & BD
Heat ticket BRD Approval UAT Sign-off Heat ticket BRD Approval UAT Sign-off
3 days 7 days 3 days 7 days
5 min 5h 1h 2h 5 min 5 min 5h 1h 2h 5 min
5 days 5 days
4 days 4 days
PMO
PMO
Approval 7 days Approval 7 days
1 day 1 day
6 min 6 min
1 day 1 day
Functional and Functional and
Release planing Test Case Status report Release planing Test Case Status report
FDD Guesstimateing systems test Validation FDD Guesstimateing systems test Validation
FA
FA
7 days 2 h (8 h) 4h 5 min 7 days 2 h (8 h) 4h 5 min
10 h 2h 12 h(60 h) 10 h 2h 12 h(60 h)
7 days 7 days
2 days 2 days
Developer
Developer
Development, Development,
1 day 7 days documentation Packeting 1 day 7 days documentation Packeting
Guesstimateing TDD 1 day Guesstimateing TDD 1 day
and test Clearrity ticket and test Clearrity ticket
4h 4h 4h 4h
13 h 1,5 h 13 h 1,5 h
15 days 15 days
manager
manager
Release
Release
Release to test Release to test
env. 4 days env. 4 days
1 h (4 h) 1 h (4 h)
GTS
GTS
Send Approval Release to prod. Send Approval Release to prod.
5 min 2 h (9 h) 5 min 2 h (9 h)
1 day 1 day
Management
Management
Approval Approval
20 min 20 min
Lead time Lead time
S = 12 days S = 12 days
M = 20 days M = 20 days
L = 40 days L = 40 days
Escaped defects Escaped defects
Level 1: 1 Level 1: 1
Level 2: 2 Level 2: 2
Level 3: 0 Level 3: 0
Customer satisfaction Customer satisfaction
NPS: 20% NPS: 20%
52. Lead time Throughput
Frontend Half the lead time 12th April
MPNet Development Process MPNet Development Process
Release Release Release Release
Create request Business proposal Approvals Technical design Development Test Release Create request Business proposal Approvals Technical design Development Test Release
planning management planning management
Market & BD
Market & BD
Heat ticket BRD Approval UAT Sign-off Heat ticket BRD Approval UAT Sign-off
3 days 7 days 3 days 7 days
5 min 5h 1h 2h 5 min 5 min 5h 1h 2h 5 min
5 days 5 days
4 days 4 days
PMO
PMO
Approval 7 days Approval 7 days
1 day 1 day
6 min 6 min
1 day 1 day
Functional and Functional and
Release planing Test Case Status report Release planing Test Case Status report
FDD Guesstimateing systems test Validation FDD Guesstimateing systems test Validation
FA
FA
7 days 2 h (8 h) 4h 5 min 7 days 2 h (8 h) 4h 5 min
10 h 2h 12 h(60 h) 10 h 2h 12 h(60 h)
7 days 7 days
2 days 2 days
Developer
Developer
Development, Development,
1 day 7 days documentation Packeting 1 day 7 days documentation Packeting
Guesstimateing TDD 1 day Guesstimateing TDD 1 day
and test Clearrity ticket and test Clearrity ticket
4h 4h 4h 4h
13 h 1,5 h 13 h 1,5 h
15 days 15 days
manager
manager
Release
Release
Release to test Release to test
env. 4 days env. 4 days
1 h (4 h) 1 h (4 h)
GTS
GTS
Send Approval Release to prod. Send Approval Release to prod.
5 min 2 h (9 h) 5 min 2 h (9 h)
1 day 1 day
Management
Management
Approval Approval
20 min 20 min
Lead time Lead time
S = 12 days S = 8 days
M = 20 days M = 16 days
L = 40 days L = 36 days
Escaped defects Escaped defects
Level 1: 1 Level 1: 1
Level 2: 2 Level 2: 2
Level 3: 0 Level 3: 0
Customer satisfaction Customer satisfaction
NPS: 20% NPS: 20%
53. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
54. Lead time Throughput
Frontend Half the lead time 12th April
MPNet Development Process MPNet Development Process
Release Release Release Release
Create request Business proposal Approvals Technical design Development Test Release Create request Business proposal Approvals Technical design Development Test Release
planning management planning management
Market & BD
Market & BD
Heat ticket BRD Approval UAT Sign-off Heat ticket BRD Approval UAT Sign-off
3 days 7 days 3 days 7 days
5 min 5h 1h 2h 5 min 5 min 5h 1h 2h 5 min
5 days 5 days
4 days 4 days
PMO
PMO
Approval 7 days Approval 7 days
1 day 1 day
6 min 6 min
1 day 1 day
Functional and Functional and
Release planing Test Case Status report Release planing Test Case Status report
FDD Guesstimateing systems test Validation FDD Guesstimateing systems test Validation
FA
FA
7 days 2 h (8 h) 4h 5 min 7 days 2 h (8 h) 4h 5 min
10 h 2h 12 h(60 h) 10 h 2h 12 h(60 h)
7 days 7 days
2 days 2 days
Developer
Developer
Development, Development,
1 day 7 days documentation Packeting 1 day 7 days documentation Packeting
Guesstimateing TDD 1 day Guesstimateing TDD 1 day
and test Clearrity ticket and test Clearrity ticket
4h 4h 4h 4h
13 h 1,5 h 13 h 1,5 h
15 days 15 days
manager
manager
Release
Release
Release to test Release to test
env. 4 days env. 4 days
1 h (4 h) 1 h (4 h)
GTS
GTS
Send Approval Release to prod. Send Approval Release to prod.
5 min 2 h (9 h) 5 min 2 h (9 h)
1 day 1 day
Management
Management
Approval Approval
20 min 20 min
Lead time Lead time
S = 12 days S = 8 days
M = 20 days M = 16 days
L = 40 days L = 36 days
Escaped defects Escaped defects
Level 1: 1 Level 1: 1
Level 2: 2 Level 2: 2
Level 3: 0 Level 3: 0
Customer satisfaction Customer satisfaction
NPS: 20% NPS: 20%
55. 26th March
Lead time
Frontend
Document the setup
process
56. 26th March
Lead time
Frontend
Document the setup We expect to
process understand the
process better
57. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
Editor's Notes
Improvement suggestions are pointing in different directions
Your run at least one process improvement experiment a week per teamWhen one experiment is done you start on the next
Kanske är det dags att prova ett alternativ till retrospektiv?Toyota Kata, från boken med samma namn innehåller just ett sådant alternativToyota Kata består av två beteende mönster eller två sk. Kator
Kata(型 or 形, literally: "form"?) is a Japanese word describing detailed choreographed patterns of movements practised either solo or in pairs.