We do not have a real solution to this. It is a very good hint, we should think this over.

Hi There,
Is this something being reviewed?

Thanks,
Nik

If I understand you, there would be one project, but multiple sprints with different people at the same time.

Since this is uncommon for most projects, we would have to hide this functionality for most (new) users.

I like this idea, but I don't believe we could do this with our few resources, regarding its complexity.

I think that a big step into the right direction would be to enable moving Stories between Product Backlogs. I once talked to a company manager of a company, that has 4 Scrum teams that basically work on the same goal. They have one management team, one marketing team and two consultant teams. Alls Stories are initially placed in the management team's backlog and they redestribute the Stories across the other Teams.

We should definitely do more research on this topic.

Thanks Mrz.
But it is very common as far as I've worked.
We have single project and as the work is more we have multiple Scrum Teams working on it. (They all have same Sprint dates) But everyone has their own Sprint Backlog (although they share same Product Backlog)

Thanks again for taking it into consideration.

We also work with many teams on the same project. Currently we have to copy paste stories from one team PB in which we store all stories to other team PB. We mark stories with themes (teams names) in "main" PB to know who is working on which story. To mark as ACCEPTED we add proper emotikon and story has to be taken down in PB to not disturb in planning.
I agree with Nikhil that such situation is very common in larger companies. Copy paste text from all story fields, copying themes etc is not very user friendly way to handle this. Maybe there could be possibility to mark projects as "joined" and when marked they would share PB, themes, qualities and all common stuff, except SB?

To me it's pretty common to see multiple scrum teams working in the same project, thus working on a single 'Product Backlog'.
In Kunagi I could live perfectly well with an additional 'dummy' project only used to maintain the single 'Product Backlog'. Whenever a story may be associated to a specific team I could move that story into a team's 'Product Backlog'. This could happen during some backlog grooming session or during sprint planing part 1 or at whatever time appropriate.
Such a simple - move to project ... - function would help me a lot!

This sounds somewhat like the Scrum of Scrums concept. But I am not sure if moving the story is a good idea. This is because the master project usualy has "bigger" stories. The sub-projects usualy represent big stories (epics) from the master project as multiple smaller stories...