Dependency Management Use Cases in Jira Align

[#1]

Dependency management in Jira Align handles a couple of scenarios which are listed below.

Dependency between

• Teams within an ART(Agile Release Train)/Program

• Teams from different ART(Agile Release Train)/Program

• Scrum Team depending on Kanban Team within/different ARTs

• Kanban Team depending on Scrum Team within/different ARTs

• Team(ART1) and ART2 

• ART and Team(ART2)

• 2 ARTs

• Team/ART on External Entities like

  • Team not in JA

  • Team/Department not in Jira ( say Finance, HR..)

  • Team working in Scrum

  • Team working in Kanban

  • Team not working in Agile

  • Team not part of an organisation ( say a vendor/supplier)

All this can be visualized in Jira Align in one place.

Dependency Lifecycle(Happy Flow)

Step1 - Dependency is raised between 2 parties(requestor and respondent).

Step2 - Respondent confirms back to requestor on time proposition.

Step3 - Respondent can add work items via which the respondent team is going to resolve the dependency.

Step4 - Requestor and respondent can chat with each other regarding the dependency, add additional information links, also attachements

Step5 - Respondent confirms dependency has been sorted.

Step6-  Dependency appears as resolved.