Programming

17398 readers

106 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

338

What are your programming hot takes? (lemmy.ml)

submitted 1 year ago by 257m@lemmy.ml to c/programming@programming.dev

906 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] zurvan2@lemmy.world 9 points 1 year ago (1 children)

Almost everything in Scrum can be seen as protecting the team.

ONE example (there are many):

Problem: vague requirements

Solutions in Scrum:

Acceptance criteria on stories need to be clear
whole team grooms the story, everyone understands it and does planning poker to agree on costs. If the team doesn't all understand it, it doesn't get past this point
only fully groomed stories get into a Sprint and get worked on.
EVEN IF YOU GOT IT WRONG, you demo what you did every sprint, and the stakeholders can ask for additional work in a future story, reducing the cost of getting it wrong once.

[–] TrustingZebra@lemmy.one 2 points 1 year ago

Almost everything in Scrum can be seen as protecting the team.

Funny, in ny team it's the opposite. Our team leader is protecting us from the Scrum BS that is forced on us by upper management.