All posts
Jackie Peng
Author·Originally published May 10, 2023 · Updated Oct 7, 2026
Agile workflow from Backlog to Done with a feedback loop to learn and adapt

Agile Workflow: Steps, Diagram, and a Practical Example

An agile workflow is the agreed path a piece of work takes from an idea to a useful result, with regular feedback that changes what the team does next. It makes work visible, defines when an item can move forward, and helps people finish small pieces of value before starting more.

Start with five states: Backlog → Ready → In progress → Review → Done. Then agree on the rules between them. These are example states, not a required Agile framework: a team handling support requests may need different steps from a team building a product.

This guide includes a worked onboarding example, a workflow rules table you can copy, and a way to keep the goal, tasks, and acceptance evidence together in AFFiNE.

Editorial note: The example below is fictional, not a customer case study or a measured productivity result. AFFiNE publishes this guide and offers the workspace discussed in it. Framework explanations are linked to their primary sources; diagrams are editorial illustrations, not product screenshots.

What makes a workflow agile?

A task board shows where work is. An agile workflow also explains how work moves, what counts as finished, and how learning influences the next choice. The Agile Manifesto emphasizes working software, collaboration, and responding to change while still recognizing the value of plans and documentation.

For a small team, make these decisions explicit:

  • Value: Who needs the result, and what will change for them?
  • Work items: What is small enough to finish and evaluate separately?
  • Movement: What must be true before an item enters or leaves a state?
  • Capacity: How much work can be active without overwhelming review?
  • Feedback: Where will findings go, and who decides what happens next?

A board with many columns but no agreed rules can still leave people waiting. Start with the decisions, then choose the tool.

An agile workflow diagram you can adapt

Five example workflow states, their exit rules, and a feedback loop from Done to Backlog
Figure: A sample workflow. Review is a work state for checking an item; it is not the Scrum Sprint Review event.

Copy this table into a shared document before setting up your board:

StateWhat belongs hereRule for moving forward
BacklogIdeas and requests that are not yet selectedExplain the user need and decide whether the item is worth preparing
ReadySmall, understandable items the team could startAgree on acceptance criteria, resolve starting dependencies, and check capacity
In progressItems the team has startedComplete the work and attach enough evidence for someone else to check it
ReviewItems undergoing agreed quality and acceptance checksPass the checks; if a check fails, return the item for rework with the reason recorded
DoneItems that meet the agreed completion policyPreserve the evidence and capture feedback that may create or reorder future work

Blocked is a condition, not progress. In this example, leave a blocked item in its current state and record the blocker, next action, responsible person, and next check. It still counts as work in progress. Moving it into an uncounted parking column would hide demand on the team.

For board setup details, see the Kanban board guide. This article focuses on the rules and feedback that make the board useful.

Scrum, Kanban, or a different workflow?

Agile is not a synonym for Scrum. Choose a working approach based on the kind of demand you receive and the decisions your team needs to make.

QuestionScrumKanban
How is work organized?Sprints with a Sprint GoalA defined workflow with explicit policies and controlled work in progress
What helps you choose it?A team benefits from planning and inspecting progress toward a shared goal at a regular cadenceWork needs to flow through a service or process as capacity becomes available
What must be made clear?Accountabilities, goals, artifacts, and a Definition of DoneStart/finish points, states, movement policies, WIP control, and flow measures
Can it be combined with the other?Kanban practices can help a Scrum team understand flowKanban can be applied to an existing way of working, including Scrum

Use the Scrum Guide and Kanban Guide for the frameworks themselves. The example in this article is a lightweight workflow design, not a claim that a five-column board implements either framework in full. If you choose Scrum, the sprint planning board with a six-week timeline shows one way to keep a Sprint Goal, backlog, and retrospective on one page.

In Scrum, the accountabilities are Product Owner, Scrum Master, and Developers. A certified scrum master may bring training to facilitation, but certification is not a substitute for understanding your team's actual constraints. A Sprint Review inspects outcomes with stakeholders; it is not a mandatory release gate. Useful increments can be delivered before it.

How does this differ from a traditional project plan?

A plan describes intended scope, sequence, dates, and resources. A workflow describes how individual items move through work. Teams often need both.

