Transcript
Page 1: Kanban Alone Is Not Enough

Kanban is not

enough

Pawel Brodzinski

@pawelbrodzinski

http://blog.brodzinski.com

http://vsoft.pl/

Page 2: Kanban Alone Is Not Enough

Kanban is

a simple tool

Page 3: Kanban Alone Is Not Enough

What do you get

from Kanban?

Page 4: Kanban Alone Is Not Enough

And what do you

have to

deal with by

yourself?

Page 5: Kanban Alone Is Not Enough

Is that true?

Well, almost

Page 6: Kanban Alone Is Not Enough

Fine, Kanban is

not enough

What now?

Page 7: Kanban Alone Is Not Enough

Screw product

management

and you screw

the product

Page 8: Kanban Alone Is Not Enough

Dealing with

product backlog

Page 9: Kanban Alone Is Not Enough

The cost of

managing

backlog

Page 10: Kanban Alone Is Not Enough

Efficiently

delivered crap

is still crap

Page 11: Kanban Alone Is Not Enough

The best

approach

doesn’t exist

Page 12: Kanban Alone Is Not Enough

Adjust methods

for people

not people for

methods

Page 13: Kanban Alone Is Not Enough

When in Rome

do like Romans do

Page 14: Kanban Alone Is Not Enough

The dark side

of project

management

Page 15: Kanban Alone Is Not Enough

Fixed-price

makes me

sleapless

Page 16: Kanban Alone Is Not Enough

Estimation

Yeah,

we suck at that

Page 17: Kanban Alone Is Not Enough

How is your team

organized?

Page 18: Kanban Alone Is Not Enough

Fix your team

you’ll fix

much more

Page 19: Kanban Alone Is Not Enough

And what about

cross-

functionality?

Page 20: Kanban Alone Is Not Enough

Kanban is

not enough

Page 21: Kanban Alone Is Not Enough

Is it about

Kanban anyway?

Page 22: Kanban Alone Is Not Enough

There is no

silver bullet

Page 23: Kanban Alone Is Not Enough

Thank you

Questions?


Recommended