srinivaspendem
commented
2 months ago Hey @stultus we are working on updating how cycles are going to work, your use-case seems very different compared to what we are thinking about. Would you be open to connect with us and discuss more about how you plan to use Plane? If you are, then please block a slot convenient for you here - https://cal.com/plane-product-team/30min
stultus
Is there an existing issue for this?
Summary
We've structured our sprint cycles with three teams in a sliding window manner, starting a new sprint each Wednesday, each lasting for three weeks. This setup, which Jira supports, allows us to maintain maximum of a one-week lead time for prioritizing our backlog (but results in multiple sprints running concurrently).
I was evaluating Plane as an alternative to Jira, but the lack of support for concurrent Cycle is currently a blocker for us.
This issue may be related to #1260 , but the description of that issue doesn't align with what I am looking for, that is why I am creating a fresh issue, if this issue is a duplicate, feel free to close this.
Why should this be worked on?
In numerous organizations, sprints (or cycles) serve as a means for teams to prioritize their tasks. In our case, the utilization of sprints is tailored to individual teams rather than projects. Given that we have multiple teams collaborating on the same project, each adhering to distinct sprint schedules, having this capability would afford us greater flexibility in team management.