this post was submitted on 20 Mar 2025
510 points (98.5% liked)
Greentext
5806 readers
752 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:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
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
view the rest of the comments
I bet its looked something like:
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.
So the people behind the Agile Manifesto are far more experienced than some random dissatisfied dev. What I think most teams miss is that the only required meeting in the Agile manifesto is to regularly meet up to discuss what has worked and what hasn't the past few weeks, aka retrospective. If there are meetings or processes that don't work for a team and they don't change it after the next retrospective, then they simply aren't agile.