10 Reasons why being a Scrum Master Sucks

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

КОМЕНТАРІ • 9

  • @andrzejkowol
    @andrzejkowol 3 роки тому +3

    My list: 1. No creative work related to this work. 2. Your goal is to be not needed by the team - very destructive thinking about yourself and your role. 3. Doesn't matter what you do - you can't show the outcome of your daily work, it is not measurable. 3. Work with the people / working based on feelings instead of facts and information. 4. You're "alone" in the team. 5. There is no developer that likes constant meetings, and you re responsible for creating them and constant explaining why they are important. 6. Meetings, meetings, talking, talking and creating excel files and presentation = boring. If you think about changing your role from developer to SM - better think twice! I got back to development after 3 years of experiment with SM and I'm now feeling released! Development is much more fun and the outcome of my work is appreciated, finally! ;D

    • @CreativeSoulProjects
      @CreativeSoulProjects  3 роки тому +1

      Ha - nice list - like them a lot. I see many of those things too. Thanks for taking the time to comment.

    • @Elisabeth-hf1oe
      @Elisabeth-hf1oe Рік тому +1

      Yeah, if everyone refused to play the game of taking this shitty role, we'd all be happier

  • @philnesmith8635
    @philnesmith8635 3 роки тому +1

    Man, I really needed a laugh this morning. Score! Fun...and spot on! :)

  • @captainheretic
    @captainheretic 7 місяців тому +1

    Too bad people are only able to compare Scrum to Waterfall. How about Common Sense?

  • @rmichaelanderson
    @rmichaelanderson 3 роки тому +1

    Haha made me laugh!!!