Never do anything until you ready to use it, in software too? [Toyota principle]

I was listening to a podcast. Where they talked about principles Toyota was using:

Never do anything until you are ready to use it.

I think this tells us to look in other places, to learn what other practices have been known for years.

It may apply to software construction, but I am not sure it does apply

If we consider the five elements in a "toyota-way of decision making", based on the principle that "how you arrive at the decision is just as important as the quality of the decision":

[mode humour ON]

• Finding out what is really going on, including genchi gembutsu.

  Except that sometime, one does finally understand what is going on when the client explain to us at the end of the project;)

• Understanding underlying causes that explain surface appearances—asking “Why?” five times.

  Sure but the client is not available enough during the project ;)

• Broadly considering alternative solutions and developing a detailed rationale for the preferred solution.

  Too late, the programmers are already coding like madmen :)

• Building consensus within the team, including Toyota employees and outside partners.

  Oops that programmer is already re-writing the authentification system even though the old one was working fine

• Using very efficient communication vehicles to do one through four, preferably one side of one sheet of paper.

  Did you hear "death by powerpoint" ? This is not always our strong suit ;)

[mode humour OFF]

Seriously, as stated by the previous answers, the Agile philosophy does address some of the core tenants of this Toyota principle.

And it may be a little richer that just "You Ain't Gonna Need It", as described in the book "The Toyota way"