xkanban v2 (ALE Bathtub III)

XKanban
XP, Kanban and timeboxing

giovedì 20 ottobre 2011

Who am I ?

• Web developer @ideato
• 3 years of “serious” php ( +2 of playing around)


XP Values
Communication

Respect Simplicity

Courage Feedback
http://www.extremeprogramming.org/


XP Principles
Humanity
Accepted responsibility Economics
Baby steps Mutual beneﬁt
Quality Flow

Failure Opportunity
Reﬂection Redundancy
Diversity Self similarity
Improvement
http://www.extremeprogramming.org/ http://martinfowler.com/bliki/PrinciplesOfXP.html

Where were we?
2 Main Stream Projects
Customers
Requests 2 Developers
user stories tasks +
emergencies bugs
1/2 Developers
http://www.ﬂickr.com/photos/kainet/288519656/

The Emergency Ward
Management
projects and clients “assistance”
long term planning 1 Developer

http://www.ﬂickr.com/photos/st3f4n/2489961263/


Problems
Spread of knowledge on projects

2 Main Stream Projects The Emergency Ward


Long term projects Bugs and requests of
Focus on new ex-“long term” projects!
functionality

Problems
Different workﬂows


VS


Iterations Bugs, small tasks, emergencies, a
Clean planning every week bit of customer care
Difﬁcult planning


Problems
“When can we do this?”: planning, resources, negotiation


VS


“Next week?” “Emm... maybe next week?”


Problems
“How much work can you do in a week?”
“Can you measure it?”

Story points? Ideal working days?
hours/man?



From... to...
Customers 2 Main Stream Projects
Requests
2 Developers
+
The Emergency Ward 1/2 Developers

Management 1 Developer
Sales
Contracts

“Account”
Customer care
Customers
Requests
user story, task, bug
Developers


SOLUTIONS
Spread of knowledge on projects

Kanban
Pick the ﬁrst in
the “to-do” list!
If needed, ask
someone to help
you.


SOLUTIONS
Different workﬂows

Kanban
Everything is on
the kanban!


SOLUTIONS
“When can we do this?”: planning, resources

Kanban Timeboxing Track and planning
“Full for the How long it Plan daily
next N takes from based on what
weeks?” “request” to you have
“done”? measured
(Lead time)

SOLUTIONS
“When can we do this?”: negotiation

PROS
Planning an unique ﬂow
Finer granularity than iterations
Can establish effort on projects weekly
CONS
Harder to plan many project in one ﬂow
Daily change of to-do list may happen


SOLUTIONS
“How much work can you do in a week?”
“Can you measure it?”

YES,YOU CAN!



SOLUTIONS
Bring you problems to ligth!
Measure your lead time
(How log it take to release value?)

Bugs discovered in QA
(Weak tests? Customer expectation not matched?)

WIP (work in progress)
(How many activities can you do at the same time?)

Bottlenecks
(Kanban can show you were activities are stuck.
You should ask yourself why.)

Non-standard workﬂows
(“Why is it not in kaban?”)


OK...but...
Is everything this beautiful?


OK...but...
Is everything this beautiful?

Unfortunatly, no :(


We found that...
Sales
Contracts

Customers Customer care “Account”
Requests user story, task, bug Developers


...changing is not bad!
Customer1
Customer2 Contracts
Developers
Customer3 Customer care Team I

New
Customers First contact Sales

Customer4
Developers
Customer5
Customer6 Contracts Team II
Customer care


Questions?
#phpday

Filippo De Santis

fd@ideato.it

twitter: @ﬁlippodesantis


References
http://www.poppendieck.com/
#phpday

Kanban and Scrum - making the most of both
http://www.infoq.com/minibooks/kanban-scrum-minibook

http://en.wikipedia.org/wiki/Kanban


xkanban v2 (ALE Bathtub III)

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Andere mochten auch

Andere mochten auch (15)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

xkanban v2 (ALE Bathtub III)