Work & boards
Themes to subtasks, Kanban boards and who may move a card.
Requirements say what must be true; work items are how you get there. CorPole keeps them apart on purpose: work links to the requirements it implements and the criteria it covers, but never replaces them. That way a story can be finished, cancelled or split without changing what the product must do.
Every work item belongs to an initiative; the initiative picker in the top bar filters the boards, work, planning check and forecast. Within it, the value tree runs from theme to epic to story or task to subtask; work packages are the delivery containers with owners, dates and budgets. Stories are work that involves development; tasks are work without it. Coding agents work on stories. Defects without a parent go to the solution's quarterly maintenance initiative.
The Kanban boards are where people and agents meet. An agent can propose work, but it starts only on items a person has moved to Ready; it moves them to In progress and Code review, and people verify and mark them Done. Gates can require that the initiative answers a demand before work is committed, that a Ready story implements an Authority requirement, and that Done has every covered criterion verified. When work is Done, the design changes it carries are applied to the solution's design.
This section explains the structure, the difference between stories and tasks, who may move which card, and how to take a requirement all the way from a set of proposed stories to a merged pull or merge request with your agent.
Articles in Work & boards
- GuideForecastWhen the remaining work is likely done, from the solution's own pace, how likely a target date is, what slows it down, what happens if one item goes first, and how finished work compared with its due dates.
- GuideFlowHow changes flow through the portfolio: how long they take from the request to done, how much of that time they wait, where they wait, and what is finished each week. Counted from the steps demands and initiatives go through.
- GuidePlanning checkBefore a planning session: which candidate items would pass the Ready gate and what each still lacks, and how much work each person and agent already carries.
- GuideWorkWork items are the execution side of an initiative: they bring its requirements to life and carry the changes to the solution's design. Requirements stay the authority; work links to them and never replaces them.
- GuideBoardsKanban boards for the work of the solution's initiatives — stories, tasks, defects and epics — and a review board for requirements. Every move is checked against the same rules as the forms. Initiatives themselves move on the Portfolio board.
- ConceptThemes, epics, stories, tasks and work packagesEvery item belongs to an initiative. Within it, a value tree says what you build and work packages say when and by whom.
- ConceptStory or task?A story involves development. A task does not.
- ConceptWho may move a cardAgents move work into progress and review. Ready, verification and Done belong to people.
- How-toBreak a requirement into stories with your agentThe agent proposes epics, stories and tasks with their links; you pick what to release.
- How-toImplement a story with your agent, end to endFrom a Ready story to Code review, with context, tests and evidence.