When you think ‘project dependencies’ you usually need something more than Jira’s standard task links. BigPicture is valued for its three options in terms of dependencies: the best known is the arrow that connects two tasks in BigPicture’s Gantt chart. We call this type ‘strong dependency‘ because once a task catches a delay, the following, linked tasks will get rescheduled automatically.
Another case is the lesser-known ‘soft dependency‘, available in Board 2.0; the soft dependency permits ‘constructing roof before walls’; it visually alerts (turning from green to orange to red) that the schedule is impossible. While soft dependencies are still arrows that connect two tasks, they were designed to merely attract attention to certain relationships. They are not capable of rescheduling anything automatically. You can use a soft dependency to monitor a relationship.
The third option is Jira’s standard task links and how BigPicture builds on them. Let’s discuss how to use the three types.
Strong dependencies are what many project managers utilize daily. Phase 2 can only begin when Phase 1 has been completed, this sort of thinking.
Strong dependencies have been bread and butter in BigPicture/BigGantt’s Gantt chart, but we’ve recently added them to Board 2.0, too.
How do strong dependencies work?
- to create a dependency hover on a task card and then drag and drop a handler from one task to the other
- connect epics, stories, tasks, sub-tasks, as well as custom types, such as phases
- click the resulting arrow to edit the link. For instance, you can enable the ASAP mode or set up a mandatory lag time between the connected tasks
- four types of strong dependencies are available: finish-to-start, finish-to-finish, start-to-start and start-to-finish with the first being most popular
- you can map Jira task links to BigPicture’s strong dependencies: Jira administration > Add-ons > BigPicture technical configuration > General > Link. And this will work bi-directionally, so if you set up a dependency arrow in BigPicture’s graphical interface, you’ll notice a newly created issue link in Jira issue detail view.
The lesser-known soft dependencies appeal to the agile product management and are available in BigPicture’s Board 2.0. Few competing apps offer this type. While it’s still an arrow connecting two tasks, the soft dependency does not intervene to prevent an impossible schedule. All it does is it changes its color from green, to orange, to red to represent how feasible the relationship is.
The soft, cross-team dependencies were designed to encourage teams to talk to each other and for a project manager as a means to monitor certain dependencies.
How do soft dependencies work?
- to create a dependency hover on a task and then drag and drop a handler from one task to the other; click the resulting arrow to edit the link
- they are meant for agile and are available in the Board 2.0 module, both on the iteration and Program Increment level
- the soft dependency will not try to rectify an impossible schedule. The arrow will become green if the following task sits within any of the following iterations (or program increments if you set up a relationship on the higher, PI level). The arrow will turn orange if the tasks are planned for the same iteration or PI, and red – for impossible relations
- you can map Jira task links to BigPicture’s soft relationship: Jira administration > Add-ons > BigPicture technical configuration > General > Link. And this is a two-way synchronization, so if you create a dependency arrow in BigPicture’s graphical interface, you also get a new task link in Jira issue detail view.
Do you practice Scaled Agile Framework? If so, note how the BigPicture Board’s dependencies correspond to SAFe’s Red Strings.
Jira task links
Now let’s move to the third type, namely Jira’s native task links. How can you put them to work in BigPicture / BigGantt?
First, you could let them live independently of BigPicture. In this scenario, the visual BigPicture dependencies (strong and soft) are one thing, and the Jira links are another thing, and the two don’t interact with each other. Such a setup is rare with our clients.
Most users map Jira links to the visual strong or soft dependencies available in BigPicture and BigGantt. To set up such a mapping, go to Jira administration > Add-ons > BigPicture technical configuration > General > Link and choose from the options evident in the screenshot below. Be aware though: BigPicture does not visualize Jira links as such; you can map Jira links to the two visual dependency species (soft and strong) available in BigPicture.
BigPicture vs. competitors
Dependencies are among the most sought-after features of any project/product management app. BigPicture and BigGantt have had them for years, and we consider this functionality mature. BigPicture’s significant competitors – Portfolio for Jira, Structure, and Tempo Planner – while they may have strong dependencies, they could lack the soft dependencies. You should check on the current status with the respective apps.
On the other hand, Jira Align, another direct competitor of BigPicture, has developed dependencies – both strong and soft. But Jira Align is loosely integrated with Jira Software and is in a different price league compared to BigPicture.
If project dependencies are what you look for, then BigPicture, or BigGantt, might be the right choice.
See also: Managing cross-project dependencies.
Firstly, what is the true cost of PPM software implementation? Traditional vs. hidden costs. How to reduce the latter? Read more
Secondly, is Gantt chart an agile tool? Check three applications of modern Gantt charts in agile management.
Thridly, deciding between BigPicture and BigPicture Enterprise? Check 6 signs your organization should upgrade to BigPicture Enterprise.