How to structure Jira Advanced Roadmaps for cross-functional game development sprints?

[Web Marketing]

Hi Atlassian Community,

We are currently restructuring our Jira Software setup to better manage cross-functional game development workflows across art, sound design, backend APIs, and mobile UI integration teams.

When managing fast-paced game updates—like tracking restaurant asset pipelines, appliance upgrades, and event feature deployments (similar to how mobile strategy sites organize documentation when users check these resource guides for level progression data)—we struggle to map dependencies cleanly between creative art sprints and technical engine builds.

Current Challenges:

1. Art vs. Code Velocity: Art assets (3D models, UI animations) follow an iterative design review cycle, whereas engine code follows standard 2-week Scrum sprints.

2. Dependency Mapping: Feature epics frequently stall because art dependencies in Jira are not dynamically blocking developers' sprint backlogs.

Questions:

1. Do you recommend using separate Jira projects for Game Art and Game Engine development linked via issue links, or a single project with component-based swimlanes?

2. How do you track dynamic asset pipelines using Jira Advanced Roadmaps without cluttering the main release version board?

Would appreciate any insights or workflow templates from game production managers in the community!

[Nikola Perisic]

Hi @Web Marketing 

This is the problem: We struggle to map dependencies cleanly between creative art sprints and technical engine builds.

• Which work item types would be used for game art and which for game engine? - if different are needed, new Jira spaces would be more appropriate.
• Same thing goes for workflows, screens

Mapping dependencies would be easier between two boards.

Furthermore, since you have things like backend, API and more and components would be a solution to handle grouping work items into one entity. If you would need to have different people as different component leads, new Jira space would be more suitable.