> Scrum has no proper way of handling these activities. That's not true. A high-level user story will indeed require investigation, architecting, perhaps expe

> Scrum has no proper way of handling these activities. That's not true. A high-level user story will indeed require investigation, architecting, perhaps experimentation. So create tasks for each step and add them to the backlog! The 'planning' part in Scrum is mostly planning the sprint, i.e. what the team is going to work on during the next incremental period based on the tasks in the backlog. This is very different from thinking about how designing a feature, which is an activity that should be treated as a task. Working in short "sprints" also helps in the investigation and architecting phases, because the format is aimed at forcing small, incremental progress when a potential common pitfall of investigation and architecting is spending a lot of time dreaming up something and writing extensive documentation, which will end up being useless or performing poorly in the real world [1]. But you can use "sprints" along perhaps modeling tools to split this into shorter architecting-experimentation-refining cyles. Again, the common issue here is the superficial, literal reading of Scrum without thinking of the deeper point, which is what matters. [1] Remember the Agile Manifesto's point about "working software over comprehensive documentation" because of that.