Skip to main content

Learning Jidoka from a production line

When you adopt an agile methodology, you first try to apply its recommendations and often you will prefer to make your own dish with these good practices.
After a few weeks of practice, you won't get the expected result that the agile guru has predicated you should. Most of the time, you will be told to apply the methodology you choose without changing a thing.

The Shu Ha Ri way coming from Aikido is often the concept which is proposed for learning an agile method:
  • Shu: first phase, concentrate on all the recommendations and practices,
  • Ha: second step, now you practice the methodology correctly and start to understand the underlying principles,
  • Ri: you have sufficient experience to make your own decision and adapt the methodology to your specific context.
You will also learn, the agile world has not suddenly erupted from the clever minds which produced its manifesto. Instead, these efficient practices have evolved over a century. Toyoda, Taiichi Ōno, Edwards Deming will be the names you will find on your trip back to further discover the root to agile.
Many of these good practices have been promoted in the Toyota company and finally studied and summarised by American researchers in a set of principles named the Toyota Production System (TPS) and the more generic Lean manufacturing.

Among these principles the Jidoka focus on developing the quality in the machine (working station), making the problem visible and separates workers from machines through mechanisms that detect production abnormalities. Two of these principles are Andon and In station quality.
  • Andon: notify management, maintenance system where the centrepiece is a signboard incorporating signal lights to indicate which workstation has the problem.
  • In Station quality: the production system must evaluate the quality of its own result.
Now watch the following video and record the measurement, quality system, colored lights and more.



Like me, you have probably been astonished to see where the USB sticks are produced. Now, step back and understand the quality tools and principles which are used here on a production line.

A production system differs from a product one, regarding the number of times, the same result is produced. Software development as a product development, produces only one time the same package and the same functionality. Consequently, Jidoka will be implemented differently with defect detection of code compilation, of functionnal tests, of feature integration, etc. Because each new product feature make the overall result different, at least the non-regression detection is the primary focus, together with a maintable build system. Also, because each part of the production must have its built in quality, a systematic unit test creation with or prior to coding the new function, is a good pratice too.

If you have seen something else in the video, that is around Toyota culture, please tell me and draw the analogy with your agile world.

Sources :
Agilemanifesto : Principles behind the Agile Manifesto
Wikipedia : Shuhari
Wikipedia : Autonomation
Wikipedia: Toyota Production System
Wikipedia : Toyoda family tree
Wikipedia : Taiichi Ohno
Wikipedia : W. Edwards Deming
Wikipedia : Toyota Production System
Wikipedia : Andon (manufacturing)
Engadget : See USB flash drives manufactured in this shocking behind-the-scenes video
Infoq : InfoQ: Second Generation Lean Product Development: From Cargo Cult to Science
Informit: The History of Lean Software Development

Comments

Popular posts from this blog

Learning about Data Science?

This is the end of a beautiful summer, and also one of the warmer recorded in France. I’m continuing my journey in the product management world and today I’m living in the product marketing one too.
I will blog about this later.

During this first half of this year, I read several articles on big data and started to understand how important the data science discipline is. Being able to define a direction/goal to search, collecting the proper data, then using a collection of techniques to extract something others can’t see - it sounds like magic.

Also, when I listened to the Udacity Linear Disgression podcast episode “Hunting the Higgs”, I understood people with these skills can be better at solving a problem than the domain experts themselves. Katie Malone explained that in a competition to solve a particle physics problem, the best results came from machine learning people.

Then I read the article about Zenefit on the vision mobile website:
“Zenefits is an insurance company that offer…

Didn't register yet to the European Agile event 29-31 August in Paris?

I tell you, I’m not an expert in agile, just someone who found solution to my professional problems using agile methodologies. If you are convinced too and want to move further, please join us at the end of august, for a lot of open discussions and fun.

Things are moving forward in the ALE 2016 organisation. Already, a great diversity of people answer to our call as shown below, but we need more.
Yes the ALE 2016 will be great as it has always been since 2011 in Berlin. For those who do not know about the yearly ALE event, please find below a few tips.

What is it? 
If you do not know yet about the Agile Lean Europe event, here a few tips.
ALE is a event for practitioners, meaning people who already practice agile methodologies like developers, modern CEO, teachers, leaders, etc. Sharing ideas and solving problems are the ALE mains goals: people can propose topics where they share their experience, other can ask to solve a problem the can’t alone The event formats helps the participant…

New personal goals for next years

Happy new year 2015.

After 10 years inside the walls, I’m moving outside!!

Time is running and I have been working in the software world for 13 years and promoting the “software agile thing” in my area, for 6 years. Today, I need to step back. As my professional life has moved from R&D management to Product Marketing Management, my professional focus has shifted and I need  to improve my skills in this area.

I’m writing this article because I would like to thank my growing network and  make sure you won’t be surprised by my new area of interest, that could be outside of your own.

I imagine a few of you, shaking your heads, uttering a pfff of disappointment and saying: Franck and his books, his constant learning curve. For what?

This is really simple: Without a sense of progress, I get bored in my professional activity.

In 2009, for the first time since beginning in this sofware development world, I had a sense of accomplishment. As Agile was the main change we had implemented, I …