Lean Study Tour 2009 - Day 2 (Feeling Privileged)

Wednesday, April 22, 2009 10:04:16 AM (Romance Standard Time, UTC+01:00)
Yesterday was a really long day, and I have to admit I was to tired to write a blog entry. So here is the field report from day 2 of our Lean study tour. To be completely honest with you - I felt incredibly privileged about what I experienced in Nagoya yesterday. First we visted Toyota Commemorative Museum of Industry and Technology and the Motomachi plant like Jesper mentioned in his earlier blog entry - I would definitely recommend both to anyone visiting Japan.

After the plant tour we met Mr. Satoshi Ishii who is a project general manager at the BR Automotive Software Engineering Dept. within Toyota. In short, these guys are doing all sorts of software that is embedded in modern Toyota/Lexus cars. Satoshi Ishii explained to us that a modern Lexus (Toyota's luxury brand) contains 70 or more ECUs (electronic control units) which all needs software (brakes, engine, fuel injection, navigation, adaptive cruise control, etc.) along with the ability to communicate with each other.

Before the meeting I was a little skeptical - Were the Toyota culture so strong that it had found its way into the relatively new field of software development? What might surprise some, was that they were using a waterfall model (in Ishii-san's own words - in reality I think it was more like the spiral model). In spite of that, I had a feeling afterwards that I had just talked to perhaps the most skilled software development managers I have ever met! Does that sound like a paradox? I do not think so.

Let me explain it this way. I once said to myself that I did not want to waste my time as a developer on non-agile projects. In the Toyota case, I would certainly make an exception. Why? Because I believe that the principles that this company is built upon is of far greater importance than any of the agile pratices that we spent so much time on in the Western world.

After meeting Mr. Ishii, I had a talk with Mary Poppendieck (who is also with us on this study tour) and she believed that this was actually the first time a Toyota manager in software development has ever spoken publicly about how they apply their (Lean) philosophy in this field - I almost had the goose bumps :-)

Trust me... I will write more about the all the learnings of this meeting - but now it is time for preparing a presentation for the Agile Japan group tomorrow.

By Sune Gynthersen
Sunday, April 26, 2009 6:10:17 PM (Romance Standard Time, UTC+01:00)
I tried to comment on this post before but it seems that the comment did not stick.

Here is my comment in the form of a blog post: http://bit.ly/18UAhc
Monday, April 27, 2009 4:44:45 AM (Romance Standard Time, UTC+01:00)
Hello Vasco,

1) They certainly are able to deliver quality software on a tight schedule. They showed how the cost of software and electronics for the Prius was 47%. That car was developed on a extraordinary tight schedule, and as far as I know the software in that car works pretty well.

2) They clearly recognized the value of early testing and other agile principles. But they found it to be the primary objective to work on architecture, skills and motivation of employees. I would not say that is a bad priority, even with agile glasses on. Would you?

So the sometimes religious question about waterfall or not, was somehow not the most relevant and productive angle to look at Toyotas software development in this specific case
Bent Jensen
Monday, April 27, 2009 4:58:21 AM (Romance Standard Time, UTC+01:00)
I have to agree with Bent. Whatever the name of their process-model - We have to accept that they have been able to deliver a quality car on a tight schedule.

Also..what does it really mean to be agile? Some does a daily standup meeting, automated testing, have retrospectives, and deliver in multiple batches. Toyota does them all (maybe except the standup meeting which I'm not sure about).

I guarantee that Toyota is more disciplined than most agile teams I have seen.

Note that even though they called it "waterfall-like", there were multiple delieveries during development. In fact the word spiral-model was also used.


Sune Gynthersen
Sunday, May 03, 2009 12:37:36 PM (Romance Standard Time, UTC+01:00)
As I expected, the Toyota does waterfall was a red-herring. They don't really do waterfall. Note that you cannot do waterfall AND spiral model development. They are NOT compatible ;)

The right answer is probably: they do requirements and design first, but then they change that because they anyway plan to deliver multiple iterations. This is fine. But to avoid religious discussions one must stay away from dogma as well ;)

Your article was good anywyay, just misleading :)
All comments require the approval of the site owner before being displayed.
Name
E-mail
Home page

Comment (HTML not allowed)  

Enter the code shown (prevents robots):

Live Comment Preview