🔴 Retrospective Examples for Fun & Effective Sprints

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

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

  • @SunilKhiataniHK
    @SunilKhiataniHK 7 месяцев назад +5

    This is a great video that describes the essential components of a retrospective and why the retro is useful

  • @zadoksworld8905
    @zadoksworld8905 2 года назад +3

    Daria is a great teacher

  • @shavonne4831
    @shavonne4831 2 года назад +3

    Lovely and amazing input as always!

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

    Thank you!

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

    Thanks for the video

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

    She is amazing ❤️

  • @Iseedstarz
    @Iseedstarz Год назад +2

    I think this is great

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

    Really admire the content around scrum, very useful, Thanks

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

    Thanks a lot! Good tips

  • @sabrinacz
    @sabrinacz 3 месяца назад +1

    1. Why you got together 7:00
    2. Ice breaker 7:15

  • @alebigna
    @alebigna 2 года назад

    Great video!

  • @NancyChanin-p1f
    @NancyChanin-p1f 11 месяцев назад

    Great video

  • @ibrahimsenan5273
    @ibrahimsenan5273 10 месяцев назад +1

    Thanks a lot for the great tips, I just have a question: After some time, retro meetings became more basic, the team got used to the method and the questions. I can feel some surface level answers. Is there a way(s) to make it more interactive, other techniques that can improve the retro meeting?

    • @kseniiapavlova3715
      @kseniiapavlova3715 2 месяца назад

      It might be not that simple. As advice, I'd start with figuring out what causes your team members to give basic answers. Is it really because of the format/techniques they have got used to? Or maybe there are some problems in the team or trust has deteriorated, and that's why they're not ready to 'go deeper'? Or maybe retrospectives don't lead to improvements, and team members aren't eager to participate because see little value. Or people are plain tired and overworked, they can't delve into deep and meaningful discussions. Or... whatever else. Once you have figured it out, then you can start solving the issue.

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

    How should retrospectives change as the scrum team matures? I imagine that icebreakers are great for new team that are familiar with each other but needed less as the team works more together.

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

      I think that they become much more to the point. But it may also lead to the team getting a bit stuck and having trouble getting to new ideas, which will require some updates to how the retrospective is run