This simulation allows you to compare different approaches to influence flow, the Flow Times and the throughput of a work process.

By adjusting the sliders below you can 

• observe the work process without any work in process limitations (WIP Limits), 
• with process step specific WIP Limits* (work state WIP limits), 
• or you may want to see the impact of the Tameflow approach with Kanban Token and Replenishment Token 
• or see the impact of the Drum-Buffer-Rope** method. 

* Well know in (agile) Kanban** Known in the physical world of factory production

The "Tameflow approach" using Kanban Token and Replenishment Token as well as the Drum-Buffer-Rope method take oth the Constraint (the weakest link of the work process) into consideration when pulling in new work items into the delivery "system". 

You can also simulate the effects of PUSH instead of PULL. 

Feel free to play around and recognize the different effects of work scheduling methods. 

If you have questions or feedback get in touch via twitter @swilluda
The work flow itselfLook at the simulation as if you would look on a kanban board. 
The simulation mimics a "typical" software delivery process. 
From left to right you find the following ten process steps. 

1. Input Queue (Backlog)
2. Selected for work (waiting for analysis or work break down)
3. Analyse, break down and understand
4. Waiting for development
5. In development
6. Waiting for review
7. In review
8. Waiting for deployment
9. In deployment
10. Done

Kanban Agile Flow Tameflow TOC Theory Of Constraints DBR Drum-Buffer-Rope

Basic Stock & Flow models for use in Systemic Perspective video.

Stock Flow Simulation Elements

Very simple ward occupancy model.

Ward Flow Queue Capacity Demand

This simulation allows you to compare different approaches to influence flow, the Flow Times and the throughput of a work process.

By adjusting the sliders below you can 

• observe the work process without any work in process limitations (WIP Limits), 
• with process step specific WIP Limits* (work state WIP limits), 
• or you may want to see the impact of the Tameflow approach with Kanban Token and Replenishment Token 
• or see the impact of the Drum-Buffer-Rope** method. 

* Well know in (agile) Kanban** Known in the physical world of factory production

The "Tameflow approach" using Kanban Token and Replenishment Token as well as the Drum-Buffer-Rope method take oth the Constraint (the weakest link of the work process) into consideration when pulling in new work items into the delivery "system". 

You can also simulate the effects of PUSH instead of PULL. 

Feel free to play around and recognize the different effects of work scheduling methods. 

If you have questions or feedback get in touch via twitter @swilluda
The work flow itselfLook at the simulation as if you would look on a kanban board. 
The simulation mimics a "typical" software delivery process. 
From left to right you find the following ten process steps. 

1. Input Queue (Backlog)
2. Selected for work (waiting for analysis or work break down)
3. Analyse, break down and understand
4. Waiting for development
5. In development
6. Waiting for review
7. In review
8. Waiting for deployment
9. In deployment
10. Done

Kanban Agile Flow Tameflow TOC Theory Of Constraints DBR Drum-Buffer-Rope

This simulation allows you to compare different approaches to influence flow, the Flow Times and the throughput of a work process. The simulation is described in the blog post "Starting late - The Superior Scheduling Approach - How, despite being identical, one company delivers almost 10 times the value of its competitor using flow-oriented project initiation."

By adjusting the slider below you can observe the work process 

• without any work in process limitations (WIP Limits), 
• with process step specific WIP Limits* (work state WIP limits), 
• with Kanban Token and Replenishment Token based on the Tameflow approach (a form of drum-buffer-rope) 
• with Drum Buffer Rope** scheduling method. 

* Well know in (agile) Kanban** Known in the physical world of factory production
The simulation and the comparison between the different scheduling approaches can be seen here -> https://youtu.be/xXvdVkxeMMQ

The "Tameflow approach" using Kanban Token and Replenishment Token as well as the Drum Buffer Rope method take the Constraint (the weakest link of the work process) into consideration when pulling in new work items into the delivery "system". 

