The 5 Biggest User Story Mistakes Teams Make

Поділитися
Вставка
  • Опубліковано 1 гру 2024

КОМЕНТАРІ • 5

  • @bgn9000fr
    @bgn9000fr 2 місяці тому +2

    I am taking away two things :
    1/ user stories are great to connect user need to solution makers then we have the slicing activity which is dedicated to organize just in time and just enough the delivery of the solution.
    2/ the activity of the team is not solely user demands. In that case other templates like job stories are more useful.
    Thanks Mike for this great video!

  • @bgn9000fr
    @bgn9000fr 2 місяці тому +1

    I am teaching user story slicing those days. I think this competency is more important than estimating. And from your video, I will pay attention to slice just enough just in time and avoiding bunch of small user stories to manage to early.

  • @TatavarthiAtWork-m1g
    @TatavarthiAtWork-m1g 2 місяці тому +2

    "since cavemen wrote the first line of code"😂 love the way you insert humour without changing. tone
    My quick take away is, user story doesn't need to always fit into the template of "as a, I want, so that". Technical PBI and job story are something that I will need to discuss with my team for them to practise.

    • @MountainGoatSoftware
      @MountainGoatSoftware  2 місяці тому +2

      Glad you like the joke! Sticking with a template when it doesn't make sense....well....doesn't make sense. I hope your team finds value in tech and job stories!