1. Planning Tasks and Milestones
1.1. The task name must begin with a verb
The name of any project task should start with a verb, emphasizing the action and the intention to achieve a result.
Example: Task: “Prepare the report” — verb “Prepare” + noun “report”.
1.2. The task name must end with a noun
The task name must end with a noun describing the specific outcome of completing the task.
Example: “Approve the technical specification”, “Approve the work plan”.
1.3. It is recommended to use verbs in complete form
For best readability and clarity, use verbs in completed form such as “Complete”, “Approve”, “Finalize”.
Example: Summary task: “Development of project documentation”.
Final milestone: “Documentation developed”.
1.4. The description of each summary task must end with a milestone
Each summary (grouping) task must include a final milestone that reflects the result of all included activities.
Example: “Requirements analysis completed”, “Project approved”.
1.5. A milestone name must start with a noun and end with a verb describing the result state
A milestone name begins with a noun to emphasize the object or result, and ends with a verb indicating the final state.
Example: “Requirements analysis completed”, “Project approved”.
2. Planning Interaction and Document Flow
2.1. All stakeholders must have defined interaction channels
Communications must be formalized and accessible to all project participants.
Example: Interaction matrix: customer — weekly meetings, team — daily stand‑ups, testers — reports in the system.
2.2. All interaction activities must be included in the project schedule
Any meetings, approvals, and information exchanges must be reflected in the project timeline.
Example: Regular status meetings should appear as tasks: “Status meeting (weekly)”.
2.3. Each interaction activity must have a defined type, template, and dates
Each activity must have a defined format, include supporting materials, and have specific time frames.
Example: Type: “Meeting”. Template: meeting minutes. Date: every Tuesday, 14:00.
2.4. Completion of work must be documented
All completed actions must have supporting documents that confirm the completion.
Example: After completing a task: Work completion act, Approval protocol, Testing report.