Feel free to play around and recognize the different effects of work scheduling methods. 

If you have questions or feedback get in touch via twitter @swilluda
The work flow itselfLook at the simulation as if you would look on a kanban board. 
The simulation mimics a "typical" feature delivery process on portfolio level. 
From left to right you find the following ten process steps. 

1. Ideas
2. Selected ideas (waiting)
3. Initiate and pitch
4. Waiting for preparation
5. Prepare
6. Waiting for delivery
7. Deliver
8. Waiting for closure
9. Close and communicate
10. Closed

Kanban Agile Flow Tameflow TOC Theory Of Constraints DBR Drum Buffer Rope

SAS Radish Flow Bunny

To show symphon flow from the model

Flow

basic flow simulation

Stock Flow Basic

Exercise 1 Tub Water Flow

Ward Flow Queue Capacity Demand

Ward Flow Queue Capacity Demand

Ward Flow Queue Capacity Demand

This simulation allows you to compare different approaches to influence flow, the Flow Times and the throughput of a work process. The simulation is described in the blog post "Starting late - The Superior Scheduling Approach - How, despite being identical, one company delivers almost 10 times the value of its competitor using flow-oriented project initiation."

By adjusting the slider below you can observe the work process 

• without any work in process limitations (WIP Limits), 
• with process step specific WIP Limits* (work state WIP limits), 
• with Kanban Token and Replenishment Token based on the Tameflow approach (a form of drum-buffer-rope) 
• with Drum Buffer Rope** scheduling method. 

* Well know in (agile) Kanban** Known in the physical world of factory production
The simulation and the comparison between the different scheduling approaches can be seen here -> https://youtu.be/xXvdVkxeMMQ
The "Tameflow approach" using Kanban Token and Replenishment Token as well as the Drum Buffer Rope method take the Constraint (the weakest link of the work process) into consideration when pulling in new work items into the delivery "system". 

Feel free to play around and recognize the different effects of work scheduling methods. 

If you have questions or feedback get in touch via twitter @swilluda
The work flow itselfLook at the simulation as if you would look on a kanban board. 
The simulation mimics a "typical" feature delivery process on portfolio level. 
From left to right you find the following ten process steps. 

1. Ideas
2. Selected ideas (waiting)
3. Initiate and pitch
4. Waiting for preparation
5. Prepare
6. Waiting for delivery
7. Deliver
8. Waiting for closure
9. Close and communicate
10. Closed

Kanban Agile Flow Tameflow TOC Theory Of Constraints DBR Drum Buffer Rope

Flow

This simulation allows you to compare different approaches to influence flow, the Flow Times and the throughput of a work process.

By adjusting the sliders below you can 

• observe the work process without any work in process limitations (WIP Limits), 
• with process step specific WIP Limits* (work state WIP limits), 
• or you may want to see the impact of the Tameflow approach with Kanban Token and Replenishment Token 
• or see the impact of the Drum-Buffer-Rope** method. 

* Well know in (agile) Kanban** Known in the physical world of factory production

The "Tameflow approach" using Kanban Token and Replenishment Token as well as the Drum-Buffer-Rope method take oth the Constraint (the weakest link of the work process) into consideration when pulling in new work items into the delivery "system". 

You can also simulate the effects of PUSH instead of PULL. 

Feel free to play around and recognize the different effects of work scheduling methods. 

If you have questions or feedback get in touch via twitter @swilluda
The work flow itselfLook at the simulation as if you would look on a kanban board. 
The simulation mimics a "typical" software delivery process. 
From left to right you find the following ten process steps. 

1. Input Queue (Backlog)
2. Selected for work (waiting for analysis or work break down)
3. Analyse, break down and understand
4. Waiting for development
5. In development
6. Waiting for review
7. In review
8. Waiting for deployment
9. In deployment
10. Done

Kanban Agile Flow Tameflow TOC Theory Of Constraints DBR Drum-Buffer-Rope