Project goals can be stored in the knowledge base, e.g. in the form of a project charter. Thus, all project members can become familiar with these goals and use them in their work.
However, the best way to settle project goals is to list them in Functions module and trace them into the primary and system requirements. Use Story Mapping and Impact Mapping practices to focus your team on project goals and monitor their progress of goal achievement.
There are two main technological schemes of development:
- In sequential scheme (Kanban, Waterfall) each requirement (or group of requirements) sequentially passes through all stages from design to documenting, and project participants do their part of work on each stage.
- In parallel scheme (Scrum, Scrumban) work on a requirement is decomposed to separate tasks for each member of project team. Tasks can be performed sequentially or concurrently - a requirement will not reach the next production stage until all its tasks are completed.
Thus, we can control and monitor:
- the progress of custom requirements implementation (using the query board or the story board);
- in the case of concurrent work on a custom requirement, we can also monitor the task board which displays the progress of performing tasks relating to requirements.