It's fun to hear such a familiar situation with workflow that causes people quit their jobs) It's unbelievable how companies copy those bad practices and people (developers) end up in the situation like you described. Instead of producing code that bring value to product, you waste your time attending all those meeting and arguing about scrum rituals - whether it should be a spike or an epic. Btw, I left my job because of similar reason. Scrum masters simply lost the feeling of the ground. The have been inventing new and new "scrum rules" until the team starting falling apart.
The problem is it's "horizontally integrated" into the entire industry. If you ever find a company actually caring about creating software, let me know :D
@@ainiro Great point. These methodologies are horizontaly integrated from the one side, but from the other side, I don't believe that stakeholders and top management are not aware about what is going on in the teams. There should be some formal/informal agreement between so called "scrum" people and top managent.
@@vasylvoina6663 You've got some great points, but you're trying to fix a broken process by adding more things to it. The process was broken because of too much stuff. Adding more stuff to it I assume will only make it more broken ...
I have a very similar experience, I learned BASIC programming from 10-11 years old, around 1984. My Laser 200, 16k RAM with a tape drive had keys with BASIC commands so that Shift-P would write PRINT and so on… Amazing times 😅
man the market in general for engr is fcked. esp for swe/hardware. the agile, scrum crap is BULL. it literally creates dumb jobs like scrum master etc where it is not needed. its only worth it as an undergrad degree for having the bare basic skills. even then as a highly skilled engineer im not looking to take on more headache. I can get a very similar salary as a technician while i wait to go for grad school.
