Chronologist
TameFlow and the Manifesto for Agile Software Development
How does Agile and the Manifesto for Agile Software Development relate to the TameFlow Approach?
Self-Interest: The Secret Sauce of the TameFlow Approach
Enlightened Self-Interest is a driving force in the TameFlow Approach. It is not considered as an idealstic concept of ethical philosophy, but as an Alexandrian Pattern providing a solution to a problem in a context.
eXtreme Programming and the TameFlow Approach
How does eXtreme Programming (XP) relate to the TameFlow Approach?
Market Disruption the TameFlow Way
We can reason about disrupting markets with the Six Innovation Questions.
Constraints Everywhere
The distinction between the Constraint in the Work Flow, Work Execution and Work Process may seem academic. The Jungle-Jeep-Journey metaphor will help you understand the differences and allow you to nail down your current Constraint.
TameFlow Insights: Cost of Delay (CoD) Improved via Theory of Constraints (TOC)
The Throughput Octane (or Financial Throughput Rate) is the most reliable measure of speed of generation of value.
How to Draw Buffer Fever Charts
A Buffer Fever Chart is a powerful tool. It provides even earlier leading signals than the other buffer penetration diagrams, because it is based on the Buffer Burn Rate, not on the Buffer Consumption. Learning to draw it properly is of essence.
Pattern Language Development
A pattern language is constructed when the confidence of the collected patterns is assessed, and when interrelated patterns are cross-referenced. Just collecting a number of patterns alone is not sufficient to define the pattern language. The quality of the pattern to be used must be recognized.
How Patterns become a Pattern Language
Patterns are the result of empirical observations, and they can constitute a phenomenological foundation for a scientific theory.
Pattern Languages are Means of Expression of Organizational Design
A pattern language is a means of expression that provides: (1) A descriptive notation for modeling and understanding organizational designs; (2) An actionable specifications of organizational designs, whereby that specification can be turned into real organizational structures; (3) A language for communicating and reasoning about organizational designs.