3 ms·

Ah, you mean "Scrum of Scrums" where the people with at best half a clue lose that half. I distinctly dislike my job (and am looking elsewhere, interview monda

Ah, you mean "Scrum of Scrums" where the people with at best half a clue lose that half. I distinctly dislike my job (and am looking elsewhere, interview monday).

Xylakant 6y ago
Scrum - as pretty much everything - is bad when it’s done bad and can be good when it’s done good. I’ve seen both: 30 minutes of SoS where you’d wish for a pure caffeine infusion just to keep your eyelids up and daily SoS meetings with representatives from about 15 teams which were quickly adjourned most of the days when no cross cutting concerns needed coordination. It all hinges on the person responsible for the meeting.
- noir_lord 6y ago
  Shrugs, I don't have the authority to fix the problems yet I'm responsible for the fallout - hence I'm leaving as soon as possible. If you have a broken process the developers with options will leave, what is left is the developers who are either stuck for family reasons or simply unemployable elsewhere - a few years later you wonder why a simple change takes a week and a half and breaks things that should be totally unrelated and blame the process, so you do workflow re-org number #27 to see if you can fix it. It's hard to explain to a more senior manager that they are in fact the problem.
2sk21 6y ago
I used to dread the weekly scrum-of-scrums when I was a squad lead at IBM. Everyone used to recite their lines and yet none of the presented information ever seemed to register in people's minds. I would often get calls right after the scrum-of-scrums asking about exactly the things I had just presented
- MattGaiser 6y ago
  Scrum really just seems like a massive reporting framework, except that instead of written reports they have oral reports, which is basically just the same as having the server logs print to a speaker. You might get something useful if you’re around to hear it and are interested in that particular thing at that particular time, but otherwise it’s just a lot of background noise.

Ah, you mean "Scrum of Scrums" where the people with at best half a clue lose that half. I distinctly dislike my job (and am looking elsewhere, interview monday).

Xylakant 6y ago

Scrum - as pretty much everything - is bad when it’s done bad and can be good when it’s done good. I’ve seen both: 30 minutes of SoS where you’d wish for a pure caffeine infusion just to keep your eyelids up and daily SoS meetings with representatives from about 15 teams which were quickly adjourned most of the days when no cross cutting concerns needed coordination. It all hinges on the person responsible for the meeting.

noir_lord 6y ago
Shrugs, I don't have the authority to fix the problems yet I'm responsible for the fallout - hence I'm leaving as soon as possible. If you have a broken process the developers with options will leave, what is left is the developers who are either stuck for family reasons or simply unemployable elsewhere - a few years later you wonder why a simple change takes a week and a half and breaks things that should be totally unrelated and blame the process, so you do workflow re-org number #27 to see if you can fix it. It's hard to explain to a more senior manager that they are in fact the problem.

2sk21 6y ago

I used to dread the weekly scrum-of-scrums when I was a squad lead at IBM. Everyone used to recite their lines and yet none of the presented information ever seemed to register in people's minds. I would often get calls right after the scrum-of-scrums asking about exactly the things I had just presented

MattGaiser 6y ago
Scrum really just seems like a massive reporting framework, except that instead of written reports they have oral reports, which is basically just the same as having the server logs print to a speaker. You might get something useful if you’re around to hear it and are interested in that particular thing at that particular time, but otherwise it’s just a lot of background noise.