A Waterfall model generally organizes delivery around sequential phases; agile approaches emphasize smaller increments and adaptation through feedback. That does not mean traditional projects cannot change or collaborate. Changes may instead follow more formal controls. For a deeper comparison, read Agile vs. Waterfall.

How to build an agile workflow

1. Define an outcome and a boundary

Use a result someone can observe. For the fictional example in this guide: help a new workspace member understand how to complete their first setup task. The first piece of work is a clearer setup instruction, not a redesign of the whole onboarding experience.

Record what is included, what is excluded, and what you still do not know. If you need a starting structure, use the brief in the project planner guide.

2. Break the outcome into small work items

Write items that can be evaluated separately. “Improve onboarding” is too broad. “Rewrite the first setup instruction and check whether a reader can follow it” has a clear output and a useful check.

Keep acceptance criteria beside the item. For example: the instruction names the next action, matches the available interface, and lets a reader complete that action without additional explanation. These are proposed checks, not evidence that an improvement has already happened.

3. Agree on states and movement rules

Use the table above as a starting point. Decide where work starts and finishes for measurement purposes. Here, work starts when an item enters In progress and finishes when it reaches Done.

For this example, Done means the agreed checks pass, the change is available to its intended audience, and the evidence is linked. Your team may define a different boundary; write it down so that “finished” means the same thing in the board, reports, and conversation.

In Scrum, an item's acceptance criteria describe its particular expected behavior, while the Definition of Done describes shared quality requirements for an Increment. A passed checklist for one item does not replace that wider quality standard.

4. Set a starting limit on active work

For the fictional three-person team, try a maximum of two items in In progress and one in Review. These are illustrative starting limits, not an industry benchmark. Revisit them when actual waiting time and capacity show they are unsuitable.

When Review is full, help finish or unblock existing work before pulling another Ready item. Do not raise the limit simply to make the board look less constrained.

5. Make checking and feedback part of delivery

Agree who will check each item, where the evidence belongs, and how feedback becomes a decision. A screenshot, test result, reviewed document, or observation note may be appropriate, depending on the work.

Keep feedback distinct from unfinished acceptance work. A failed required check means rework. A new idea discovered after an item genuinely meets the completion policy becomes a new backlog candidate.

6. Review the workflow itself

At a regular check-in, ask which item has been waiting longest, what is blocking it, and which rule needs to change. Record one specific improvement and check its effect later. “Communicate better” is hard to act on; “name the reviewer before starting the item” is testable.

Worked example: a blocked onboarding task

The following names, IDs, rules, and sequence are illustrative. They show how to make decisions visible, not how an actual AFFiNE team performed.

Illustrative onboarding workflow with O-01 blocked in progress, one other active item, and one item in Review
Figure: The blocked item remains in In progress and counts toward its limit. The illustration is a conceptual board, not an AFFiNE interface.
FieldExample entry for O-01
NeedA new member needs to know which setup action to take first
DeliverableRevised first-step instruction in the onboarding page
Person coordinating the itemMaya; Leo checks the instruction against the interface
Acceptance criteriaCorrect action and destination; a reader can follow the instruction without additional explanation
Current stateIn progress — blocked
BlockerThe draft references a button label that has not been confirmed
Next actionLeo checks the current interface and records the label before the next team check-in
Evidence to attachReviewed copy, interface reference, and a note of the reader check
Completion policyChecks pass, the instruction is available to its audience, and evidence is linked

The decision: Keep O-01 active and visible. With two items already In progress and Review at its limit, the team helps clear the review or resolves O-01's question instead of starting a fourth active item. They do not mark O-01 Done just because the copy is written.

The next loop: Once the instruction passes its checks and is available, suppose a reader asks a new question about inviting a teammate. Record that as a candidate O-04 with the observation that prompted it. Compare it with other needs before starting it. The finished instruction stays Done unless the feedback reveals that its original acceptance conditions were never met.

This connection between evidence and the next decision is the useful part of the workflow. A colored status alone cannot provide it.

Download the blank work-item CSV or download the illustrative example CSV. Open either in a spreadsheet, or copy the fields into your existing workspace. These are plain tables with no automation, formulas, or account requirement.

Keep the goal, workflow, and evidence together in AFFiNE

AFFiNE combines Docs and an Edgeless whiteboard. The product pages describe structured writing, tables, and movement between document and canvas views. You can use those building blocks to keep a workflow's explanation close to its working notes.

