Tool setup for SaFe

[Ain Tmyreal]

Hi,

We are about to take SaFe into use in our R&D. Our development teams (5-10 teams) are already using JIRA Agile, but now are planning on how to manage the common portfolio and program backlogs.

We need to have a clear portfolio backlog, which will contain epics for three different products. Then we need to have a program backlog, that will contain our features. Features will contain already quite detailed descriptions and definitions on how the feature should be implemented. We also need to be able to link the JIRA agile issues (storys, subtasks, bugs, etc) into features and epics to avoid writing everything down three times in different systems.  

In a team level we will use JIRA Agile. In the program level we might have to use Jama for detailed descriptions. But how about the portfolio then. JIRA Portfolio maybe? But how do these three interact with each other, does this setup support my vision of "write once, use everywhere"?   

So the question is, which tools or tool setup would you recommend for us?   

[Robert Leitch [ALM Works]]

There's a detailed description of a real-life JIRA SAFe implementation here - https://fschop.wordpress.com/2015/08/13/implementing-safe-with-jira-part-1/

[Timothy]

I am not sure about what Jama is but JIRA Portfolio integrates somewhat with JIRA Agile as it relies on issues created to fill up both backlogs.

You might be interested in this readup:

• http://blogs.atlassian.com/2015/05/see-jira-portfolio-team-uses-jira-portfolio/