I want to add: 2-3 sprints ahead is a GREAT begining goal for a team trying to get started with Agile.

Long term though let's set that bar higher :D

I do greatly appreciate my management and general company tech culture, they're great.

I agree with your stance here, because it's part of my point. I tend to see more people bitching about Agile itself and not management or their particular implementation.

The jobs where I was only given enough info to plan 2 - 4 weeks out were so stressful because I frequently felt like I was guessing at which work was important or even actually relevant. Hated it.

Turns out it's a skill issue ;p (on the management level to be clear). Folks, don't let your lazy managers ruin you on a system that can be perfectly fine if done right.

Why do people do this? There is neither a clubhouse sandwich or any fries in this image.

This looks like a great lunch but why is it so common to call things what they aren't? "Fries" isn't a shape. Apple sticks? Slices? Roughly julienned apples?

Put pork flavoured soy on whatever you want, but why the need to call it vegan bacon ya know?

2-3 sprints?! Y'all really flying by the seat of your pants out here huh?

My teammates and I have no trouble planning multiple quarters in advance. If something crops up like some company wide security initiative, or an impactful bug needing fixed, etc then the related work is planned and then gets inserted ahead of some of the previously planned things and that's fine because we're "agile".

I delivered a thing at the end of Q3 when we planned to deliver at the start of Q3? Nobody is surprised because when the interruptions came leadership had to choose which things get pushed back.

I love it. I get clear expectations set in regards to both the "when" and the "what", and every delay/reprioritization that isn't just someone slacking was chosen by management.

Configuration management and build automation are definitely worth the time and effort of learning. It doesn't have to be ansible, find which tool suits your needs.

Ah yes, the core definition of communism: a small farm offering a delusion of independence, which is run within a capitalist system.

The AJFA book is full of nothing but lies. Buy another blunt or something instead ;p

Bonus tip: Many distros make this info available on the cli by including a "hier" man page that you can read using the command "man hier".

There is literally an image of it happening in the linked article. Followed by more pictures that help make this make sense. That's how.

An absolute lack of consideration in regards to chat etiquette. Man now that I think about it, it's chat threads/notification in particular.

People who carry on side conversations in threads. You're giving everyone else who has participated in the thread the choice of "disable notifications for this thread and risk missing something relevant come back around, or get a notification for every single side message they're sending". Especially when someone is chiming in like 4 hours later. "Glad you guys got this sorted out". Yes, all 12 of us on-call people in this thread needed to get that message direct to our phones at 3a.m. 4 hours after the outage has been resolved. Thanks for that. Very fucking helpful. High value communication.

People who will not use threads. I don't need a new fucking notification every 20 seconds because you guys are deciding to have a chat about e-bikes. Make a goddamn thread or use a room made for chit chat, we're all on the same team, we're all in on-call positions. I'm paid to respond when this thing makes a noise. I am NOT comfortable muting the team channel.

It's addressed elsewhere in these comments, but +1 to folks who just message you "hi". Go get stabbed.

On the topic of notification fatigue:

People who will just not finish a thought.

Before hitting their enter button.

So they end up like doing this thing.

Where you get a notification every 15 seconds, because they are just absolutely addicted.

To their enter key I mean.

They are addicted to thier enter key.

their*

Oh.

I guess I could have just edited that message instead of sending the correction with the thing.

Asterisk? Asterisx? I forget what it's called.

LOL.

Anyway, that thing.

Also, when I'm helping you I am 100% going to stop what I am doing every time I get a message and read the message. There's no way for me to know whether or not you're messaging me "Oh never mind, I had a typo" or "here is more relevant info to make your work easier". That message may very well have immediate impact on what I'm doing, and affect the course I take. Of course I'm going to stop what I'm doing to read it. So maybe don't wait 5 minutes to send me the message "k" after I kindly, thoughtfully provide you with the status update "I think it's the fizzibob, let me verify in the logs real quick" of my own volition so that you are not only aware of what's going on, but don't have any question as to whether or not your question is still being looked at.

I don't remember the source, could have been anything from Stand Up Comedy to someone I know IRL, but I feel like they really cracked the "2 truths 1 lie" code.

• My name is Korthrun.
• I use Lemmy.
• I truly believe that this is a high value exercise that we should continue on with.

I am about 12 years into using Agile at my work place and I am about a decade in to being dumbfounded at the fucky implementations I read about in this type of post and it's comments.

We are never asked to turn our cameras on during any of our agile related meetings. In any meetings really. Some people do it, some people don't, I don't think I've ever had someone ask me to turn my camera on at work.

How do you even set a color for a meeting? Is that an outlook thing? Are you scheduling meetings in JIRA? I honestly don't even understand how one uses a color for a meeting. I would love an explanation of this :D

I've never once used a sticker, virtual or not, to tell others how I feel (at work). I'll assume this is a retrospective thing. We mention anything that happened in the last sprint where we think we as a team need to do one of:

• Start doing X
• Keep doing X
• Stop doing X

Then the team has a quick anonymous vote and if we have a majority we either start, stop, or continue doing X.

e.g. "The slack workflow we implemented in our public channel last week was used 15 times. We should definitely keep prioritizing moving FAQ type items to slack workflows"

Quoting from some of the comments

Its literally hand holding and baby sitting.

That's about your team and/or your teams leadership, not scrum.

checking in from the 45 minute “stand up” in which 10 people have their cameras on but only 3 people speak.

This is about your scrum masters inability to keep the meeting focused. We just do a straight up rotation, alphabetical by first name. Any time we are in danger of devolving into dev/engineering discussion our scrum master interjects and the conversation is saved for after standup or a meeting is setup depending on the topic. More often than not we give our updates and then say something like "JoBob I'll need some time from you sometime today to discuss how to integrate with the thingamajig" or "After standup I'd like to talk to the team about XYZ". We sometimes certainly have 3 people start trying to engineer a solution when someone says "I couldn't figure out how to schoop the woop, so I'm still working on that." but again our scrum master will say "Oh, JoBob is the schoop the woop SME, why don't we chat it out after stand up".

I hate that paragraph but I can't find a good place to break it up, sorry.

Most of the complaints I see (overall, not just in this post/comments) come down to really basic shit:

• Your scrum master is fucking terrible at their job
• Your team actually does behave like a group of toddlers
• Your manager is actually a micromanager and this is just another micromanaging tool to them
• You're bending your team/process to fit agile, and not bending agile to fit your team/process

I want to give two examples addressing my last list item.

First: We do not have stand ups scheduled 5 days a week. We found a cadence that makes sense for our teams work pace and our sprint duration.

Second: There's such a thing as tasks that take less time/effort than writing the associated JIRA story would take. My team has agreed to just not bother with a story in these cases. It fits our workflow better and as a group of adult human beings we accept that it's a waste of time/effort to write four paragraphs and a customer value statement for what essentially comes down to "type the number 70 into a form on a website and hit submit".

Again as adult humans we also try to be aware of and avoid abuse of this mentality, and make sure we aren't just doing mental gymnastics to avoid writing a story for something. When someone says "eeehhhh maybe we should throw a story on the backlog about that", we just suck it up and do it.

This shit is so easy, and so helpful, it's crazy to me how ridiculous y'all make the process.

edit: I will add that if you Masto-stalk me you'll definitely find me bitching about long stand ups. FWIW that's almost invariably when the scrum master is out and management has decided to run the meetings because none of the team felt like stepping up and doing it for a few days. i.e. it's our own fault when it happens to us.