How do you best organize iOS and Android development of the same app in Jira?

Dear Community.

I am working on a project, where we are developing an iOS and an Android version of an app.

I am curious how to best organize this in Jira, and I would love your input, and hear of your experiences.

So far, I have made a custom field, which is required, indicating whether the issue relates to iOS, Android or both.

But here is where the way to do it, can go in several directions.

Are you splitting the work on a User Story level?

A User Story concerning feature X is made in two identical versions - one for Android and one for iOS. They have their individual estimate.

Are you splitting on a subtask-level?

A user story concerning feature X is made, and on a task level, you differ between iOS tasks, Android tasks and common tasks. The story has a common Story point estimate for the whole team, which contains both Android and iOS developers.

I can see pros and cons to both strategies.

Much of this debate is related to how you are running your agile teams (have you split them into Android and iOS teams), and not Jira directly, but since how I am going to organize it will be reflected in Jira, I am right now seeking inspiration.

I hope you can enlighten me :)

Best regards

Christian

1 answer

Hi Christian,

Interesting question, and I'd love to continue this discussion.

I have a question - is there any particular reason to use a custom field instead Components in JIRA? Components can be used to specify a given issue as iOS/ Android/ Both.

Splitting a user story into two stories is a good strategy in cases where development work associated with iOS and Android significantly differ. This is not to be a strict rule, but depending on the story team can decide it during iteration planning.

In other cases where development work associated with both platforms are much similar, you can use both components for the same story (multiple components for a single issue). In this case, just create Android/ iOS/ common subtasks.

Bottom line: Best strategy is a case-by-case strategy and it's up to the team to decide during iteration planning/ backlog grooming.

Please let me know how it goes.

Thanks!

Shaakunthala

 

 

If the choice is to use subtasks split into iOS and Android versions, is there a way of not showing the overall story on the board, which in our case is assigned to the team PM?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,296 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot