InfoQ

News

Presentation: The Development of a New Car at Toyota

Posted by Abel Avram on Aug 14, 2008 03:15 AM

Community
Agile
Topics
Agile Techniques
Tags
agile2008 ,
Management ,
Toyota Production System

In this presentation made during Agile 2008, Kenji Hiranabe talks about Toyota's development process of a new car. Kenji shares his experience meeting Nobuaki Katayama, Chief Engineer at Toyota, and the lessons he learned from him.

Watch: The Development of a New Car at Toyota (25 min)

Kenji met Nobuaki Katayama during Developers' Summit 2008 in Tokyo where Toyota's Chief Engineer kept a presentation about the process used in creating a new car. Nobuaki says there are three main phases in car development:

  1. Planning and Concept Development – Concept, style, market research, pre-development, cost and profit target.
  2. Real Car Development – Designing, prototyping, evaluation.
  3. Production and Sales - Entering into mass production and selling the car.

Nobuaki emphasizes the first phase, creating a good concept being the most important. A complete concept is created, then it is tested with dealers and possible customers around the country to see if the concept is well received. Then comes prototyping and production.

Nobuaki gives some advices useful in software development. One of them is honest communication. Another, face-to-face communication, or TV conference if face-to-face is not possible. Another is: "Don't complain. Cooperate", and is Toyota's DNA, according to Nobuaki.

Nobuaki also noted some differences between Agile methodologies and car manufacturing ones. For example, there is no room for repetition or iteration when making a car.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
Toyota not the only way. by Zubin Wadia Posted Aug 17, 2008 1:23 AM
Re: Toyota not the only way. by Tero Vaananen Posted Aug 18, 2008 11:40 AM
? by elzo valugi Posted Aug 21, 2008 10:57 AM
  1. Back to top

    Toyota not the only way.

    Aug 17, 2008 1:23 AM by Zubin Wadia

    It's interesting how the CE prefers to have a non-Charismatic leader for teams. That was about the only surprise. The 'Toyota Way' is usually always the focus, but I would be surprised if every Japanese car manufacturer shared these values and perception of leadership.

    Honda, for example, probably has a different value system - it seems that passion & charisma are positive aspects in that system. Take Formula 1 for example - both manufacturers have had long stints but Honda clearly has the edge when it comes to World Championships and race wins (5 championships, 71 wins as an engine supplier, 3 Factory wins).

    Toyota, if I remember correctly, has yet to register a race win in 116 attempts with a yearly budget rumored to be in the $200-600M zone. More alarmingly, Toyota hasn't shown itself to be particularly accepting of their F1 shortcomings, neither are they taking any calculated risks. They have repeated, refined and spiraled-up to nowhere. ;)

    So, the question that sprung up in my mind is the following:

    In a system that has a low tolerance for passion & charisma, can adversity & chaos be easily overcome when encountered? Or would a company that encourages passion & charisma respond & overcome those challenges better?

    It is no surprise to me that while GM/Toyota/Ford saw U.S. domestic sales slump, Honda somehow conjured up a sales gain in the first seven months of 2008 (source: Reuters).

    Must have been some charismatic leader who spurred them on.

    Cheers,

    Zubin Wadia

    CTO

    www.zwadia.com

    www.imagework.com

    "Business Acceleration through Process Automation."

  2. Back to top

    Re: Toyota not the only way.

    Aug 18, 2008 11:40 AM by Tero Vaananen

    I think what ever you do, you always have to have a sense of balance. Charisma and passion can be good things but they can also take you to a very bad place if you can not sit back and see the big picture in a calm and calculative manner.

    I can understand why a more subdued and calm leader would be preferred in most situations. They can be wrong as anyone else, but it can be usually caught before things really go wrong. Charismatic leaders can be much harder to keep in check, as they usually carry so much unchallenged support by their own virtue that some natural feedback loops do not exist to correct failures in judgment.

  3. Back to top

    ?

    Aug 21, 2008 10:57 AM by elzo valugi

    I don't remember since I saw such a bad presentation. We all know how to read, the fellow was an extra... he should stayed mute.

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.