1
0
Fork 0

Final version

This commit is contained in:
Dirk Nederveen 2023-05-26 10:29:31 +02:00
parent 9d498366a0
commit db9bb206eb
Signed by untrusted user who does not match committer: dirk
GPG Key ID: 30C016E96E2219B8
2 changed files with 61 additions and 26 deletions

BIN
cd-pipeline.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

View File

@ -54,6 +54,7 @@
</p>
<aside class="notes">
<p>Today we'll follow a bug through the processes of development team</p>
🦹🏻‍♂️ Customer<br>
🦸🏼‍♂️ Support Hero<br>
🧑‍💼 Company/Product Owner<br>
@ -79,13 +80,11 @@
</aside>
</section>
<section data-markdown>
# Closed sprint
- Two weeks is fast in context of 6 month CD-ROM releases!
- How long does shipping take for your application?
---
# Closed sprint
@ -193,21 +192,37 @@
</aside>
</section>
<section data-markdown="" class="unfinished">
<section data-markdown="">
# Time to value
- The bug is fixed, 🦹🏻‍♂️ Customer can send their invoices again!
- Took 5 weeks
- Took 5 weeks <!-- .element: class="fragment" -->
</section>
</section>
<section class="unfinished">
<h1>Processes are there for a reason!</h1>
<section>
<section data-markdown="">
# Value stream mapping
- How the *value* flows through an organisation
- *Who* holds responsibility
- Time to value
</section>
<aside class="notes" data-markdown="">
- We engaged in an exercise of (informal) value stream mapping
- Actually helps with providing estimates
</aside>
</section>
<section>
<h1>We have processes for a reason</h1>
<ul>
<li>Quality assurance</li>
<li>Pace</li>
<li>Delivering software reliably</li>
<li class="fragment">Make the suits happy</li>
</ul>
<aside class="notes">
@ -241,20 +256,6 @@
</section>
</section>
<section>
<section data-markdown="">
# Value stream mapping
- How the *value* flows through an organisation
- *Who* holds responsibility
- Time to value
</section>
<aside class="notes">
asdfasdf
</aside>
</section>
<section>
<section id="continuous-delivery">
<h1>Continuous delivery</h1>
@ -278,9 +279,24 @@
</section>
<section id="deployment-pipeline">
<h2>The deployment pipeline</h2>
<h2>Deployment pipeline</h2>
...!!!
<img src="cd-pipeline.png">
</section>
<section>
<h2>Deployment pipeline</h2>
<p data-markdown="">
- Releasable: `True` or `False`
- Quick feedback
- Release → Domain knowledge → Pipeline improvements → Better release → …
</p>
</section>
<section id="deployment-pipeline">
<h2>Deployment pipeline</h2>
<img src="cd-pipeline.png">
</section>
<section id="build-quality-in" data-markdown="">
@ -316,7 +332,8 @@
<section id="everyone-is-responsible" data-markdown="">
## Everyone is responsible
-
- Understand the Ops team
- Grow in mutual trust
</section>
</section>
@ -346,7 +363,7 @@
# What to do this Monday?
* Computers perform repetitive tasks, people solve people-solve-problems
- improve the automation of one repeating task
- improve your app's deployment pipeline
---
# What to do this Monday?
@ -367,8 +384,25 @@
---
# What to do this Monday?
Ask *"Why can't we deploy this today?"*
and automate the answer
Ask *"Why can't we deploy this today?"* and automate the answer
</section>
</section>
<section>
<section id="credits">
<h1>Why can't we deploy this today?</h1>
Credits:
<ul>
<li>👸🏻 My lovely wife for telling again and again my slides have too many words</li>
<li><a href="https://lineicons.com/">Lineicons</a> for the brand icons</li>
<li>The Jet-Stream crew for joining me in discovering Continuous Delivery in more depth</li>
<li><a href="https://revealjs.com/">reveal.js</a> for the slides framework</li>
</ul>
</section>
<section id="endcap">
<h1>Why can't we deploy this today?</h1>
</section>
</section>
</div>
@ -384,6 +418,7 @@
// - https://revealjs.com/config/
Reveal.initialize({
hash: true,
defaultTiming: 42,
// Learn about plugins: https://revealjs.com/plugins/
plugins: [RevealMarkdown, RevealHighlight, RevealNotes]