Vigile
SearchContents

How it works

The plan as a graph

A plan is items and the links between them. Hierarchy is a link, order is a link, and who works on what is a link.

A plan as a graph The project WEB contains the group WEB-001, Checkout, and the incident WEB-014. The group contains three tasks: WEB-002, done; WEB-003, in progress and assigned to agent1, which depends on WEB-002; and WEB-004, which depends on WEB-003 and waits. The task WEB-013, Launch, depends on the whole group and waits for it. PROJECT WEB Website relaunch GROUP WEB-001 Checkout 1 of 3 done WEB-002 Cart page done WEB-003 Payment form in progress WEB-004 Confirmation email waiting agent1 assigned to WEB-013 Launch waiting waits for the whole group WEB-014 incident Staging site is down in progress HOW TO READ IT contains: a project or a group holds a task depends on: the arrow points at what waits assigned to: who works on it
A project holds a group and a task. The group holds three steps. Two steps depend on the one before, the launch depends on the whole group, and one step is assigned to an agent.

Three kinds of item

  • A project gathers the tasks of one product or goal. It has a status of its own and, usually, a prefix of 2 to 8 letters, such as WEB, that starts the IDs of the tasks created in it.
  • A task is something to do. It has a title that says the outcome, a description that says how to tell it is finished, and optionally a reason, a type (a task, or a bug, an issue or an incident), a priority, a value and a size. The model lists the fields.
  • A user is a person or an agent. Tasks are assigned to users, and every change is recorded under the user that made it.

Nothing but a task is required. A task with a title and a description, in no project and no group, is a valid plan.

Items are joined by links. A link has a type, and the type decides what Vigile does because the link exists.

TypeReverse nameFromToWhat it does
containsis containedproject or tasktaskGroups tasks under a project or another task. A task can be contained more than once. A link that would create a loop is rejected.
depends onis depended on bytasktask or projectThe first task waits until the second item is finished: a task that is done or cancelled, or a project that is ready or cancelled. A link that would create a loop is rejected.
assigned tois assignedtaskuserSays who works on a task. A task can be assigned to several users.

Each link is stored once, under its forward name. Either name can be used when making or removing one: "A is contained B" is stored as "B contains A".

A link that would close a loop is refused when it is made, for "contains" and for "depends on" together: a task cannot be inside a group that waits for it, however long the way round is. The refusal shows the path.

Groups

There is no separate kind of item for a feature, an epic or a release. A task that contains other tasks is a group. Create the task for the feature, then create its steps with parent set to it.

  • Groups hold groups, as deep as the work is, and a task can be in several at once.
  • A group reports its progress: how many of the tasks inside it are finished, at any depth. So does a project.
  • A group does not close by itself. Whoever owns it sets it to done once its parts are done, and marking it done over unfinished tasks is refused.
  • Depending on a group waits for all of it with one link.

What the shape of the plan tells you

A plan that is held as a graph can be looked at whole, and the whole says how the work is cut, beyond how far along it is. Vigile does not rate a plan. It flags contradictions, and shows the rest for a person to read on the board and the graph, and for an agent to read through the same lists.

To noticeA person looks atAn agent calls
Work that belongs nowhereThe graph: a task in no group lies loose in its project's box, and a task in no project outside every boxlist_tasks with top_level, which lists the groups and the ungrouped tasks; a task's contained_in
Groups that are too wide or too thinThe groups with their progress, as "1/4 done" on a card, and the graph with its groups collapsedlist_tasks with top_level, then with parent to look into one group
Too many unrelated things in progressThe "in progress" column of the board: each card with its priority, who has it, and its group and projectlist_tasks with status set to in_progress: each task with its priority, assigned_to and contained_in
Work that hangs on much elseThe arrows of the graphdepends_on and waiting_for of each task, and get for its links in both directions

Order is never stored

There is no position of a task among its neighbours to keep up to date. Dependencies decide whether work can start. Among active paths, list_next_tasks compares priority from the outermost group through nested groups to the task; a task in several groups uses its highest active path. Where a path still leaves several tasks, whoever picks chooses with value and size.

IDs

IDs are given by the service: WEB for a project, after its prefix; WEB-012 for a task created in it, which keeps that ID when it is moved; USER-004 for a user. A number is given once, and so is a prefix, so an ID never comes to mean something else. The model has the details.

Reference