5.3 Hierarchy

To make the most effective use of projects in AgileTrack, it is important to utilize the tree hierarchy capabilities of projects. For example, assume the following structure of components:

• Car
  • Interior Cab
    • Dashboard
    • Seats
  • Drive System
    • Engine
    • Steering
    • Suspension

Each component of the system may have associated stories and tasks. Because of the tree structure the relationship of components in the system, the tracked tasks can be explored in various ways. Obviously, if we need to know all of the work that needs to be done on the Suspension, we have a specific project to store those tasks. Where the tree structure becomes more useful and powerful is in inclusive grouping when viewing lists. For example, if we need to know all of the tasks related to the Drive System, the sub-projects are automatically included in the list.

When the number of stories and tasks being tracked in the system becomes large, project trees become very useful in understanding the scope of changes to sections of the system, and in turn allows good planning to be done.

Arranging the Tree

From the project view, notice that "Parent" field that is available on all products, components, and projects. The "Parent" field is used to associate a project with a particular parent project and thus form a tree structure. Simply select a project from the combo-box list to be the parent, or leave it blank if it is to be a root project or product. Once saved, the project list will adjust itself according to the new hierarchy.

When in an open project, the project's parent may be changed. By changing the parent project, the tree hierarchy the relates projects to one another can be changed. To change the parent project, simply select a different project from the "Parent:" combo box, or none if no parent is wanted. Before the change takes effect, it must be saved.

Next Section: 5.4 Status/Classification