Using JIRA, can product owners manage functional areas span multiple platforms and SCRUM teams (any arguments for or against this approach)?
Is there an easy way to manage stories for epics that span multiple JIRA projects (one for each platform) or is there a better way to manage this type of scenario?
How can product owners effectively manage the lifecycle of new requirements at a product level even though execution is done by each platform's SCRUM team?
Heres the scenario:
There is one product that supports 3+ mobile platforms. Each platform has a JIRA project and each SCRUM team has their own sprint that pulls from the groomed platform backlog. There are multiple SCRUM teams with a minimum of 1 per platform but possibly more than one on each platform. The code base is largely nat0ive to each platform and teams work somewhat independently.
In general, all capabilities of the product will be the same across platforms with some differences in implementation based on the UI/UX or API's available. Currently there is one product owner per platform, and they consistently lack the time to effectively collaborate with their PO counterparts on story creation, planning etc. We end up having the same conversations multiple times, with the only difference being the platform in discussion.
Hi @Evan Hurst
I have come across this sort of problem multiple times. There are a number of ways it can be solved and here is the one I found easiest to work with for different users.
Step 1 is to create a filter of all your epics across the projects that reflect the 3+ mobile platforms.
Step 2 Create a Kanban board based off the filter from step 1.
Step 3. Train your POs to prioritise in the Kanban backlog - Any epic that is not in the To Do list is already prioritised and underway.
Nice to haves but not essential
Amend the workflow for Epics to have an additional stage eg. To Do - Ready for Work - In Progress - Done. Then your POs can confirm an Epic is complete and drag to the Ready for Work column to indicate to the platform teams that it is ready for work to be done, confirming the priority at the same time. The Scrum board for each team can then be updated to exclude any issues in "To Do" and they will focus on those that are Ready for Work.
I would also add a new custom field to Epics with a multi-select for the platforms. Once this is added you can use quickfilters to see which epics apply to a particular platform. Eg customfield is platform then you can use the JQL platform is 'Android' to identify all features related to the Android platform
Copy the filter from Step 1 and add the condition "OR flagged is NOT EMPTY" then use this as a report for Scrum of Scrums or Status meetings.
There are lots of other things you can do with this sort of setup but that is probably enough to get you started.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
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!
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