I don't like Agile so much. Things are always rushed and you rarely ever have 30 minutes to discuss something in depth, not even in the retrospective meeting. Team mates too busy to discuss concerns. Sigh.

dead inside culture vibe

My incompetent manager from last job said we’re agile because we do a daily standup now. Bro was that nerve wracking

@Chewbanacas ooeeh, take it :p

@Chewbanacas Lucky we have 3 standups now

@BordedDev 3 a day? Why ?

@Chewbanacas Agency stand up (morning), client stand (lunch), agency checkout (afternoon)

It's annoying and I hate it

@jestdotty On the outside you're ablaAAaze-and-aliiive, but you're dead inside! Du, dudududududum, waahh!

@Chewbanacas Lmaooo. Taking the term literally is not very agile indeed...

Love Agile hate Scrum.

Nothing you described has anything to do with agile™

@hjk101 I have taken my agile certificate.

In this instance, as well as in PRINCE2:

- The ability to quickly adapt to team inquiries rather than letting everything syphon through a bureaucratic line.

- Pick up on concerns quickly.

- Agile behaviors: adaptability, collaboration. Individuals and interactions over processes and tools. Responding to change over following a plan.

- Agile practices: frequent review of progress (retrospective). "According to the Agile Manifesto, teams should regularly reflect on how to become more effective and adjust their behavior accordingly."

@CaptainRant don't know why you reply to me and probably downvoted. You are making exactly my point...

The complaint in OP should be handled in a retro. They are just going through some weird burocratic motions and use that as an excuse to not function as a team or have any meanings for making important decisions (as a team).
I don't care what methodology™ you throw at it this is never the goal.

@hjk101 I replied to you because you stated it has nothing to do with agile, when it does. I'm the original poster.

Given the agility behavior in agile, a retro is way, way too late and too costly to handle concerns in, especially when working on a user story. Everyone knows the average time stuck before you ask someone something is 4 hours to 1 day, depending, and in agile, if you don't voice your concerns in time, this is not appreciated because you impact the project's progress by not communicating effectively.

Sorry to hear you may think I downvoted you, but I didn't.

Of course you don't know what's going on in the team but you can make educated guesses. In this case they are too busy with other projects, but it's not that bad. My team always has a slot somewhere here or there to discuss a concern because they know we are a team, not an I. I don't know why you argue about being methodology-agnostic when I didn't mention a methodology but rather a (n)(agile) mindset.

@CaptainRant the way of working is something you bring up in retros, other learnings too. But for summer reason a lot of people are stuck with the idea that a daily scrum or stand-up is about 3 questions and that's all the communication that is needed.

I don't have a doctorate in agile or scrum however I've fought hard to make teams operate the way that works and I like. It's more kanban style and no freaking status updates. We schedule a meeting when we need it with people that makes sense. Nothing in the agile manifest is against that quite the opposite actually.

What you guys are doing is twisting it like terrorists and politicians twist religion.