https://github.com/theangrydev/why-kanban
https://github.com/theangrydev/why-kanban
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/theangrydev/why-kanban
- Owner: theangrydev
- Created: 2015-11-12T20:21:33.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-02-16T01:34:38.000Z (over 9 years ago)
- Last Synced: 2025-02-09T16:42:51.559Z (3 months ago)
- Language: Java
- Size: 64.5 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Why Kanban?
This project implements a simple [Kanban](http://kanbanblog.com/explained) simulation to investigate the effects a Kanban approach can have on a software development pipeline.
Here are some key points I have learned so far by playing around with this:
* When there are no WIP limits and the team works slower than the new story rate, the average lead time increases unboundedly
* When there are WIP limits and the team works slower than the new story rate, the average lead time is bounded above by the maximal WIP limit divided by the overall throughput. This is a manifestation of [Little's Law](http://www.fabtime.com/ctwip.shtml).
* Regardless of WIP limits, throughput remains constant when the team works slower than the new story rate, provided that the team's behaviour is not influenced by the total amount of work in progress.
* Setting WIP limits too low will decrease the throughput if the team is capable of working at a rate faster than the WIP limits support.