• Like
Kanban -  improvements when you don't look for them
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Kanban - improvements when you don't look for them

  • 2,703 views
Published

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 …

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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,703
On SlideShare
0
From Embeds
0
Number of Embeds
29

Actions

Shares
Downloads
38
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. KanbanImprovements when you don’t look for them Pawel Brodzinski blog.brodzinski.com vsoft.pl @pawelbrodzinski
  • 2. Kanban in a pill
  • 3. Kanban improvements – emergentbehaviorNo prescription how to organize team or projectBig help with unveiling bottlenecksIncentives to improve the flow of workWith Kanban you don’t plan specificimprovements – they just emerge
  • 4. Areas of improvementsProcessoptimizationsThe way teamworksEngineeringpractices
  • 5. Example: optimized handoffs
  • 6. Following feature’s lifecycle time
  • 7. Optimization in handoff stages
  • 8. Example: ad-hoc swarming
  • 9. Typical problem solving approach
  • 10. Natural (on-demand) swarming
  • 11. Example: collective code ownership
  • 12. Bus factor = 1?
  • 13. Choosing tasks
  • 14. Final food for thoughtThese were only a few of possible examplesDon’t buy that uncriticallyYour team is uniqueWith proper approach improvements will come
  • 15. Kanban is like a box of chocolates…
  • 16. Thank you Pawel Brodzinski blog.brodzinski.com vsoft.pl @pawelbrodzinski