First actual CD slide

index.html

@@ -64,7 +64,7 @@
         <section data-markdown>
           # Deployment Anxiety Disorder
 
-          *A troublesome fear that prod go boom. Symptoms may include:*
+          *A troublesome fear that prod go 💥. Symptoms may include:*
             - excessive or insufficient release planning
             - difficulty to perform updates
             - panic attacks
@@ -94,6 +94,7 @@
             - from *flight* to *take a break*
             - from *freeze* to *accept*
           * Apply brakes
+          * Build trust
           * Control emotions
         </section>
 
@@ -103,7 +104,32 @@
           * Apply brakes
             - Commit to an *acceptable* workload
             - Communicate about your needs
+
+          * Build trust
+            - Deliver quality software
         </section>
+
+      </section>
+
+      <section id="continuous-delivery">
+        <h1>Continuous delivery</h1>
+
+        <div style="width: 80%; float: left" data-markdown="">
+          * Build quality in
+          * Work in small batches
+          * Computers perform repetitive tasks, people solve problems
+          * Relentlessly pursue continuous improvement
+          * Everyone is responsible
+        </div>
+
+        <div style="float: right; width: 20%; height: 8em">
+          <a href="https://www.bol.com/nl/nl/p/accelerate/9200000080652224">
+            <img src="accelerate.jpg" style="height: 50%;">
+          </a><br>
+          <a href="https://www.informit.com/store/continuous-delivery-reliable-software-releases-through-9780321770424?ranMID=24808">
+            <img src="cd-book.png" style="height: 50%;">
+          </a>
+        </div>
       </section>
 
       <section>
@@ -111,6 +137,8 @@
           # Value stream mapping
 
           How does the value stream through the organisation?
+
+          👇
         </section>
         <section data-markdown>
           - Customer calls with a question about sending an invoice on Monday 1 May, Support Hero logs ticket BS-1234 in
@@ -119,18 +147,42 @@
           'Highest'
           - Product Owner and Tech Lead have backlog grooming meeting on Friday 5 May
           - Team has Sprint Planning meeting on Monday 8 May, commit to BS-1234 for 2 Story Points
+
+          👇
         </section>
         <section data-markdown>
           - Jr. Dev picks up BS-1234, needs clarification and sends Customer an email on Wednesday 10 May
           - Customer responds Thursday 11 May, 16:00
           - Jr. Dev starts implementation on Monday 15 May, opens PR #2345 in GitHub
           - Sr. Dev responds to PR #2345 on Tuesday 16 May 16:00, needs improvement
+
+          👇
         </section>
         <section data-markdown>
           - Jr. Dev processes feedback on Thursday 18 May, 10:00
           - Sr. Dev merges PR #2345 on Thursday 18 May 🎉
           - Operations Team prepares release after Sprint end, and deploys update on Tuesday, 23 May
         </section>
+
+        <section data-markdown="">
+          Why is this process slow?
+
+          * Closed Sprint (1 week)
+          * Hand-offs:
+            - Support Hero ➡️ Tech Team
+            - Jr. Dev ➡️ Sr. Dev
+            - Dev Team ➡️ Ops team
+          * Delays in process
+            - Asynchronous PR review
+            - Separate release team
+        </section>
+
+        <section data-markdown="">
+          # What to do this Monday?
+
+          * Draw the value stream in your org
+          *
+        </section>
       </section>
     </div>
   </div>