Best Practice – Implementation of a design sprint with a Scrum methodology

The bigger the organism, the less mobile.

When starting up, it is not worth sticking to the established process, but reacting agile to changes.

From experience I realize that in the beginning it is worth spreading as much content as possible. I mean, insights, user story, analytics, strategy.

Later, they collide with reality – I mean hard facts – time and money.

Then it is worthwhile to predict potential problems in the design phase
Enter image description here

At each subsequent iteration, the team adapts and recognizes areas that can be improved.

In the beginning, it's worth being agile to adapt the process to your own needs and goals.

As growth grows, process creation is normalized and standardized, and results become more predictive-which is more useful in stable organizations.

Events are important in Scrum – I recommend to read:

The Five Scrum Events