Work out of the story
This commit is contained in:
Dirk Nederveen
parent
c8719a956a
commit
b6a1efddb1
GPG Key ID:
30C016E96E2219B8
152
index.html
152
index.html
|
|
@ -18,18 +18,20 @@
|
|||
<body>
|
||||
<div class="reveal">
|
||||
<div class="slides">
|
||||
<section>
|
||||
<section data-markdown>
|
||||
# About me
|
||||
<section data-markdown="" id="cover-page">
|
||||
# Why can't we deploy this today?
|
||||
</section>
|
||||
|
||||
* Dirk Nederveen, [@dirk@blog.ndrvn.nl](https://blog.ndrvn.nl/u/dirk)
|
||||
* Husband, father of 3, Streaming Engineer (QA) @Jet-Stream
|
||||
* Interests:
|
||||
- Theology
|
||||
- Neurospychology
|
||||
- Reading
|
||||
- Beer brewing
|
||||
</section>
|
||||
<section data-markdown>
|
||||
# About me
|
||||
|
||||
* Dirk Nederveen, [@dirk@blog.ndrvn.nl](https://blog.ndrvn.nl/u/dirk)
|
||||
* Husband, father of 3, Streaming Engineer (QA) @Jet-Stream
|
||||
* Interests:
|
||||
- Theology
|
||||
- Neurospychology
|
||||
- Reading
|
||||
- Beer brewing
|
||||
</section>
|
||||
|
||||
<section data-markdown="" id="bluf">
|
||||
|
|
@ -37,39 +39,98 @@
|
|||
</section>
|
||||
|
||||
<section>
|
||||
<section data-markdown>
|
||||
<section data-markdown id="story-bug">
|
||||
# The story of a bug
|
||||
|
||||
Starring:
|
||||
- 🦹🏻♂️ Customer
|
||||
- 🦸🏼♂️ Support Hero
|
||||
- 🧑💼 Product Owner
|
||||
- 👩🏾💻 Sr. Dev
|
||||
- 👷🏻♂️ Jr. Dev
|
||||
- 👩🏼🚒 System Operator
|
||||
</section>
|
||||
<section data-markdown>
|
||||
- 🧑💼 Company/Product Owner
|
||||
- Dev team: 👩🏾💻 Sr. Dev and 👷🏻♂️ Jr. Dev
|
||||
- Ops team: 🙅 QA and 👩🏼🚒 System Operator
|
||||
|
||||
---
|
||||
|
||||
- 🦹🏻♂️ Customer calls with a question about sending an invoice on Monday 1 May, 🦸🏼♂️ Support Hero logs ticket BS-1234 in
|
||||
Jira
|
||||
- 🧑💼 Product Owner, 👩🏾💻 Sr. Dev and 🦸🏼♂️ Support Hero have triage meeting on Thursday 4 May, bug confirmed, priority
|
||||
'Highest'
|
||||
- 🧑💼 Product Owner and 👩🏾💻 Sr. Dev 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
|
||||
|
||||
👇
|
||||
- Team has Sprint Planning meeting on Monday 8 May, commit to BS-1234 for 1 Story Point
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<section data-markdown style="color:red">
|
||||
# Closed sprint
|
||||
|
||||
- Two weeks is fast in context of 6 month CD-ROM releases!
|
||||
- How long does shipping take for your application?
|
||||
|
||||
---
|
||||
|
||||
# Closed sprint
|
||||
|
||||
- 👍
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section id="pull-requests">
|
||||
<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
|
||||
---
|
||||
|
||||
👇
|
||||
# Pull Requests
|
||||
|
||||
- Untrusted contributer send in patch
|
||||
- Trusted maintainer chooses what to merge
|
||||
- Communication through centralised repositor
|
||||
---
|
||||
# Pull Requests
|
||||
|
||||
- 👍 Multiple people look at the code
|
||||
- 👎 Focus on code level, not product level
|
||||
- 👎 Value spends a lot of time waiting
|
||||
</section>
|
||||
<section data-markdown>
|
||||
- 👷🏻♂️ Jr. Dev processes feedback on Thursday 18 May, 10:00
|
||||
- 👩🏾💻 Sr. Dev merges PR #2345 on Thursday 18 May 🎉
|
||||
- 👩🏼🚒 System Operator prepares release after Sprint end, and deploys update on Tuesday, 23 May
|
||||
</section>
|
||||
|
||||
<section id="handoffs">
|
||||
<section data-markdown="" style="color: red;">
|
||||
- 👷🏻♂️ Jr. Dev processes feedback on Wednesday 17 May, 10:00
|
||||
- Oh no! 💥 Merge conflict!
|
||||
- 👩🏾💻 Sr. Dev checks PR #2345 and Slacks 👷🏻♂️ Jr. Dev on Wednesday 17 May, 15:00
|
||||
- It's the Ascension Day weekend! 👷🏻♂️ Jr. Dev is off to a festival 🕺
|
||||
---
|
||||
# Handoffs
|
||||
|
||||
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section id="shared-responsibility">
|
||||
<section data-markdown="">
|
||||
- Monday 22 May: another Sprint Planning meeting. The team commits to BS-1234 again (0 Story points now, "it's basically done")
|
||||
- Tuesday 30 May: 👷🏻♂️ Jr. Dev picks up BS-1234 again, fixes the merge conflict
|
||||
- Tuesday 30 May: 👩🏾💻 Sr. Dev approves PR #2345 and 👷🏻♂️ Jr. Dev gets to click the ⛙ Merge button!
|
||||
- Friday 2 June: Sprint end! Dev team sends the release candidate to Ops team
|
||||
|
||||
---
|
||||
TODO: Chapter about value streams crossing team boundaries
|
||||
</section>
|
||||
</section>
|
||||
<section id="time-to-value">
|
||||
<section data-markdown="">
|
||||
- 👩🏼🚒 System Operator prepares release after Sprint end, and deploys update on Tuesday, 6 June 07:00
|
||||
- 🧑💼 Product Owner sends the update newsletter Tuesday at 09:00
|
||||
- 🦹🏻♂️ Customer calls again: the bug is not fixed!
|
||||
---
|
||||
- 🧑💼 Product Owner calls an urgent meeting: Why is BS-1234 (zero points!!) open for over a month?
|
||||
|
||||
---
|
||||
TODO: Chapter about time-to-value
|
||||
</section>
|
||||
</section>
|
||||
|
||||
|
|
@ -88,32 +149,15 @@
|
|||
- Separate release team
|
||||
* Hand-offs:
|
||||
- 🦸🏼♂️ Support Hero ➡️ Dev Team
|
||||
- 👷🏻♂️ Jr. Dev ➡️ 👩🏾💻 Sr. Dev
|
||||
- Dev Team ➡️ 👩🏼🚒 System Operator
|
||||
</section>
|
||||
|
||||
<section data-markdown="">
|
||||
# What to do this Monday?
|
||||
|
||||
* Sketch how a 1-hour bug streams through your org
|
||||
- Discovery
|
||||
- Selection/prioritisation
|
||||
- Implementation
|
||||
- Verification
|
||||
- To production
|
||||
- 👷🏻♂️ Jr. Dev ↔ 👩🏾💻 Sr. Dev
|
||||
- Dev Team ➡️ Ops Team
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<section data-markdown="">
|
||||
# Processes are there for a reason!
|
||||
<section data-markdown="" style="color:red">
|
||||
# TODO Processes are there for a reason!
|
||||
|
||||
but whom do they benefit?
|
||||
</section>
|
||||
|
||||
<section data-markdown="">
|
||||
# Closed sprint
|
||||
</section>
|
||||
but whom do they benefit?
|
||||
</section>
|
||||
|
||||
<section id="continuous-delivery">
|
||||
|
|
@ -137,7 +181,17 @@
|
|||
</div>
|
||||
</section>
|
||||
|
||||
</div>
|
||||
<section data-markdown="">
|
||||
# What to do this Monday?
|
||||
|
||||
* Sketch how a 1-hour bug streams through your org
|
||||
- Discovery
|
||||
- Selection/prioritisation
|
||||
- Implementation
|
||||
- Verification
|
||||
- To production
|
||||
</section>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<script src="dist/reveal.js"></script>
|
||||
|
|
|
|||
Loading…
Reference in New Issue