-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsimulator.html
88 lines (69 loc) · 4.4 KB
/
simulator.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
<!--
Copyright 2015 David Kane
This file is part of FeatureBanSimulator.
FeatureBanSimulator is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
FeatureBanSimulator is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with FeatureBanSimulator. If not, see <http://www.gnu.org/licenses/>.
-->
<html>
<head>
<script src="lib/d3/d3.min.js" charset="utf-8"></script>
<script src="lib/jquery-2.1.3.min.js" charset="utf-8"></script>
<script src="simulator.js" charset="utf-8"></script>
</head>
<body>
</body>
<h1>FeatureBan Simulator</h1>
<p>This simulator serves two purposes. One, it provides
a tool to explore possible outcomes if facilitators want
to alter any of the basic rules of the simulation. Two,
it can be used as part of debriefing the simulation,
by letting facilitators help participants explore alternate
scenarios that they didn't explore during the FeatureBan activity.</p1>
<p>To use, select the desired paramters. The default parameters
are suitable for a baseline. Then click the Run Simulation button</p>
<p>The simulator will produce two results. First it will calculate
the average lead time and average number of work items completed
across ALL of the simulations just executed. It will also produce
a cumulative flow diagram of the LAST simulation as an illustration.<p>
<h3 id="parameters">Simulation Parameters</h3>
<label for="stages">Stages:</label>
<input type="text" name="stages" id="stages" value="5">How many stages should be on the Kanban board. Include 1 to cover the backlog.<br>
<label for="rounds">Rounds:</label>
<input type="text" name="rounds" id="rounds" value="10">How many rounds of die-rolling should be included in each simulation.<br>
<label for="minimumToUnblock">Minimum to Succeed:</label>
<input type="text" name="minimumToUnblock" id="minimumToUnblock" value="4">On a 6-sided die, on what value should be counted as a success result. Lower than this is considered a block. e.g. a 4 is a 50/50 split.<br>
<label for="workers">Workers:</label>
<input type="text" name="workers" id="workers" value="5">How many people should be included in each simulation.<br>
<label for="workItemsPerWorker">Work Items per Workers:</label>
<input type="text" name="workItemsPerWorker" id="workItemsPerWorker" value="10">This is used to determine how many simulated cards should be initialized.<br>
<label for="simulations">Number of Simulations:</label>
<input type="text" name="simulations" id="simulations" value="100">How many times the simulation should be run. If you are only interested in the cummulative flow diagram, 1 is sufficient. The metrics stablize around 1000 simulations.<br>
<label for="wipLimits">WiPLimits (Comma Separated):</label>
<input type="text" name="wipLimits" id="wipLimits" value="35,35,35">A comma separated list of WiP limits for all of the stages, except for the first (i.e the backlog) and the last (i.e. completed work). E.g. if there are 5 stages selected above, there should be 3 listed here. The defaults are set to be high enough that there should be in practice no effective limits.<br>
<label for="collaboation">Use Team Collaboration to Optimize Order of Work:</label>
<select name="collaboation" id="collaboation" >
<option value="false">False</option>
<option value="true">True</option>
</select>There are some differences in outcome based on how well the team works together. You need to run with a large number of simulations to see the effect reliably.<br>
<label for="randomizer">What Random Number Generator to Use:</label>
<select name="randomizer" id="randomizer" >
<option value="die">Dice</option>
<option value="cards">Cards</option>
<option value="fixed">Fixed</option>
</select><br>
<button type="button" id="start" onClick="simulate()">Run Simulation</button>
<h3 id="averageLeadTime"><h3>
<h3 id="averageCompleted"><h3>
<h3 id="averageCompleted">Cummulative Flow Diagram from the Last Simulation<h3>
<div id='chart'></div>
<h3 id="metrics"></h3>
<h3 id="board"></h3>
</html>