• BehindTheBarrier@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    6 months ago

    Quick google shows that Kanban is a method. Mainlu around picking up things as the come, but also limiting how much can happen at once.

    The project I’m has a team that uses Kanban for the “Maintenance” tasks/development, take what is at the top of the board and do it. Adapt if higher priority things comes around, such as prod bugs. Our developments teams are trying to implement Scrum, where interruptions are to be avoided if possible during sprints. You plan a sprint, try to do that work, and can present it, and iterate when users inevitably changes criteria.

    In the meme, kanban does somewhat make sense, since getting armrests is never going to get a high priority as part of building a rocket. Scrum isn’t exactly right, but I can see where it’s coming from. They are all agile methods though.

    • bloubz@lemmygrad.ml
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      6 months ago

      Kanban is just a board. You can implement different things with it, like pull system, one piece flow, prioritizing, etc…