How to handle the dependencies for Jira stories?

[Sowjanya Mupparaju]

In our project we have some dependencies for completing a Jira story. That dependency is on other teams outside our Agile release train and they are not using Jira. Is there a way handle and maintain these external dependencies in a Jira story? 

[Ste Wright]

Hi @Sowjanya Mupparaju 

What tool are the other teams using?

Ste

[Sowjanya Mupparaju]

@Ste Wright : They aren't using Agile at all.. No tools.. 

[Ste Wright]

Hi @Sowjanya Mupparaju 

If there's no tool in use - I'd be encouraging them to use one, and positioning Jira as that solution.

Alternatively, I'd either...

• Get them to create stories, etc in Excel so you can at least load them into Jira
• Use either a Custom Field or a Component to identify issues being done by an external team, creating placeholders for them (at minimum) so you can track dependent work

But these are workarounds to the fact that realistically, using Jira directly would be the most beneficial approach.

Ste

[Christopher Maxwell]

I had to chuckle when I read this because SAFe Program Board uses stick notes for features, and red string for dependencies. Which is a great visual for the Program Board, but then, yes, how to keep everything up-to-date while implementing the program? That's why Jira, or a similar tool, is important.

I think @Ste Wright 's advice to recommend Jira and help them get set up on it is great. If you go that route, work to keep things VERY simple for starting. If they are going from no tool to Jira, basic is better. They can add over time. Better to get them set up and using a very basic/minimal Jira instance than set up anything more complex that doesn't get used.

Another option is to set up a board for them in Jira (very basic) and then have a weekly status meeting with their Project Manager/Scrum Master to get updates - and you can update the board for them.