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 itself
Look 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.
- Input Queue (Backlog)
- Selected for work (waiting for analysis or work break down)
- Analyse, break down and understand
- Waiting for development
- In development
- Waiting for review
- In review
- Waiting for deployment
- In deployment
- Done
Clone of [Archive] Kanban Board Simulation - WIP Limit, Tameflow Kanban Token and Drum-Buffer-Rope
This simulation mimics the flow of projects through an organization. The organization consists of teams that idependently or collaboratively work on projects. Many of the projects have a mulit-team dependency.
If you want to understand more in depth what this simulation is all about, read this blog post: https://stefan-willuda.medium.com/super-powerful-how-full-kitting-will-speed-up-your-cross-team-projects-1598d55fa9d7
Clone of [Published] Full Kitting in Dependent Team Delivery
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 itself
Look 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.
- Input Queue (Backlog)
- Selected for work (waiting for analysis or work break down)
- Analyse, break down and understand
- Waiting for development
- In development
- Waiting for review
- In review
- Waiting for deployment
- In deployment
- Done
Clone of [Archive] Kanban Board Simulation - WIP Limit, Tameflow Kanban Token and Drum-Buffer-Rope
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 itself
Look 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.
- Input Queue (Backlog)
- Selected for work (waiting for analysis or work break down)
- Analyse, break down and understand
- Waiting for development
- In development
- Waiting for review
- In review
- Waiting for deployment
- In deployment
- Done
Clone of Kanban Board Simulation - WIP Limit, Tameflow Kanban Token and Drum-Buffer-Rope
To show symphon flow from the model
Water flow
Day 2 - We started with this software, using a example of medicine being pumped into the cochlea of someone's ear. Everything with units is in microliters, micrograms, Min. Concentration of medicine enters the ear, what is the concentration after a day, if there was no medicine concentration to begin with.
08_28
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 itself
Look 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.
- Ideas
- Selected ideas (waiting)
- Initiate and pitch
- Waiting for preparation
- Prepare
- Waiting for delivery
- Deliver
- Waiting for closure
- Close and communicate
- Closed
Clone of [Published] Simulation Starting late - The Superior Scheduling Approach (advanced version)
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 itself
Look 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.
- Input Queue (Backlog)
- Selected for work (waiting for analysis or work break down)
- Analyse, break down and understand
- Waiting for development
- In development
- Waiting for review
- In review
- Waiting for deployment
- In deployment
- Done
Clone of Kanban Board Simulation - WIP Limit, Tameflow Kanban Token and 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 itself
Look 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.
- Ideas
- Selected ideas (waiting)
- Initiate and pitch
- Waiting for preparation
- Prepare
- Waiting for delivery
- Deliver
- Waiting for closure
- Close and communicate
- Closed
Clone of [Published] Simulation Starting late - The Superior Scheduling Approach (simplified version)
Basic Stock & Flow models for use in Systemic Perspective video.
@LinkedIn, Twitter, YouTube
Clone of Stock & Flow Models
Day 2 - We started with this software, using a example of medicine being pumped into the cochlea of someone's ear. Everything with units is in microliters, micrograms, Min. Concentration of medicine enters the ear, what is the concentration after a day, if there was no medicine concentration to begin with.
Clone of 08_28
Clone of Simple ward DCAQ
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 itself
Look 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.
- Input Queue (Backlog)
- Selected for work (waiting for analysis or work break down)
- Analyse, break down and understand
- Waiting for development
- In development
- Waiting for review
- In review
- Waiting for deployment
- In deployment
- Done
Clone of Kanban Board Simulation - WIP Limit, Tameflow Kanban Token and Drum-Buffer-Rope
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 itself
Look 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.
- Input Queue (Backlog)
- Selected for work (waiting for analysis or work break down)
- Analyse, break down and understand
- Waiting for development
- In development
- Waiting for review
- In review
- Waiting for deployment
- In deployment
- Done
Clone of [Archive] Kanban Board Simulation - WIP Limit, Tameflow Kanban Token and Drum-Buffer-Rope
Very simple ward occupancy model.
Clone of Simple ward DCAQ
This simulation mimics the flow of projects through an organization. The organization consists of teams that idependently or collaboratively work on projects. Many of the projects have a mulit-team dependency.
If you want to understand more in depth what this simulation is all about, read this blog post: https://stefan-willuda.medium.com/super-powerful-how-full-kitting-will-speed-up-your-cross-team-projects-1598d55fa9d7
Clone of [Published] Full Kitting in Dependent Team Delivery
WIP Based on paulH Requisite Organization and Elliott Jaques with some dynamics added. Could link to CLD work
Levels of Work
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 itself
Look 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.
- Input Queue (Backlog)
- Selected for work (waiting for analysis or work break down)
- Analyse, break down and understand
- Waiting for development
- In development
- Waiting for review
- In review
- Waiting for deployment
- In deployment
- Done
Clone of Kanban Board Simulation - WIP Limit, Tameflow Kanban Token and Drum-Buffer-Rope
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 itself
Look 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.
- Input Queue (Backlog)
- Selected for work (waiting for analysis or work break down)
- Analyse, break down and understand
- Waiting for development
- In development
- Waiting for review
- In review
- Waiting for deployment
- In deployment
- Done
Clone of Kanban Board Simulation - WIP Limit, Tameflow Kanban Token and Drum-Buffer-Rope
This simulation mimics the flow of projects through an organization. The organization consists of teams that idependently or collaboratively work on projects. Many of the projects have a mulit-team dependency.
If you want to understand more in depth what this simulation is all about, read this blog post: https://stefan-willuda.medium.com/super-powerful-how-full-kitting-will-speed-up-your-cross-team-projects-1598d55fa9d7
Clone of [Published] Full Kitting in Dependent Team Delivery
This simulation mimics the flow of projects through an organization. The organization consists of teams that idependently or collaboratively work on projects. Many of the projects have a mulit-team dependency.
If you want to understand more in depth what this simulation is all about, read this blog post: https://stefan-willuda.medium.com/super-powerful-how-full-kitting-will-speed-up-your-cross-team-projects-1598d55fa9d7
Clone of [Published] Full Kitting in Dependent Team Delivery
