Bastardised Kanban

Retrospective and current status of my work with using directed graphs for planning software development work.

Presented at Schibsted Classified Media's "Superweek" conference in Barcelona.

Transcript

1. Bastardised Kanban
   Mårten Gustafson, Schibsted Media Platform
   

   View Slide

2. But first,
   some personal opinions…
   

   View Slide

3. Whiteboard
   

   View Slide

4. Digital whiteboard
   

   View Slide

5. Kanban
   

   View Slide

6. One main concern
   

   View Slide

7. No dependencies
   

   View Slide

8. No dependencies
   

   View Slide

9. Why dependencies?
   

   View Slide

10. Why dependencies?
    The road to shipping is paved with real world problems
    

    View Slide

11. Why dependencies?
    Scenario: X and Y is blocking A
    

    View Slide

12. Why dependencies?
    If A is most important, we must solve X and Y first
    

    View Slide

13. Why dependencies?
    If A is our end goal: X and Y are more important
    

    View Slide

14. Why dependencies?
    We rarely want to do X and Y, but must
    

    View Slide

15. Why dependencies?
    Be explicit about X and Y’s relation to A
    

    View Slide

16. Why Kanban?
    Buyer beware: personal opinions
    

    View Slide

17. Why Kanban?
    Because: DevOps
    

    View Slide

18. DevOps
    Development should manage Operations
    

    View Slide

19. DevOps
    Development should manage Operations
    (but not necessarily infrastructure)
    

    View Slide

20. Kanban & DevOps
    Development should manage Operations
    (but not necessarily infrastructure)
    

    View Slide

21. Why Kanban?
    Because: continuity
    

    View Slide

22. Continuity
    In business, technology, operations & process
    

    View Slide

23. My previous attempts
    

    View Slide

24. 2011 @ hitta.se
    

    View Slide

25. View Slide

26. View Slide

27. View Slide

28. View Slide

29. View Slide

30. View Slide

31. View Slide

32. View Slide

33. View Slide

34. 2012 @ Omni
    

    View Slide

35. View Slide

36. View Slide

37. View Slide

38. Publish
    Show related
    Search
    Write article
    (Presentation @ Omni 2012: 1/3)
    

    View Slide

39. Search
    Publish
    Show related
    Write article
    (Presentation @ Omni 2012: 2/3)
    

    View Slide

40. Search Publish
    Show
    related
    Write
    article
    User test
    Time
    Goal
    Tasks
    (Presentation @ Omni 2012: 3/3)
    

    View Slide

41. Current status
    Stoneboard
    

    View Slide

42. Stoneboard
    A Github based, and centric, approach
    

    View Slide

43. Milestones
    An overall thing to get done
    

    View Slide

44. Milestones
    “Integrate AFP newsire”, “Move to GHE”, “Support GIF and
    PNG”, “Migrate to Java 8”, “Support URL slugs”
    

    View Slide

45. Issues
    Tasks required to complete a milestone
    

    View Slide

46. Issues
    Design discussions, coding, refactoring, testing, scoping
    

    View Slide

47. No milestones for
    Continuous efforts
    

    View Slide

48. Not in milestones
    Bugs*, ops and one-off maintenance
    *unless clearly belonging with a milestone
    

    View Slide

49. View Slide

50. View Slide

51. View Slide

52. View Slide

53. View Slide

54. https://github.com/plan3/stoneboard
    

    View Slide

55. My work is predated
    (as usual)
    

    View Slide

56. Impact Mapping
    Mentions from Feb 2011, book published Oct 2012
    

    View Slide

57. Impact Mapping
    

    View Slide

58. Mikado Method
    First mentions around 2009, book published 2013
    

    View Slide

59. Mikado Method
    

    View Slide

60. CPM & PERT
    Critical Path Method, Program Evaluation & Review Technique
    Around 1950’s
    

    View Slide

61. CPM & PERT
    

    View Slide

62. CPM & PERT
    

    View Slide

63. CPM & PERT
    

    View Slide

64. Common theme?
    

    View Slide

65. Common theme?
    Directed graphs
    

    View Slide

66. Directed graph
    Time moves in one direction
    

    View Slide

67. Kanban as a graph
    Items ordered by priority and dependencies
    

    View Slide

68. Kanban as a graph
    Pull work from any beginning of the graph
    

    View Slide

69. View Slide