So my team (read: not the team at all) has decided that we are going to scrum. Someone ease tell me it's not as fucking tedious as it sounds. Sounds like it's just more meetings. Especially on this team which is actually already pretty agile. And the way our "certified scrum master" describes the retrospective sounds like it was designed by the type of shitlord PM that forces everyone to wear ugly t-shirts to the mandatory company barbecue for "team building". Please tell me he's just a terrible salesman.

Certified scrum master 🤣
Suits creating jobs for themselves again...

I love Scrum, but variations like kanban are also great. Its good to know what everybody is doing and what struggles there are in a team.

But if your team is already talking a lot it might be not needed. I work with kenyans and when there are elections they are a week or more gone. When its raining they dont have power. We have to know at all times what they are doing so if something goes wrong we can easily fix it.

@Codex404 the problem we have is that one of our teams doesn't try to engage, then blames us for not keeping them in the loop.

@projektaquarius ah, for most projects Ive worked on until now its just one or two teams. And the teams are mixed Dutch and Kenyan. It forces us to communicate

@Codex404 we have two teams as well. One of them are the software developers, the other are the system engineer. The system guys do the requirements, documentation, testing, and, from a high level perspective, architecture and design.

A sample conversation goes sort of like:
Systems Guy: hey did you change this module?
Me: not recently.
SG: yeah well I was working in the build from three months ago and something is wrong.
Me: well I will go look at it, but if you didn't notice it for 3 months it probably doesn't need to be high priority.
SG: actually we noticed 3 months ago we were just working around it.
Me: then why didn't you tell me three months ago when that was still fresh in my mind.
SG: we had other priorities.
Me: yeah, but you're supposed to flow software issues to us ASAP. Like we do with requirements and design.
SG: yeah but . . .

And then we have to do three weeks worth of work in 3 days.

@projektaquarius thats when scrum is great, standups daily so you have to tell whats wrong within a team. Having also scrummaster standups or just one scrummaster will make the two teams communicate at least once a day.

@Codex404 I mean I guess but it feels like punishing the whole class for that one jackass who doesn't do his homework.