This website contains age-restricted materials including nudity and explicit depictions of sexual activity.
By entering, you affirm that you are at least 18 years of age or the age of majority in the jurisdiction you are accessing the website from and you consent to viewing sexually explicit content.
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.