Criticism of Scrum

[mstakh.i.mom.i]

According to the study, the main problem with Scrum is the stability of the requirements over two weeks. Every two weeks was too slow for the tech companies. A working product should be delivered more often.

Now there is an approach where all developers are responsible for testing freight forwarders brokers email lists their own code. There is no longer a need to wait days for feedback before the code can be transferred to production. Now the study says that this has been tried, but the two-week sprints and the numerous Scrum rituals became the next problem.

Scrum was getting in the way of daily delivery. Scrum, in short, is sprints, i.e. defining tasks at the beginning of the sprint, working on these tasks during the sprint and presenting the results at the end of the sprint. Many of the teams used Kanban for this because this way of working was too slow. According to the study, the tech giants dropped most of the rituals that go with Scrum. It was now just a question of: what are we currently working on and what is important in the next sprint!

This meant that there was no longer a need to present to the product owner, which often resulted in a 2-3 day delay. There were many product owners, and thus there were quick and short feedback cycles. The study says that this can be achieved primarily by platform teams (infrastructure and developers). With a first-class infrastructure and ready-to-use platforms, teams can focus on their actual work goals instead of worrying about setting up the infrastructure or ensuring a service is compliant.