Just-In-Time Software Manufacturing (True North PHP 2016)

Kanban is a method of managing processes that was originally pioneered in the automobile manufacturing industry in Japan. The Kanban method for managing software projects lowers the barrier to shipping working code and dramatically reduces the project management overhead for engineers participating in the process. In short, Kanban allows engineers and product groups to deliver real value at a very rapid pace, while still maintaining some sanity. Kanban is an excellent complement to the technical aspects of a continuous delivery process. We'll learn what Kanban means to your team, how to get started transitioning to it, and how to avoid common mistakes.

Transcript

1. Just-In-Time Software Manufacturing
   Josh Butts
   
   True North PHP 2016
   

   View Slide

2. About Me
   • VP of Engineering at Offers.com
   • Austin PHP organizer
   • I play competitive Skee Ball
   • github.com/jimbojsb @jimbojsb
   

   View Slide

3. View Slide

4. かんばん
   

   View Slide

5. Kanban
   

   View Slide

6. An abbreviated history of Kanban
   • Originated inside Toyota manufacturing - 1940s
   • Designed to manage inventory & component production
   • Applied for business / software process by David J.
   Anderson ~2005-2007
   

   View Slide

7. What problems does Kanban Solve?
   • “Just In Time” production
   • Flow control
   • Incremental change management
   • Communication through visualization
   

   View Slide

8. 3 fundamental principles of Kanban
   • Start with what you do now
   • Agree to pursue incremental, evolutionary change
   • Respect the current process, roles and responsibilities
   

   View Slide

9. Start With What You Do Now
   • You can start this today
   • No sweeping changes
   • No heartburn for managers
   • Start with step 0, figure out how to get to step 1
   

   View Slide

10. Agree to pursue incremental change
    • Incremental change lowers resistance
    • Keep building products while you build process
    • You won’t get it right the first time
    • Everyone can afford small changes
    

    View Slide

11. Respect the current process
    • Your current process is not 100% broken (I hope)
    • People fear change
    • Gain support, manage expectations
    • Be aware of emotional resistance
    

    View Slide

12. Encourage leadership at all levels
    • Kanban is about continuous improvement (“kaizen”)
    • Everyone can improve the process
    • People who execute it daily understand it best
    • Solicit new ideas from all levels
    

    View Slide

13. Lets talk about processes you already know…
    

    View Slide

14. Release&
    Review&
    Implement&
    Priori2ze&
    Plan&
    

    View Slide

15. Plan%
    Plan%
    Plan%
    Define%Sprint%
    Build%
    Build%
    Build%
    Release%
    

    View Slide

16. Plan% Priori)ze% Build% Accept% Release%
    Plan% Priori)ze% Build% Accept% Release%
    Plan% Priori)ze% Build% Accept% Release%
    Plan% Priori)ze% Build% Accept% Release%
    Plan% Priori)ze% Build% Accept% Release%
    Plan% Priori)ze% Build% Accept% Release%
    Plan% Priori)ze% Build% Accept% Release%
    Plan% Priori)ze% Build% Accept% Release%
    

    View Slide

17. How do we create order from this apparent chaos?
    

    View Slide

18. Visualize the workflow
    • You need some sort of Kanban Board
    • Can be post-its or notecards
    • Lots of great software out there
    • Commit to moving the cards real-time
    • Communication flows from the board
    • Honest & Transparent
    

    View Slide

19. Build a Kanban Board!
    

    View Slide

20. Pending'
    Task'1'
    Task'2'
    Task'9'
    Task'11'
    In'Progress'
    Task'3'
    Task'4'
    Review'
    Task'5'
    Deployed'
    Task'6''
    Task'7'
    Task'8'
    

    View Slide

21. Kanban Board Basics
    • Items are “pulled” from left to right
    • Set limits on key columns
    • Columns are ranked in absolute priority order
    • If items become blocked, move on to the next one
    • Everyone can see immediate absolute and relative priority
    

    View Slide

22. View Slide

23. View Slide

24. Mange the Flow
    • Goal is constant output from the process
    • Watch for bottlenecks
    • Measure facts of the system
    • Use metrics to improve choke points
    • Make policies explicit
    

    View Slide

25. Limiting Work-In-Process
    • Enforce constraints on the length of columns
    • How many tasks can one person actually do
    • Board must actually reflect status for effective
    communication
    

    View Slide

26. What metrics should you track?
    • Length of time an item is in a given state
    • Actual time spent on an item
    • Items exiting the process, per day
    • Number of blocking or dependent items encountered
    • Calendar time from beginning to end for items
    

    View Slide

27. How to move from Scrum to Kanban?
    • Keep your sprints, but review stories as they are completed
    • Remove sprint durations
    • Review progress
    • Define workflow columns & steps
    

    View Slide

28. Kanban enables continuous feature delivery
    • Features are defined and built as incrementally as possible
    • Automated tests can provide evidence against regressions
    • Acceptance of a shippable product is done in feature context
    • When features are accepted, they can ship
    

    View Slide

29. This fast-moving fluid process will change your life.
    

    View Slide

30. View Slide

31. Focus on pipelines instead of deadlines
    

    View Slide

32. Focus on features instead of releases
    

    View Slide

33. Intermix big and small scope items with ease
    

    View Slide

34. Eliminate wasteful estimation
    

    View Slide

35. Complete process transparency
    

    View Slide

36. Shift priorities instantly, without mutiny
    

    View Slide

37. Non-acceptance is not wasteful
    

    View Slide

38. This makes for happy engineers!
    

    View Slide

39. Upgrade your infrastructure for added benefits
    • Strive for a one-click deployment
    • “Hotfixing” is a thing of the past
    • Ditch your version numbers
    • Fail Forward
    • If you can’t deliver code to production fast, you’ve created a bottleneck
    

    View Slide

40. View Slide

41. Implications on your VCS model
    • I believe git-flow is too heavy for Kanban
    • Ditch your develop branch
    • Every item on the board is a feature branch off master
    • Master is golden
    • Recommend using a pull request process
    

    View Slide

42. Where Kanban may not work
    • Short client projects with one deliverable
    • Businesses that are driven by hard external deadlines
    • Software that is hard to release / deploy
    

    View Slide

43. Learn From My Mistakes
    • When we designed our board, we had too many columns
    • Things tend to languish in the middle
    • It’s easy to fall into a trap of too many “status columns”
    • Don’t forget to iterate
    

    View Slide

44. My Kanban Promise:
    We will break things.
    And then we will fix them fast.
    

    View Slide

45. Questions / Discussion?
    

    View Slide

46. I’d love your feedback:
    joind.in/talk/209ba
    

    View Slide