On which sprint do you do what?
Once all the high-level goals are defined, your Developers and Architects will be involved in breaking down each wanted feature into concrete things that can be implemented within the time of a sprint. These are called User Stories in Scrum. Think about how long your sprint is, what needs to be accomplished and whether the team agrees that your separation makes sense given the time constraints.
After all of this, you now have a list of stories that Developers can tackle and know which technologies to use. Now you have to decide what to prioritize for a given Sprint.
This is done by the Product Owner in conjunction with the Scrum Master and whoever they choose to delegate this to. The goal is to select the most currently relevant stories for the current sprint and order them by relevance.
How this is done is subjective, but keep your team in mind when deciding these things and always communicate to ensure everything is on track.
If you're unsure of how to do this, maybe try using Planning Poker to estimate the size of your items with your team, to help decide what fits in the sprint.