The setup below is a suggested manual arrangement, not a tested click-by-click walkthrough of a particular app release. It does not assume automatic WIP enforcement, workflow transitions, notifications, or flow-metric reports.

Connect the goal brief to workflow rules, the O-01 work item, acceptance evidence, and a new feedback decision
Figure: Keep one work-item ID across the brief, visual plan, and evidence so teammates can follow the decision. These are suggested document sections, not software features.

Start with the goal and visual plan

Use Edgeless to discuss the outcome and draw the relationships between the work. Keep the five states and their movement rules visible. Add O-01 to the visual explanation without turning the canvas into a second, conflicting task register.

Write the scope and rules in Docs

Record the goal, excluded work, start/finish boundaries, and completion policy in a document. Put the acceptance criteria beside each item, not only in meeting notes. If a rule changes, record the reason and date.

Maintain one task table and an evidence trail

Use a table for ID, work item, state, coordinating person, acceptance criteria, blocker, next action, started time, finished time, and evidence reference. Maintain those fields manually in this suggested setup. If your team already tracks delivery elsewhere, keep that system authoritative and use AFFiNE for the brief and visual context.

Check current whiteboard layouts for additional planning arrangements. The best setup is the one your team can keep accurate during work, not only at kickoff.

Original planning illustrations from the 2023 article

The original article illustrated the same three planning activities below. They are retained as historical examples; interface labels may differ from current AFFiNE. Use the rules and fields above for the refreshed workflow.

Original AFFiNE illustration accompanying the brainstorming and goal-setting step
Original goal-setting illustration, retained from the earlier edition.
Original AFFiNE illustration accompanying the project introduction and scope step
Original scope illustration; the earlier article used the name Paper mode.
Original AFFiNE illustration accompanying the task-prioritization table step
Original task-table illustration, retained as a planning example.

Measure flow and decide what to change

The Kanban Guide's flow metrics distinguish work that is active from work that has finished. Use consistent start and finish boundaries:

MeasureMeaningA useful question
Work in progress (WIP)Items started but not finishedAre we starting more than we can finish?
ThroughputItems finished per unit of timeHow much work actually completed this week?
Work item ageElapsed time since an unfinished item startedWhich active item needs attention now?
Cycle timeElapsed time from an item's start to its finishHow long does completed work take through this workflow?

For a simple illustrative calculation, an item started Monday at 09:00 and finished Wednesday at 09:00 has a cycle time of 48 elapsed hours. If your team reports working hours instead, define the calendar and label the measure accordingly. Do not mix the two units or count only hands-on time while excluding waiting.

Use several observations before deciding whether a change helped. A single fast item does not establish a trend, and differently sized work items make raw counts hard to compare. Flow measures should guide improvements to the system, not rank individual teammates.

SymptomCheck firstTry this adjustment
Items accumulate in ReviewIs a reviewer available, and is the required evidence clear?Name the reviewer earlier and help finish the oldest review before starting more work
Items stay active for daysIs the item too large or waiting on a dependency?Split future items around smaller useful outcomes; give current blockers an explicit next action
Urgent work constantly interruptsWho decides urgency, and what gets displaced?Record the tradeoff and agree on a limited exception policy
Done items repeatedly returnAre acceptance criteria and shared quality requirements clear?Tighten the relevant check and attach evidence before completion
Retrospectives change nothingIs the improvement specific enough to try?Choose one rule change, name an owner, and revisit it at the next review

Common questions

Does every agile workflow need sprints?

No. Scrum uses Sprints; a workflow using Kanban can manage continuous flow without adopting Sprint timeboxes. Choose the approach for the work and retain its essential practices rather than borrowing only the board labels.

Is a Kanban board enough to make a team agile?

A board makes work visible. It does not automatically establish customer feedback, useful increments, shared quality standards, or a way to adapt decisions. Add explicit policies and a feedback routine that the team actually uses.

How do you start without adding too much process?

Choose one small outcome, copy the state rules, and follow one item from Ready to Done. Keep the acceptance evidence and the next decision with that item. Add complexity only when a real coordination problem requires it.

Start by copying the rules and downloading the work-item table. If your team needs a shared place for the written brief and visual plan, try AFFiNE. For product updates and community discussion, use GitHub, Discord, or Telegram.