In Jibility, each initiative on the roadmap is represented as a dot on a grid, and the dependencies between initiatives are shown as a line. The grid is arranged by stages (columns) and themes (rows). The stages are chronological from left to right, therefore, the initiatives on the roadmap are always delivered from left to right. A stage can have one or more columns of initiatives, and likewise, a theme can have one or more rows of initiatives.

In the following example, Stage 2 has two columns of initiatives, and also Theme B has two rows of initiatives.

Here are some general rules that govern how dependencies work in Jibility
​

1) An initiative can depend on one or more initiatives from an earlier stage and column. i.e. An initiative cannot be dependent on an initiative in the same column or a column on its right.
​

2) An initiative automatically depends on another initiative to its immediate left on the same row.
​

3) An initiative is independent when its dependency is explicitly removed.
​

4) An independent initiative will remain independent as long as it remains on the same row and in the same order

When initiatives are placed in the same row as other initiatives, their dependencies are drawn automatically. The dependencies are always from right to left. That is, the initiative on the right depends on the initiative on the immediate left.

For example, as shown below, initiative F is dependent on D, D is dependent on C and so on.

Dependencies between initiatives can be deleted by selecting the dependency line and clicking the Delete button. You can see below how the dependency from initiative C to B is deleted. Initiative C is considered an independent initiative.

An independent initiative is created when the dependency for that initiative is deleted. When an initiative is independent, it will remain independent unless it is moved to another row or its sequence order is changed.

To create or draw a dependency between two initiatives, drag and drop the initiative onto the other initiative where a dependency exists. In the following example, initiative B is dragged and dropped onto initiative C to create a dependency for initiative C on B.

NOTE, dependencies are always with an initiative in an earlier stage. ie. If initiative C is dependent on initiative B then B must be in a column on the left of the initiative C column.

Dependencies between initiatives on the same row are automatically drawn, but diagonally dependencies are drawn manually by dragging and dropping the initiative. You can see an example of a diagonal dependency between initiative D and C below.

When a horizontal dependency is removed, then that initiative is (horizontally) independent, and it will remain independent unless that initiative is moved to another row or its sequence in that row is changed. In the following example, Initiative D is independent. Adding Initiative C to the left of Initiative D or moving the initiatives (as long as the sequence is retained) does not automatically create a horizontal dependency.

In the following example, Initiative D is moved to another row and back. Note, Initiative E was not an independent initiative, so it automatically depends on Initiative C when Initiative D is moved. Also, when Initiative D is moved back, it is no longer an independent initiative, so it is automatically dependent on Initiative C.