Kanban Alone Is Not Enough

Preview:

DESCRIPTION

In terms of best practices and rules Kanban prescribes close to nothing which means that choosing it as your project management approach usually requires additional techniques in place to achieve a success. On the other hand specific set of practices used by a team depends much on a project and business environment which makes Kanban a good choice in variety of different situations.The session describes Kanban surroundings discussing different aspects related to software development, product management and project management in Kanban teams. Real-life scenarios used in presentation focus on areas which Kanban leaves open or customizable. Possible solutions are proposed which can be applicable in different situations.

Citation preview

Kanban is not

enough

Pawel Brodzinski

@pawelbrodzinski

http://blog.brodzinski.com

http://vsoft.pl/

Kanban is

a simple tool

What do you get

from Kanban?

And what do you

have to

deal with by

yourself?

Is that true?

Well, almost

Fine, Kanban is

not enough

What now?

Screw product

management

and you screw

the product

Dealing with

product backlog

The cost of

managing

backlog

Efficiently

delivered crap

is still crap

The best

approach

doesn’t exist

Adjust methods

for people

not people for

methods

When in Rome

do like Romans do

The dark side

of project

management

Fixed-price

makes me

sleapless

Estimation

Yeah,

we suck at that

How is your team

organized?

Fix your team

you’ll fix

much more

And what about

cross-

functionality?

Kanban is

not enough

Is it about

Kanban anyway?

There is no

silver bullet

Thank you

Questions?

Recommended