Project goals can be written in the knowledge base, for example as a project charter. Every project participant can then read them and use them in their work.
A better way to record project goals is to list them in the "Features" module and then trace them to requirements: primary and system requirements. Use Story Mapping and Impact Mapping to focus the team on the project goals and to track progress toward those goals.
There are two main development workflows:
- Sequential (Kanban, Waterfall), in which each requirement (or group of requirements) passes through every stage in order, from design through documentation, and at each stage the project team members do their part of the work.
- Parallel (Scrum, Scrumban), in which work on a requirement is broken into tasks for each participant. Tasks can be done sequentially or in parallel. The requirement does not move to the next production stage until every task for it is done.
When managing the work, we therefore track:
- progress on user requirements, using the request board or the story board;
- and, when work on a user requirement is parallel, the task board as well, which shows progress on the tasks for those requirements.