HOCO B2B
Team tasks

Team tasks

Delivery briefs for every task of the plan, grouped by team member.

Every task of the plan has a brief: dates, effort, dependencies, subtasks, deliverables, acceptance criteria, the requirements, screens and API operations it covers, test measures and risks. The pages are generated from content/plan/tasks.json; the dates come from the scheduler, so they move when the plan moves.

Load per person

PersonRoleEffortTasksWindowOwns
AnisFull-stack developer · 1 FTE92.75 d5618 Oct 2026 → 04 Apr 2027Server (API), back-office dashboard, reseller web app, docs, DevOps
ImadMobile developer (Flutter) · 1 FTE76.25 d4718 Oct 2026 → 07 Feb 2027Reseller app and delegate app (Flutter monorepo)
AkramUI/UX designer · 1 FTE48.25 d3818 Oct 2026 → 01 Apr 2027Design system and every interface, design QA, training and store assets

Phases per person

18 Oct 2026 → 04 Apr 2027
Oct 2026Nov 2026Dec 2026Jan 2027Feb 2027Mar 2027Apr 202718/1025/101/118/1115/1122/1129/116/1213/1220/1227/123/110/117/124/131/17/214/221/228/27/314/321/328/34/4
Milestones
AnisImadAkramV2 scopePublic holiday◆ Milestone (hover for name)

How to use a brief

  1. Before starting, check the Depends on tasks are done and the linked requirements and screens are clear (definition of ready).
  2. Branch as feature/<TASK-ID>-short-description and put the task id in commit subjects.
  3. Work through the subtasks; record decisions in the decision register, not in chat.
  4. Demonstrate every acceptance criterion and the test measures before marking the task done (definition of done).
  5. Anis updates the plan status on the Thursday progress update; dates recompute from the plan.

On this page