kanban - improvements when you don't look for them
DESCRIPTION
Kanban is probably the simplest commonly used approach to software development and project management. With such a simple tool, which in terms of required practices prescribes close to nothing, we don't expect much change of the way we work. After all we are advised to start without changing our process much when introducing Kanban. The interesting thing which is observed in Kanban teams in the long is something which is called emergent behavior - best practices which are seamlessly introduced without much conscious effort. What more it's pretty common that exactly the same practices were resisted when introduced by direct management action before. The session shows how Kanban, as an alternative to top-down approaches, can be used to support introduction of best engineering and organizational practices using a few real-life examples.TRANSCRIPT
KanbanImprovements when you don’t
look for them
Pawel Brodzinski
blog.brodzinski.com
vsoft.pl
@pawelbrodzinski
Kanban in a pill
Kanban improvements – emergent behavior
No prescription how to organize team or project
Big help with unveiling bottlenecks
Incentives to improve the flow of work
With Kanban you don’t plan specific
improvements – they just emerge
Areas of improvements
Process
optimizations
The way team
works
Engineering
practices
Example: optimized handoffs
Following feature’s lifecycle
time
Optimization in handoff stages
Example: ad-hoc swarming
Typical problem solving approach
Natural (on-demand) swarming
Example: collective code ownership
Bus factor = 1?
Choosing tasks
Final food for thought
These were only a few of possible examples
Don’t buy that uncritically
Your team is unique
With proper approach improvements will come
Kanban is like a box of chocolates…
Thank you
Pawel Brodzinski
blog.brodzinski.com
vsoft.pl
@pawelbrodzinski