question Different Sprint schedules per ART in SPM forum

Different Sprint schedules per ART

art_jones — Wed, 29 Jan 2025 15:46:31 GMT

Is it possible for different ARTs to use different sprint schedules when using the same PI? We are running Enterprise Agile in SPM on Xanadu.

If I have a sprint setup for Team 1 (Apr1-Apr14), and then I attempt to setup another for Team 2 who follow a different schedule (Apr2-Apr16) then I get an error "Calendar entries should not overlap within a calendar". Is there a way to do this? Thanks!

Re: Different Sprint schedules per ART

brianlan25 — Wed, 29 Jan 2025 16:12:17 GMT

Unless something has changed in Xanadu. There should be a group dropdown on the planning board. If you change the group to Team 2 you should be able to create a separate sprint with different time lines.

Re: Different Sprint schedules per ART

Natalie Hunter — Thu, 30 Jan 2025 09:18:26 GMT

Hi Art

In SAFe it is typical that teams within the SAME ART sprint on the same cadence. There is some automation in SAFe that automatically generates a sprint for each of the teams in the ART when the PI is created. It might be worthwhile checking if a sprint has already been created for that Team in that specific PI, as there are checks in place to ensure that sprints do not overlap, even by one day.

Re: Different Sprint schedules per ART

art_jones — Thu, 30 Jan 2025 21:24:38 GMT

Hi Brian;

Thanks for responding! Yes, the UI for all of this changed significantly in Xanadu. Unfortunately as far as I can tell, that dropdown doesn't exist in the workspace.

Regards, Art

Re: Different Sprint schedules per ART

jordimsant — Fri, 04 Apr 2025 13:17:32 GMT

So the conclusion is that sprints cannot overlap within the same ART? I am facing the same issue

Re: Different Sprint schedules per ART

art_jones — Wed, 09 Apr 2025 19:46:19 GMT

If "Synch sprint with Agile Development 2.0" is checked in your Agile config, you cannot overlap sprints.

Re: Different Sprint schedules per ART

art_jones — Wed, 09 Apr 2025 19:47:46 GMT

My issue was that my Agile config was setup to synch with Agile 2.0 and this prevents overlapping sprints (by design).