this post was submitted on 01 Sep 2023
339 points (96.2% liked)

Programming

17504 readers
19 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

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 [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
339
What are your programming hot takes? (lemmy.ml)
submitted 1 year ago by [email protected] to c/programming
897 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 17 points 1 year ago (2 children)

SCRUM is good, actually

[–] [email protected] 15 points 1 year ago

The problem is that only 1 organization that I've worked for has actually tried to implement it correctly. The rest just say "yeah we do Agile SCRUM" but it becomes obvious quite quickly that no they do not. Just because we throw stories on a Jira board every 2 weeks and move them around does not make it SCRUM. I suspect this is partially the reason that some people have a negative view of it. They've only done "SCRUMfall" and assume that's all it really is.

[–] [email protected] 3 points 1 year ago (1 children)

Why?

[–] [email protected] 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.
[–] [email protected] 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.