Organizing by ART vice by project in program

[Todd Cloutier]

We have multiple projects that touch one reconfigurable product, we'll call it "VX". So VX-A is a custom set of extensions for customer A, plus improvements to the back end of "VX" that all other projects can share, etc...

Running five parallel projects at present - and looking to step up to using your Program Planning software to improve planning of cross project tasks that can impact each other.

To complicate this further, we have a design team, back end and UX development teams, and a mgt/sys engr team all working on every project. So when I tried Program Planning, I was hoping to see a way to more easily pull all design tasks into an ART across all customer projects, all back-end dev into another ART, all UX dev tasks into another ART, etc... 

All of your examples show this kind of Functional grouping for the ART rows in PI planning, but in practice it looks like the rows have to be JIRA Projects as is.

Is this possible to do while retaining JIRA's "Project" structure divided by customer project?

[Teagan · Accepted solution]

Hi Todd, 

My name is Teagan and I am a Product Manager at Easy Agile. Thanks for reaching out via Community and for your interest in Easy Agile Programs. 

Each 'Team' in Easy Agile Programs is representative of an agile Board in Jira, not a Jira Project. 

To see each of your cross-ART Teams as their own swimlane in Easy Agile Programs, I would suggest the following:

• Create a new Project called 'Cross-ART Teams' or something to that effect
• Create a new Board for each of the shared teams you described above (Design, UX, Backend and Mgmt/Sys Engineering) where the board filter for each of your new Boards pulls in their specific tasks from the various Projects
• You may be using some Jira primitive today to differentiate those specific Team's work from the work of the other Teams (a component or a label for example)
• In that case, your new board filters may look something like Project in (ABC, DEF, GHI, JKL) AND label = Design 

We've also put together this doc which explains how to set up Team and Roadmap Boards in Easy Agile Programs which may also be useful.

I hope that makes sense, and of course I'd be happy to answer any other questions or clarify anything further. 

Thanks Todd, looking forward to hearing from you
Teagan Harbridge 
Product Manager - Easy Agile