Launch multiple sprints from a team project

[Guillaume HARARI]

Hi,

First, this is the strong context :

• We used to manage our project with Trello. We had more than 400 issues.
• We decide to use Jira instead with Scrum management
• Following Jira documentation instructions for transferring trello to Jira, we ended up with a team project Kanban (instead of Scrum beacause apparently we can't transfer Trello into Scrum template)
• On this new fresh kanban, we have activated the Scrum option on this project.
• It is a team project (not an entreprise one)

Our problematic :

We need to launch parallels sprints. We tried to enable "Parallels sprints" options in product parameters. But it doesn't work because it is a team project (not an entreprise one)

What we ever try :

We have recreated a new Scrum enterprise project in which we wanted to load our main kanban team project. But our project wasn't display in the dropdown (we think because it is a Kanban project)

Everything would be simple if we could tranfert our Kanban project (with Scrum features) into a real Scrum project.

Thank you in advance if you have any workaround or solution for us.

[Trudy Claspill]

Hello @Guillaume HARARI 

Welcome to the community.

To gain access to the Parallel Sprints option for your work, you will have to use the Company Managed project type (or "enterprise" as you have called it).

You will need to move your issues data from the Team Managed project to the new Company Managed project in order for the full functionality of a Company Managed project to work correctly. 

Refer to this document for information on migrating your issues from the Team Managed project to the Company Managed project. Note that there are limitations in this process, such as the loss of links between Epics and their child issues.

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

[Guillaume HARARI]

Thank you for your answer. It seems to have too much data loss for us. We keep investing.

[Alex Ortiz]

Did you import the issues as just stories or tasks?  I would recommend you start over and do the following:

Create a scrum based Company-managed project.  

Export your Trello work into a CSV file.  

At a minimum, you just need to have a summary and issue type so you import your Trello issues into Jira.  If you have additional fields, I would recommend you create those fields first, before you import anything that way you can map the fields when you perform the import.

Import your CSV file under the External System Import feature and map any fields from Trello to your new Jira Custom Fields.

This should automatically put all your issues in the backlog.  

From there, you can plan out your sprints.

A big question I have is why do you need parallel sprints?  It's a better practice to divide your issues into different boards (each with their own sprint) or set up multiple Jira projects (again, each with their own board/sprint).  

[Guillaume HARARI]

Thank you for your answer.

Following your questions :

I have to import issues as stories AND tasks.

CSV Export / import is a good idea. It doesn't seems simple : I keep this way in mind if other solutions won't be good for me.

I need parallel sprints for this reason :

One sprint for dev team

One sprint for UX/UI team

In a perfect world, our UX team have 1 sprint ahead. Like that, I can use same User Stories tickets

Sprint 1:

Ticket B for devs

Ticket C for UX

Sprint 2:

Ticket C for devs

Ticket D for UX

[Alex Ortiz]

I would personally recommend you have 2 different boards.  If you are going to pass the baton between 2 teams like that, I would also recommend your workflow allow for the issue to pass between the 2 teams.  You could then give your UX board (with the statuses specific to that board) and then the Dev team can have their own board (with their specific tasks).  

[Guillaume HARARI]

Thank you very much for your answer.

It helps for our thinking.

We are going to add steps for UX team on the same workflow, before devs steps.