– – GO KANBAN !
GO KANBAN !
Applying kanban thinking
A BASIC REFRESHER...
Lean + Agile
Set of values and principles that outline how to
succeed with product development
Scrum + XP + Kanban
Put this principles into practice
*Scrum - Sprint planning meetings
**XP - Pair programming
***Kanban - Limit work in progress
TAKEAWAY*
or disclaimer
This presentation wouldn't explore kanaban to its core,
or would talk gibberish
this would start from very basic and understand Kanban in its role
to achieve the goals of Lean and Agile, in small, easily digestable steps
beside, yoy'll also know
How kanban can benefit you as an individual and
how you could apply it in your personal thinking
KANBAN? WHAT?
WHAT?
Literally, Kanban is Japanese for "visual cards"
or "sign board"
Pioneered at Toyota in the 1950s, is the term used
for visual and physical signaling system that ties
together the whole lean production system.
It's popping up in offices around the globe to boost
efficiency.
TECHNICALLY SPEAKING,
"Kanban system for software development" now simply
referred as "Kanban" was pioneered in 2004 by David Anderson
as a more direct implemenation of
Lean Thinking and
Theory of constraints*
So Kanban as applied to software development is
quite new, Kanban as used in lean
production is more than half century old.
http://en.wikipedia.org/wiki/Theory_of_Constraints
AS TOYOTA EXPLAINS,
KANBAN HOW ?
How it can be brought in picture
GROUND RULES.
To start with, Kanban relies on few surprisingly simple
rules
but that don't implicate that the game's easy too...
VISUALIZE LIMIT ANALYZE
VISUALIZE
the workflow
?
split the work into pieces, write each item on a card, and put
the card on a wall
Use named columns to illustrate where each item is in
the workflow
LIMIT
work in progress(WIP)
Assign explicit limits to how many items may be in progress at each workflow state
say 5, or 7...just what you think you could
comfortably see at a time
MEASURE
and manage cycle time
Average the time to complete one item, sometimes called lead time .
Optimize the processto make the cycle time as small and predictable as possible.
In a typical software world,
the scenario could easily be described in following manner
& a few days later...
KANBAN WHY?
CHANGE IS CONSTANT,
and you can't escape it...you should gracefully tackle it
to succeed in your life and processes.
we need such a way of working which keep us or our
team focused on what we are doing and allow to see and analyze the problems occurring and take necessary
actions. Kanban way of working
is awesome because
- is about understanding the whole process, defining and analyzing problem areas
- is about eliminating waste, inconsistencies and unreasonable requirements and increasing efficiency
- is about making positive, incremental and evolutionary change
- is about making workflow visible
- is about limiting the amount of work in progress
- is about evolving current processes for excellence
- is about disciplined execution and continuous innovation
- is a way to organize chaos through prioritization and clear focus
- can be applied to existing processes
- helps to see a problem forming
- helps not to lose clarity on what to do the next and what's most important
- helps to see the big picture
- respects people's ability to absorb change
KANBAN AROUND
what people are saying.....and doing
KANBAN isn't
"RAAMBAAND"
but it could be, if you start liking it
and for God's sake..stop thinking about the party afterwards :)
THE END
BY Aftab / aalam.in
code available at
https://github.com/one-aalam/go-kanban