Knowledge Work and Software
Knowledge Work and Software carries TOC into settings where the constraint is rarely a physical machine. The constraint in a software delivery pipeline is more typically deployment frequency, testing capacity, code-review throughput, a release-gating policy, or a single resource — Gene Kim’s “Brent” — than any countable physical resource. The Five Focusing Steps apply unchanged: find the bottleneck in the deployment pipeline, exploit it (automate what can be automated at the constraint), subordinate everything else (do not let non-bottleneck work pile up ahead of the constraint), elevate it (hire, train, restructure), repeat.
The entries here cover ToC for Software and DevOps as the Phoenix Project-lineage operationalization of TOC for software development and IT operations; Flow Metrics for Knowledge Work as the measurement vocabulary (cycle time, work-in-progress, throughput, flow efficiency) that makes non-physical constraints legible; Agile CCPM as Ujigawa & Updegrove’s 2016 reformulation of Critical Chain for sprint-based teams (covered jointly with the CCPM section, with its primary structural treatment here in the software context); and Throughput Economics for Software Organizations as Schragenheim, Camp, and Surace’s 2021 framework for applying throughput accounting to subscription, licensing, and services revenue contexts where engineering capacity is the operating expense.
The bridge from The Phoenix Project’s narrative to working TOC vocabulary is the largest reachable audience for new TOC adoption today. The Three Ways of DevOps (flow, feedback, continuous learning) map onto TOC’s constraint-focused improvement cycle, but the mapping is not automatic; software practitioners adopting CCPM almost always need an Agile / CCPM bridge that preserves the buffer aggregation discipline rather than layering Critical Chain language on top of standard Scrum.
A practical reading path starts with ToC for Software and DevOps as the entry point from The Phoenix Project into the core TOC vocabulary, then Flow Metrics for Knowledge Work to establish the measurement language Step 1 of the Five Focusing Steps requires in a non-physical system, then Throughput Economics for Software Organizations when the question is product-mix or roadmap prioritization, then Agile CCPM when a software team is adopting Critical Chain in sprint-based work.