• Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    which I’ll fire back and say should all be team decisions. Usually with my teams I try to persuade them to go sprints at first while they’re getting to know each other, but Kanban is always a possibility. Thing with Kanban is that you need a lot of trust within the team and a lot of honesty, things like “This story is really really stuck and idk what I’m doing wrong” vs letting it sit there holding up the WIP count.

    • jochem@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Oh, it should absolutely be the team’s decision and you’re also totally right that Kanban requires a more mature team. People indeed need to be able to recognise and ask for help when they’re stuck (which means being vulnerable, but also simply being able to formulate the right questions). People also need to be able to give feedback to their team members when they feel or see that someone is struggling or not delivering enough.

      To facilitate I always have some form of retrospective in my teams, even when doing Kanban. Sometimes only once every other month, sometimes every two weeks. Highly depends on the maturity of the team and customer.