Personal Kanban

class: center, middle, inverse

# Personal Kanban

## Haïkel Guémar - @hguemar
## FAS: hguemar
## IRC: number80

---
## Whoami

.right-column[
<img src="img/me.jpeg" />
]

.left-column[

+ Fedora developer

+ CentOS Cloud SIG

+ RDO Release Wrangler @ Red Hat

+ OpenStack developer

]

---
class: middle, center

# Why?

---
class: middle

## I HAZ TOO MUCH WORK

---
class: middle

## Organizational failures

* Pressure Pressure Pressure

* Demand/Supply mismatch

---
class: middle

## The human mind

* Human sucks at multitasking (short-term memory has 7 slots -/+2)

* Constant interruptions (Context Switch Hell)

---
class: middle

## Zoomin on Context Switching

* Best way to kill productivity

* One thing at a time is the most effective

* Look at this graphic based on Gerald Weinberg's book " Quality Software Management: Systems thinking"

---
class: middle, center

# Kanban to the rescue!

---
class: middle

## What's that?

* KanBan means "Visual Card" in Japanese

* Originally came from Toyota as a scheduling  system for JIT manufacturing

* Tightly linked to Lean and Toyota Production System

---
class: middle

## Kanban Principles

---
class: middle

## Do not wait and start applying

---
class: middle, center

# How to start?

---
class: middle

## Step 1: define your Value Stream

The Value Stream is the flow of work from the moment you start to when it is finished.

---
class: middle

## Step 1: define your Value Stream

Simplest value stream being:

* Backlog: work waiting to be done

* Doing: work being done

* Done: guess what?

---
class: middle

## Step 2: Fill your backlog

---
class: middle

## Step 3: limit Work in Process

---
class: middle

## Theory of Constraints

* Defined by Eliyahu M. Goldratt  in his book "The Goal"

* Based on the premise that throughput is limited by one constraint

* By studying bottlenecks, we can improve the workflow

* Short term (leverage bottlenecks to make the most of our worlflow) vs long term (invest on removing bottlenecks)

* A system is as strong as its weakest link

---
class: middle

## Step 4: begin to pull

---
class: middle

## Step 5: Retrospective

Regularly evaluate your workflow

* Set the stage

* Gather data

* Generate insight

* Define actions

* Close it

---
class: middle

## Beyond

* Root-Cause Analysis

* Metrics:  lead-time, due-date performance, discarded tasks

* Cumulative Flow Diagram

---
class: middle

## Zoomin on CFD

---
class: middle, center

# Why it works?

---
class: middle

## Visualize

* Information radiators

* Measure your project pulse in a glance

* Centered around your value stream

---
class: middle

## Visualize

* Actual capacity

* Actual throughput

---
class: middle

## Improves our ...

* time management (are we making a good use of our time?)

* efficiency (are we doing the right thing?)

* Effectiveness (are we doing the right thing at the right time?)

---
class: middle

## Pitfalls

* Timeboxing is good

* Not an excuse to be lazy (Kanban is about self-discipline)

---
class: middle

## Tools

* paperboards, pens, stickers and you're done

* cantas

* trello

* kanboard

* Taiga.io

---
class: middle

## Readings

* "Personal Kanban" by Jim Benson

* "Kanban in Action" by Marcus Hammarberg and Joakim Sundén

* "The Toyota Way to Continuous Improvement" by Jeffrey Liker and James Franz

* "Scrum and XP from the Trenches" by Henrik Kniberg

* "Extreme Programming Explained: Embrace Change" by Kent Beck

---
class: middle, center, inverse

# Q/A