Question: Let's suppose you have a team of 10 developers working on automation (RPA). They are working in 4 different, independent bots.

The PO comes with more opportunities for automation. These opportunities need to be reviewed, sized and an effort estimation need to be provided, i.e. a discovery session is needed.

How do you plan a discovery session for new work items, considering:

1) The PO and involved stake holders and SMEs definitely can not spend more than 1 day on such a session

2) The ideas for automation, based on previous experience, could be completed within 1-2 sprints (1 sprint = 2 weeks)

3) The development team is already busy working in the current sprint

Do you pull some of the devs working in the current sprint to participate on this? How do you handle that?

Answer: 
> 
> The development team is already busy working in the current sprint
> 
> 
> 

One of the principles in the [Scrum Guide](https://scrumguides.org/scrum-guide.html#artifacts-productbacklog) is that a Scrum team spends time during the sprint refining their backlog of work. This can represent up to 10% of the time in the sprint.

In your situation this backlog refinement would include discovery sessions, review, etc.

How the refinement is organised is up to the team.
A short answer I have found easy to implement in many different kinds of teams: Create a user story for the discovery session, and treat it like you do any other story. That is, rank it high enough in your Product Backlog to get into the sprint; estimate and task it out (if you do those things); add the developers who choose to be involved; and if that pushes a development story out of the sprint based on your method of ensuring "sustainable pace," so be it.