Work with project tasks

Tasks are the pieces of work inside a project, shown on a board you can arrange to match how your team actually works.

• Add a task and give it a title, an assignee (Angi ansvarlig) and a deadline.
• Move it between columns as it progresses. The columns are the stages of your delivery process.
• ⟦Legg til kolonne⟧ to change those stages. The board should describe your process rather than you working around a board that describes somebody else's.

Fremdrift on the project follows from the tasks, so a board kept up to date reports itself and one that is not shows a project frozen in time.

Project tasks versus activities. A project task is delivery work, lives on the board, and counts towards the project's hours. An activity is customer-facing work — a call, a meeting, a follow-up — and lives on the customer's timeline. Keeping them apart is what stops delivery work drowning the customer history, and what keeps the project's hours honest.

Rough rule: if it is something you do *with* the customer, it is an activity; if it is something you do *for* them, it is a project task.

Break work down to something a person can finish. A task called "build the site" sits at the same column for six weeks and tells nobody anything. A handful of smaller tasks makes progress and blockage visible while there is still time to react.