JIRA Tutorial 2023 | New Project, Adding Fields to Issues

Поделиться
HTML-код
  • Опубликовано: 8 сен 2024

Комментарии • 7

  • @Paul_uk_3000
    @Paul_uk_3000 Год назад +1

    Great video- very helpful

  • @florianbonnet
    @florianbonnet Год назад

    Thanks!

  • @RVictorN
    @RVictorN Год назад

    For large scale enterprise, how would you split the teams and Jira ?
    Would you set teams to focus just on run type activities, maintenance type work and some other teams to focus on change type activities ?
    So team A,B focusing just on run and team C,D focusing on change type activities?
    Or would you give team A some run & change so that the colleagues get a bit of variety and don’t get fed up with doing just run work ?
    Same Q for Jira, would you have teams just using a kanban for run and scrum boards for change ?

    • @AgileStateofMind
      @AgileStateofMind  Год назад

      Hey Nicolae, depends. Are there enough people for both? What's the structure, the PO, the Team Lead's knowledge. But most of all, what do the teams say? I think it is a great question to ask the teams and let them tell you what can be the easiest and best setup for them. When we treat people as mature, they usually chose the best options and take ownership for their decisions.

    • @RVictorN
      @RVictorN Год назад

      @@AgileStateofMind completely get the sentiment around involving the teams and get their feedback. I’m talking here about cca 50 teams so over 500 colleagues in total
      We might be able to run some feedback sessions but from your perspective what would an ideal setup look like ? Would you look to split the teams or do a mix & match?
      Thinking if I split let say Team A into just run and team B into just change some members of Team A after a while might get bored & demotivated if they only do run work so we should also allow that flexibility that after a while teams can move between change run like swapping colleagues from B to A etc

    • @AgileStateofMind
      @AgileStateofMind  Год назад

      @@RVictorN that is quite a number! It is hard to asses by knowing so little. I would try to find a few team members, team leads etc who are passionate about the topic and poll them on what they think. Thwy could provide you with insights to make your decision