allow the same sprint for more projects
What if a team is involved in more than one project and wants to share a sprint? I don't think the tool allows that. Why? As a workaround I have to duplicate the same sprint for each project but it is not "the same" sprint, and moreover it is a little frustrating.
Anonymous
shared this idea
Hi,
Thanks for the feedback.
Due to security and simplification reasons, we isolated projects, meaning each project has it’s own backlog and sprints.
Now adding the possibility of sharing sprint would essentially means that, users from one project could be responsible of items from other project. We have to analyze impacts on UI etc of opening up the sharing.
As a work around for now, perhaps you can add members from one project to another and vice versa, then they would be able to see both projects and perhaps need of duplication of sprint goes away.
Meanwhile, as said, we will analyze the impact of possibility of sharing sprints between projects.
Best Regards,
Yodiz Support Team
Finland
-
Jonson Chatterley
commented
Any update on the impacts of allowing multiple projects per Sprint? I have a small team that is shared across numerous projects, and it is overly cumbersome to manage one sprint per project.
-
Ralph Moog
commented
...I heavily want to support that idea, since otherwise the application would not suit our organization and would be useless.
-
Derrick
commented
Hello. I came across this thread in a search and in the exact same situation. I divided up projects to cover off huge major initiatives from various dept heads. However some people will work in multiple project components in a single sprint. The current setup doesn't allow this to happen. Instead I need a different way to prioritize requests from different groups (while preserving where the request came from) and allow resources to be assigned to different initiatives in the same sprint. Ideas here?
-
Hi Jon,
Understood your point and we will try to find some work around for this use case.
Best Regards,
Yodiz Support Team
Finland -
Jon Anders
commented
Adding members to both projects still doesn't make it possible to add user stories from more than one backlog into one single sprint, which is what we need.
Our use case:
We are developing a software product which always need extensions and customizations when delivered to one of our customers. We want to maintain one backlog for our product and one separate backlog for each customer. When implementing a new feature for a customer, this usually involves some items from the product backlog and some items for the customers backlog, but we want all this in one sprint.