If I am not wrong, Scrum groups user stories into sprints so the team focuses its resources to complete as much user stories as possible.
How flexible is the sprint planning according to Scrum ?, in theory a sprint should not allow to add new user stories to a running sprint, right ?, but what happens when an organization is doing both, implementing the product and developing the product's concept at the same time ?
For example, if business teams need to do experiments, which require the addition of new user stories to be implemented in a middle of a sprint, and such tasks should be released as soon as possible, for example if it is possible on the same day.
If the experiments do not compromise sprint planning from resources point of view, in fact there could be a "free developer" just focused on these business experiments, the integration of the experiment results could be merged into the project as tasks for the next sprint.
So, back to the question. Does Scrum consider situations like these or are there any other agile methodology that consider these and provides approaches to manage them ?