Don’t Start with Kanban!
Marcin Czenko
Eindhoven,The Netherlands
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
All team members received an
introductory Scrum training.
No p...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
PO and the team received sufficient
coaching in writing User St...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Common excuses
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
We cannot have Product Owners
authorised to decide about budge...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
There is no way to give the team
appropriate space to work...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
It is impossible for a developer to be
associated with one pro...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
We have to keep the high reporting
level to senior management....
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
There is no budget for training and
coaching...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
We cannot align our business with
Scrum...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
KANBAN
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
It is a nice book.
“Product Owner role is an especially
egregi...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
“The Product Owner plays a crucial part not
only in bringing n...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Workflow
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Design Code Review Test Deploy
Workflow
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Because there is a false perception that Kanban
is all about w...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Organisation suffers from heavy
functional silos - heavy well-...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Design Code Review Test Deploy
CASE 1: Functional silos
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Design Code Review Test Deploy
Introduce queues
Not Good Probl...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Design Code Review Test Deploy
Limit the queue sizes
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Design Code Review Test Deploy
Get Rid of the queues
= Perfect...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
And what then ?
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
“Sequential development in a short
iteration does not work.”
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Cross-functional teams
Concurrent engineering
eXtreme Programm...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Which means you will have to get through
all this Scrum/XP stu...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
For many, however, functional silos is not
an issue (ie. they ...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Instead they start something best named
SrumBUT or KanBUT
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Introduction of the sequential
workflow in a potentially cross-...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
This might be a step back.
KanBUT #1 - consequences
By not wor...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Multiple access points to the team.
No Product Owner.
No Scrum...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Stakeholders are going directly to the
team members.
KanBUT #2...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
A group of engineers sitting in their proximity
but actually w...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Because there is no team, someone has to
synchronise that.Team...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Lots of Work In Progress.
KanBUT #3
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
One developer may be working on only one
story but looking at ...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
More and more technical debt.
KanBUT #3 - consequences
Lower a...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Experienced/senior members/architects
are the source of impedi...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Often THEY ARE USELESS: their only activity is to
keep themsel...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
If the organisation would satisfy some
standard Scrum constrai...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Conclusions
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Because there is a perception that Kanban is
all about workflow...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Avoid introducing a sequential
workflow to your engineering pro...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Do use ATDD and eXtreme
Programming for shortest cycle time.
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Don't forget that well-implemented
Kanban is Lean.
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Scrum can help you getting there.
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
All these "horrible" constraints that
Scrum puts on your organ...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Most of the organisations we saw (and we
saw quite a number of...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Functional
Silos
Cross-functional
feature teams
2 weeks
SCRUM
...
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Final Conclusion
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Start with Scrum
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Refactor to
Kanban
(or just Lean)
Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko
Acknowledgements
Quantum of Value Ltd.
Thank you !
Marcin Czenko
Eindhoven,The Netherlands
Upcoming SlideShare
Loading in …5
×

Don't start with kanban

1,477 views

Published on

These are slides from the talk during the Agile By Example conference in Warsaw, Poland, Sep 15-16, 2011.

Published in: Business, Technology, Travel
2 Comments
2 Likes
Statistics
Notes
  • @RobMyers64
    Hi Rob !
    I wanted Slide 3 to look 'crowded' with issues. I think it is my fault if it looks wrong. Don't hesitate to mail me if you want the original PDF.

    I do not have any blog post yet about the problems listed on slides #2 and #3. These are the problems I observed most frequently. Sometimes I summarize these three points as follows: 1) Business is separated from the team (like SCRUM is only for the development team and the rest is kept as usual), 2) The Scrum Team misunderstands the nature of planning as the means for inspection and adaption very quickly falling back to bad old habits, and 3) yes, complete lack of engineering practices. And I do not know how to emphasize this. It is hard to believe, but in the last year doing trainings in - one could say - top high-tech organizations - I could hardly see people doing solid engineering (so no TDD, no Continuous Integration as the most important two). On the other hand every developer knows how does it feel to have technical debt.

    Indeed, it could be good for me as well to summarize those issues in a blog post. I should have something soon.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • In slide #3, you address three of the top reasons Agile projects fail: PO/Story/Backlog issues, team space issues, and lack of XP engineering practices. Nice! For some reason, slideshare is not displaying it correctly. Do you have a blog post or paper written, particularly about this single slide?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
1,477
On SlideShare
0
From Embeds
0
Number of Embeds
41
Actions
Shares
0
Downloads
15
Comments
2
Likes
2
Embeds 0
No embeds

No notes for slide

Don't start with kanban

  1. 1. Don’t Start with Kanban! Marcin Czenko Eindhoven,The Netherlands
  2. 2. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko All team members received an introductory Scrum training. No prisoners in the teams. Product Owners selected and empowered. Scrum Masters selected and empowered. Pilot project selected. Scrum - steps you may need to take...
  3. 3. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko PO and the team received sufficient coaching in writing User Stories, estimating them and grooming the Product Backlog. Empowerment levels clearly defined. The team members received sufficient training and coaching in eXtreme Programming engineering practices. Informative workspace facilitated. Developers directly involved in hiring. Senior stuff trained in mentoring and coaching.
  4. 4. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Common excuses
  5. 5. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko We cannot have Product Owners authorised to decide about budget...
  6. 6. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko There is no way to give the team appropriate space to work...
  7. 7. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko It is impossible for a developer to be associated with one project only...
  8. 8. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko We have to keep the high reporting level to senior management...
  9. 9. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko There is no budget for training and coaching...
  10. 10. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko We cannot align our business with Scrum...
  11. 11. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko KANBAN
  12. 12. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko It is a nice book. “Product Owner role is an especially egregious error that trivializes the problems of product planning, product design, and requirements analysis and hides them behind a black-box role that encompasses at least as much complexity as the development part of software creation process.”
  13. 13. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko “The Product Owner plays a crucial part not only in bringing new products to life but also in managing the product lifecycle. Having one person in charge across releases ensures continuity and reduces handoffs, and it encourages long-term thinking.” It is a nice book too!
  14. 14. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Workflow
  15. 15. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Design Code Review Test Deploy Workflow
  16. 16. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Because there is a false perception that Kanban is all about workflow, many organisations believe they can avoid serious organisational changes by only optimising their workflow.
  17. 17. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Organisation suffers from heavy functional silos - heavy well-defined workflow. No functional silos Two most popular cases
  18. 18. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Design Code Review Test Deploy CASE 1: Functional silos
  19. 19. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Design Code Review Test Deploy Introduce queues Not Good Problem
  20. 20. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Design Code Review Test Deploy Limit the queue sizes
  21. 21. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Design Code Review Test Deploy Get Rid of the queues = Perfect Flow
  22. 22. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko And what then ?
  23. 23. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko “Sequential development in a short iteration does not work.”
  24. 24. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Cross-functional teams Concurrent engineering eXtreme Programming (Test Driven Development, Continuous Integration, Pair Programming, etc). Acceptance Test Driven Development Heavy stuff :)
  25. 25. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Which means you will have to get through all this Scrum/XP stuff first anyway before you can proceed to a more Lean process.
  26. 26. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko For many, however, functional silos is not an issue (ie. they don't have them). So they could start right from the start, right ? They don't... CASE 2: No functional silos
  27. 27. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Instead they start something best named SrumBUT or KanBUT
  28. 28. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Introduction of the sequential workflow in a potentially cross- functional teams. Even though there is no functional silos issue. KanBUT #1
  29. 29. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko This might be a step back. KanBUT #1 - consequences By not working for short sprints, sequential engineering demonstrates its limited efficiency, which means that further improvement will be significantly limited.
  30. 30. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Multiple access points to the team. No Product Owner. No Scrum Master. KanBUT #2
  31. 31. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Stakeholders are going directly to the team members. KanBUT #2 - consequences Tight relation between a developer and a stakeholder leads to further specialization of the developer.
  32. 32. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko A group of engineers sitting in their proximity but actually working independently from each other. KanBUT #2 - consequences No code ownership. It is not important who is doing the job but that the job is being done at a right time - this can be fully explored only in cross-functional teams.
  33. 33. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Because there is no team, someone has to synchronise that.Team Leads will feel very happy. KanBUT #2 - consequences
  34. 34. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Lots of Work In Progress. KanBUT #3
  35. 35. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko One developer may be working on only one story but looking at the whole system there are multiple changes happening at the same time. KanBUT #3 - consequences Conflict resolution.
  36. 36. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko More and more technical debt. KanBUT #3 - consequences Lower and lower internal quality. WAY DOWN TO HELL.
  37. 37. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Experienced/senior members/architects are the source of impediments. KanBUT #4 Afraid of being useless. They may try to convince you that a deeper reorganization is a bad idea.
  38. 38. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Often THEY ARE USELESS: their only activity is to keep themselves busy in an everlasting sequence of meetings so that it looks to everyone they do not have time.They are always busy and under strong time- pressure. Be understanding.Training/coaching in mentoring is the thing.They can be great coaches and mentors for less experienced members. KanBUT #4
  39. 39. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko If the organisation would satisfy some standard Scrum constraints, most probably they would be able to avoid most of the problems mentioned. Observation
  40. 40. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Conclusions
  41. 41. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Because there is a perception that Kanban is all about workflow, organisations blindly believe that by hanging a Kanban board they can bypass heavy organisational changes.
  42. 42. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Avoid introducing a sequential workflow to your engineering process. It is a step backward...
  43. 43. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Do use ATDD and eXtreme Programming for shortest cycle time.
  44. 44. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Don't forget that well-implemented Kanban is Lean.
  45. 45. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Scrum can help you getting there.
  46. 46. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko All these "horrible" constraints that Scrum puts on your organisation is a safety net that protects you. Use it...
  47. 47. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Most of the organisations we saw (and we saw quite a number of them) are not doing Scrum well. If you cannot adopt Scrum it may be just unrealistic to expect magic from Kanban.
  48. 48. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Functional Silos Cross-functional feature teams 2 weeks SCRUM Kanban Use Kanban here if necessary Towards a Lean process...
  49. 49. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Final Conclusion
  50. 50. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Start with Scrum
  51. 51. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Refactor to Kanban (or just Lean)
  52. 52. Agile By Example, Warsaw, 15-16 September 2011Marcin Czenko Acknowledgements Quantum of Value Ltd.
  53. 53. Thank you ! Marcin Czenko Eindhoven,The Netherlands

×