-
Notifications
You must be signed in to change notification settings - Fork 0
Sources and Further Reading
Bill Eisenhauer edited this page Aug 7, 2026
·
3 revisions
Owner: Bill Eisenhauer Last Updated: August 6, 2026 Status: 🚧 Curated public references Contributors: Bill Eisenhauer
These references inform the operating hypothesis; they do not validate the simulator's constants or prove its causal relationships.
| Source | Relevance |
|---|---|
| TameFlow | Constraint-focused elevation, throughput, and the interaction of operational, financial, informational, and psychological flow |
| TameFlow Campfire Talks #1 | Connects Full-Kitting to informational flow, shared understanding, and Touch Time versus Wait Time |
| TameFlow Campfire Talks #8 | Shows Full-Kitting as a joint business-and-engineering activity that supports economic prioritization |
| TameFlow: Pull policies and flow debt | How premature or exceptional entry into a flow can make other WIP wait and create system-level debt |
| TameFlow: Bottleneck in workflow vs. constraint in process | Why a visible queue or long activity need not govern throughput |
| The Kanban Guide, May 2025 | Pull-based flow, workflow definition, WIP, throughput, work-item age, and cycle time |
| The Scrum Guide, November 2020 | Transparency, inspection, adaptation, Product Goals, and Sprint-based empirical delivery |
| DORA: State of AI-assisted Software Development 2025 | Evidence that AI amplifies the strengths and weaknesses of the underlying organizational system |
| Anthropic: Building Effective Agents | Distinguishes workflows from agents and recommends matching complexity to the task |
| GitHub: Creating diagrams | Mermaid support in GitHub wikis and Markdown |
- Eliyahu M. Goldratt and Jeff Cox, The Goal
- Steve Tendon, The Book of TameFlow
- Steve Tendon, Standing on Bits: Agile Software Engineering Management at Scale with the Theory of Constraints
- Steve Tendon and Wolfram Müller, TameFlow
- Steve Pereira and Andrew Davis, Flow Engineering: From Value Stream Mapping to Effective Action
- Daniel S. Vacanti, Actionable Agile Metrics for Predictability
- Matthew Skelton and Manuel Pais, Team Topologies
- Gene Kim and Steven J. Spear, Wiring the Winning Organization
- Mik Kersten, Project to Product
flowchart LR
A["Established methods"] --> C["Leverage Lab synthesis"]
B["Emerging agent research"] --> C
C --> D["Executable teaching model"]
D --> E["Questions and field experiments"]
E -. not proof .-> C
In prose: the lab synthesizes established methods and emerging agent research into a teaching model. Playing it should create questions and field experiments, not be treated as proof of the synthesis.
Useful additions to this wiki would answer one of these questions:
- What evidence best distinguishes a visible bottleneck from the governing constraint?
- How should human-attention capacity be measured without turning judgment into utilization theater?
- Which adoption and ownership signals are both inexpensive and defensible?
- How do constraint dynamics differ between product, platform, and partner-delivery work?
- Which agent tasks reliably increase accepted outcomes rather than intermediate output?
Back to Home