this post was submitted on 20 Mar 2025
503 points (98.5% liked)

Greentext

5779 readers
1138 users here now

This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.

Be warned:

If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] TedDallas@programming.dev 27 points 1 day ago (1 children)

I bet he did PI planning for a week. Created 132 user stories. Decided on 2 week sprints at a velocity of 27 story points. Had daily 1 hour stand-ups. Weekly 2 hour sprint retro meetings. Per sprint a 3 hour sprint review meetings and a 6 hour grooming session with his cat. Not to forget the bi-weekly 2 hour sprint refinement meetings. And each sprint had a 4 hour backlog meeting on the potty. All by himself.

[โ€“] HereIAm@lemmy.world 3 points 1 day ago (1 children)

Are 1 hour (or anything close to it) really a thing that happens? No wonder people hate on scrum then. It's called a stand up because no one wants to stand still for more than 10 minutes and would like to get out of there asap. ๐Ÿ˜

[โ€“] Buddahriffic@lemmy.world 1 points 4 hours ago

I bet its looked something like:

  1. Developer in large company was frustrated with how much time was spent just communicating rather than doing.
  2. Comes up with a new system for effective communication and organization.
  3. Doesn't get much traction at current company because of inertia.
  4. Eventually starts his own company or joins a smaller startup where they are open minded because they haven't developed their own system for that yet.
  5. Less time spent communicating and organizing because it's a smaller company but confirmation bias gives credit to new system.
  6. Many companies adopt "proven" system.
  7. Large companies end up in same or worse boat because things still need to be communicated and disagreements still need to be resolved through discussion or orgazational power.

Though just a guess, since my only "experience" with "agile" has been seeing people complain about it. Plus experience working in a large enough team to have experienced the communication problem and to understand that a part of it is with so many meetings that are often irrelevant to the work any individual is working on, the default often ends up being tune most of it out until it's their turn to speak, so they often end up missing relevant stuff anyways and any big meeting is mostly a waste of time.