Best practice to manage 2 apps and one web portal as one project or 3?

[Thor]

Best practice to manage 2 apps and one web portal as one project or 3?

We are a software company, and we have 2 apps (both for Android and iOS) and one web portal.

What is unclear for us to how we could do best practice with this.

Since we have 2 apps and they are both for Android and iOS, and they are not updated at the same time and does not have the same features and bug to solve.

The web portal is connected to the apps, and therefore part of the project.

What we want to do is try to manage this big project as simple as possible.
What is your recommendation to do?

One Master Project with one active Sprint?
or 3 Project that all have each Sprint?

To zoom up, these 3 projects do does make one big project as the work all together as one.

[Carlos Khatchikian · Accepted solution]

Hey! I work in Atlassian and I answer the same question a couple of days ago here

You might want to take a look at it

[Thor]

Perfect @Carlos Khatchikian Thanks a lot I will take a look at it!

[Laki6999 Laki]

Web App proponuję jedna wspólną datę i czas dla tych samych systemów={meta}

[Hernan Halabi - Elite IT Consulting Group]

Hi @Thor sounds like it would be good to have one project per OS and another for the website. Why? Because of what you mention about the releases. This way, it's easy to manage each app version.

If you later want, you could have a single board that shows the 3 projects and you do the planning as a single thing

[Alexander Puentes]

Thanks for sharing @Hernan Halabi - Elite IT Consulting Group 

[Thor]

@Hernan Halabi - Elite IT Consulting Group  Thanks for this, and I believe that you are right. I started to create one board, but I see it will be a long list of ToDo and there you need to define what product has the issue each time, and more difficult to have the overview of each app.

Actually I did typo error in the question, it is 2 apps, not 3 apps, but still the same flow and overhead.