Best recommended way to maintain the sprints for different projects

[Durga P Chavali]

My team handles 3 projects which are interdependent on each other. Currently, we are using one sprint and handling the issues. I would like to know the best practice to handle the sprints as it often adds confusion in assigning the tickets.

[Mark Segall]

Hi @Durga P Chavali - If these are truly independent teams with individual scrum masters and/or individual sprint events, I'd recommend creating independent sprints. This eliminates the overhead that comes with multiple teams sharing the same sprint as they can start/complete without having to coordinate the action and they still get their individualized sprint reporting.

One common practice I've seen/used for sprint naming is this:

<Project Key> Sprint n (e.g. DEV Sprint 5)

[Durga P Chavali]

unfortunately, its the same team that works on multiple projects but has different start and end dates.

[Mark Segall]

Project start and end dates shouldn't matter.  If it's a single team working on the same cadence, the shared sprint is the best approach. 

However, I would question whether that team is achieving peak efficiency if they have to regularly context switch between projects.  Ideally teams should be focused on one project at a time.