3 ms·
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
by 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 agoShrugs, 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.