"Good morning" no longer a greeting

It's just a proof you've logged in for the day

(WFH)

* waking up
* "good morning"
* going back to bed

Ah yes just like the "stand up" at 8 am(aka lets talk nonsense for 20 minutes, then look at what we are meant to be doing) and another one at the end of the day (4pm). So much for "flexible" hours

@Lensflare

1. schedule a Teams message via Power Automate

2. stay in bed

@BordedDev > 'aka lets talk nonsense for 20 minutes'.

Pretty much my every standup ever attended. Most of the time, this was the 'water cooler talk time'.

Good thing I don't have to attend those dreaded stand-ups.

My previous work did this; The first week it was 50% of the people that responded. 2 weeks later only 25% and when I left, it was down to 4 people (including the 2 founders)

At my old company we had a #morning Slack chatroom. It was fun for the first few weeks but I eventually muted it forever.

My current place doesn't even have a channel for our team! People post everything in the daily stand meeting chat 😬

@BordedDev You have two?! One is bad enough ... I miss the old week status meetings from a decade ago. Better times.

@djsumdog 2? No, I have 3 ;P

2 for internal company and 1 with the client. Which also likes to have the other AGILE meetings every other day, so close to 4 or 5 per day ;P

And yeah miss the "check in once a week" styles as well

@BordedDev

Agile is the biggest lie of the dev world.

It would be useful if the only involved parties were devs, but since bosses and salesmen tend to allow client reps in planning, it turns out to be "do whatever shit client asks for, but more agile!"

In short, a shortcut to bothering you in ways they couldn't before.

@CoreFusionX Agreed there, I think that's something the original creators also say. Though I do like constant feedback, but let's be honest you'll generally only get "it's broken" until it's done and they want the whole thing changed

@CoreFusionX agile works if you work in teams who have a good separation layer between devs and clients.
Yes, those teams exist.
And yes, it doesn’t always work.

@Lensflare

I admit I'm also one of those people that make agile fail.

I've always been kind of the fireman dev, putting out fires here and there, and when you are constantly shifting your attention everywhere, the scrum master is delusional if he expects me to *also* pull whatever was in the usually already bloated sprint.