deploy: 29c1f1f

pintergreg · Sep 16, 2024 · 3f98fda · 3f98fda
1 parent cf21101
commit 3f98fda
Show file tree

Hide file tree

Showing 9 changed files with 156 additions and 2 deletions.
diff --git a/lectures/01_sdlc.html b/lectures/01_sdlc.html
@@ -549,6 +549,7 @@ <h2 id="kanban-in-software-development"><a class="header" href="#kanban-in-softw
 <h1 id="scum--kanban--scrumban"><a class="header" href="#scum--kanban--scrumban">SCUM + kanban = scrumban</a></h1>
 <ul>
 <li>SCRUM and kanban can coexist</li>
+<li>quite new methodology</li>
 </ul>
 <h1 id="references"><a class="header" href="#references">references</a></h1>
 

diff --git a/lectures/03_kanban.html b/lectures/03_kanban.html
@@ -347,6 +347,53 @@ <h1 id="kanban-measures"><a class="header" href="#kanban-measures">kanban measur
 <p>Visualizing these metrics using charts is recommended. It does not
 matter what kind of charts are used as long as they enable a shared
 understanding of the Kanban system’s current health and performance.</p>
+</div>
+<h1 id="toyotas-six-rules-enwiki1239509091"><a class="header" href="#toyotas-six-rules-enwiki1239509091">Toyota’s six rules [@enwiki:1239509091]</a></h1>
+<div class="columns">
+<div class="column" width="70%">
+<ol>
+<li>Each process issues requests (kanban) to its suppliers when it
+consumes its supplies.</li>
+<li>Each process produces according to the quantity and sequence of
+incoming requests.</li>
+<li>No items are made or transported without a request.</li>
+<li>The request associated with an item is always attached to it.</li>
+<li>Processes must not send out defective items, to ensure that the
+finished products will be defect-free.</li>
+<li>Limiting the number of pending requests makes the process more
+sensitive and reveals inefficiencies.</li>
+</ol>
+</div>
+<div class="column" width="30%">
+<figure>
+<img src="figures/080527-F-0000A-001.JPG"
+alt="Kanban card together with the bag of bolts" />
+<figcaption aria-hidden="true">Kanban card together with the bag of
+bolts</figcaption>
+</figure>
+</div>
+</div>
+<h1 id="scrumban"><a class="header" href="#scrumban">scrumban</a></h1>
+<div class="columns">
+<div class="column" width="50%">
+<p>Scrum contributes to scrumban:</p>
+<ul>
+<li>sprints</li>
+<li>daily standups</li>
+<li>retrospectives</li>
+</ul>
+</div>
+<div class="column" width="50%">
+<p>Kanban contributes to scrumban:</p>
+<ul>
+<li>board</li>
+<li>cards</li>
+<li>work-in-progress limits</li>
+</ul>
+</div>
+</div>
+<h1 id="references"><a class="header" href="#references">references</a></h1>
+<div class="refs">
 </div>
 
                     </main>

diff --git a/lectures/figures/080527-F-0000A-001.JPG b/lectures/figures/080527-F-0000A-001.JPG
diff --git a/print.html b/print.html
@@ -1202,6 +1202,7 @@ <h2 id="kanban-in-software-development"><a class="header" href="#kanban-in-softw
 <h1 id="scum--kanban--scrumban"><a class="header" href="#scum--kanban--scrumban">SCUM + kanban = scrumban</a></h1>
 <ul>
 <li>SCRUM and kanban can coexist</li>
+<li>quite new methodology</li>
 </ul>
 <h1 id="references-1"><a class="header" href="#references-1">references</a></h1>
 <div style="break-before: page; page-break-before: always;"></div><p>this presentation is based on The Scrum Guide (2020)<br>by Ken Schwaber
@@ -2134,6 +2135,53 @@ <h1 id="kanban-measures"><a class="header" href="#kanban-measures">kanban measur
 <p>Visualizing these metrics using charts is recommended. It does not
 matter what kind of charts are used as long as they enable a shared
 understanding of the Kanban system’s current health and performance.</p>
