TPS's influence on software development runs through multiple channels. The primary transmission path: TPS → lean manufacturing (named by Womack/Jones) → Lean Software Development (Mary and Tom Poppendieck, 2003) → Agile practices. Specific TPS concepts that map to software: kanban → Kanban boards and WIP limits (David Anderson), one-piece-flow → continuous integration and small batches, smed → continuous deployment (reducing release "changeover"), pull-production → pull-based backlogs, five-whys → retrospective root-cause analysis (adopted by Eric Ries for Lean Startup), andon → build/deploy status radiators, seven-wastes-muda → software waste categories (Poppendieck's seven wastes of software development), value-stream → software value stream mapping. The DevOps movement (2008-present) extends the mapping further: infrastructure as code enables standard-work for deployment, monitoring enables jidoka-style defect detection, and the "three ways" of DevOps (flow, feedback, continuous learning) are direct TPS analogues. Not all mappings are equally strong — heijunka and takt-time have weaker software analogues, and the physical nature of manufacturing creates constraints that software does not share.