Editing UNITA Agile Management Guide (section)

== Dependencies ==

Dependencies in project management are links between different activities of a project. Dependencies in UNITA should be managed by WP and TT co-leaders, with support from the local project managers, for the following purposes:
* identifying sensitive milestones in the project's timeline where dependencies may engender critical situations;
* avoiding delays or alterations in the results/ actions of one task due to conections to another task's results/ actions.
* avoiding parallel work in different teams for the same purpose;
* developing complementary actions that serve the bigger picture of our alliance's objectives where doubling an action may occur due to various reasons;
* ensuring clarity and collaboration among task teams' work, for a better understanding of the project's general objectives and the role of the Task objectives in this bigger picture;
* ensuring coherence in an experimental project in which actions may develop in unplanned directions, which may coincide.

Dependencies should be identified and tracked during the whole duration of the project. To that end, a specific tab is included in each of the WP's Gantt chart, following the model of the table below.  
There, each dependency is classified into one of the following categories:
# Finish to Start (FtS): Activity B can only start when Activity A is finished (sequential)
# Finish to Finish (FtF): Activity B can only finish when Activity A has finished (can run in parallel)
# Start to Start (StS): Activity B can only start when Activity A has started (can run in parallel)
# Requires: Activity A requires from Activity B budget, tools, expertise, information sharing

The table below allows to define the current status of the dependency, define possible related issues and propose solutions. This way, the TT can easily establish the specific actions with which the dependency will be handled.