+</div>
+<h1 id="toyotas-six-rules-enwiki1239509091"><a class="header" href="#toyotas-six-rules-enwiki1239509091">Toyota’s six rules [@enwiki:1239509091]</a></h1>
+<div class="columns">
+<div class="column" width="70%">
+<ol>
+<li>Each process issues requests (kanban) to its suppliers when it
+consumes its supplies.</li>
+<li>Each process produces according to the quantity and sequence of
+incoming requests.</li>
+<li>No items are made or transported without a request.</li>
+<li>The request associated with an item is always attached to it.</li>
+<li>Processes must not send out defective items, to ensure that the
+finished products will be defect-free.</li>
+<li>Limiting the number of pending requests makes the process more
+sensitive and reveals inefficiencies.</li>
+</ol>
+</div>
+<div class="column" width="30%">
+<figure>
+<img src="lectures/figures/080527-F-0000A-001.JPG"
+alt="Kanban card together with the bag of bolts" />
+<figcaption aria-hidden="true">Kanban card together with the bag of
+bolts</figcaption>
+</figure>
+</div>
+</div>
+<h1 id="scrumban"><a class="header" href="#scrumban">scrumban</a></h1>
+<div class="columns">
+<div class="column" width="50%">
+<p>Scrum contributes to scrumban:</p>
+<ul>
+<li>sprints</li>
+<li>daily standups</li>
+<li>retrospectives</li>
+</ul>
+</div>
+<div class="column" width="50%">
+<p>Kanban contributes to scrumban:</p>
+<ul>
+<li>board</li>
+<li>cards</li>
+<li>work-in-progress limits</li>
+</ul>
+</div>
+</div>
+<h1 id="references-3"><a class="header" href="#references-3">references</a></h1>
+<div class="refs">
 </div>
 
                     </main>

diff --git a/searchindex.js b/searchindex.js
diff --git a/searchindex.json b/searchindex.json
diff --git a/slides/01_sdlc.html b/slides/01_sdlc.html
@@ -521,6 +521,7 @@ <h2>kanban in software development</h2>
 <h1>SCUM + kanban = scrumban</h1>
 <ul>
 <li>SCRUM and kanban can coexist</li>
+<li>quite new methodology</li>
 </ul>
 </section>
 

diff --git a/slides/03_kanban.html b/slides/03_kanban.html
@@ -236,6 +236,63 @@ <h1>kanban measures</h1>
 matter what kind of charts are used as long as they enable a shared
 understanding of the Kanban system’s current health and performance.</p>
 </aside>
+</section>
+
+<section id="toyotas-six-rules-enwiki1239509091"
+class="title-slide slide level1">
+<h1>Toyota’s six rules <span class="citation"
+data-cites="enwiki:1239509091"><strong>enwiki:1239509091?</strong></span></h1>
+<div class="columns">
+<div class="column" style="width:70%;">
+<ol type="1">
+<li>Each process issues requests (kanban) to its suppliers when it
+consumes its supplies.</li>
+<li>Each process produces according to the quantity and sequence of
+incoming requests.</li>
+<li>No items are made or transported without a request.</li>
+<li>The request associated with an item is always attached to it.</li>
+<li>Processes must not send out defective items, to ensure that the
+finished products will be defect-free.</li>
+<li>Limiting the number of pending requests makes the process more
+sensitive and reveals inefficiencies.</li>
+</ol>
+</div><div class="column" style="width:30%;">
+<figure>
+<img data-src="figures/080527-F-0000A-001.JPG"
+alt="Kanban card together with the bag of bolts" />
+<figcaption aria-hidden="true">Kanban card together with the bag of
+bolts</figcaption>
+</figure>
+</div>
+</div>
+</section>
+
+<section id="scrumban" class="title-slide slide level1">
+<h1>scrumban</h1>
+<div class="columns">
+<div class="column" style="width:50%;">
+<p>Scrum contributes to scrumban:</p>
+<ul>
+<li>sprints</li>
+<li>daily standups</li>
+<li>retrospectives</li>
+</ul>
+</div><div class="column" style="width:50%;">
+<p>Kanban contributes to scrumban:</p>
+<ul>
+<li>board</li>
+<li>cards</li>
+<li>work-in-progress limits</li>
+</ul>
+</div>
+</div>
+</section>
+
+<section id="references" class="title-slide slide level1">
+<h1>references</h1>
+<div class="refs">
+
+</div>
 </section>
     </div>
   </div>

diff --git a/slides/figures/080527-F-0000A-001.JPG b/slides/figures/080527-F-0000A-001.JPG