List Types

Besides keeping track of start and due dates, one of the strengths of Track+ is the ability to manage several lists for a project. Lists can be categorized according to their type. Here are a few examples:

Problem Report	Somebody has a problem with something, rather unspecified. May be a know how problem, a user interface problem, or a bug.
Requirement Change	The agreed on requirements need to be changed to achieve the desired functionality.
Feature Request	The requirements need to be extended to achieve a new functionality.
Implementation Error	There was some problem found in the implementation, i.e. the requirements are correct, but the implementation is not.
Work Package	In a well managed project there exists a work breakdown structure with many work packages. It is very tedious for a project manager to keep track of the status of such work packages. Using this list and having each $RESPONSIBLE take care of the status of her work package the project manager can without a lot of effort obtain the actual status of his project and look for instance for late packages.
Action Item	There may be use for a rather unspecific list of action items at the project management level.
Milestone	Keeping a list with important milestones could be the shortcut version of keeping a list with work packages.
Risk	Project management without a current list of relevant risks is not really complete.

Note that for the different list types, not every state out of the set of possible states may make sense. You can define for each project type and list type a specific workflow.