This document briefly outlines the general process to follow when creating tasks on the Standalone - Kanban Board

Each task should contain two main aspects: the Goal and the Deliverable. A task can optionally contain additional information on useful resources or suggestions on methods of completing the task.

Goal

The goal of a task is, in essence, what the completion of a task aims to accomplish. It describes the task from an external standpoint. That is, what does this task provide to the end user (or the next level of abstraction)? It can also be thought of as the motivation or rationale of the completion of the deliverable.

Examples:

1. The task “Add a UI button press animation” may have the goal: Add an animation that plays on UI button presses, so that users receive improved feedback from UI interaction.
2. The task “Implement the probe() driver function” may have the goal: Implement the panel driver’s probing function, allowing the driver to perform initial setup after the kernel matches it to a device

Deliverable

The deliverable of a task is a concrete description of what the exact conditions are for the completion of a task. While the goal acts as rationale, the deliverable acts as direction. This ensures that the assignee of a task has a clear set of conditions that they can evaluate their progress against.

Examples:

1. The task “Add a UI button press animation” may have the deliverable: A clear button animation that plays when a button is clicked, or otherwise interacted with
2. The task “Implement the probe() driver function” may have the deliverable: A fully implemented probe() function within the driver that meets the function’s specification ([reference to specification)], and passes the appropriate tests.

Additional Information

Additional information can be included within the task to aid the assignee in its completion. The task creator is encouraged to, when possible, include things like:

• Suggestions on paths to follow toward the completion of the task. E.g. “you can start by creating a basic visual change, such as the button’s color, whenever it is pressed”
• Useful resources relating to the task itself, or the tools and technology used. E.g. “refer to the GDScript documentation on button press events”