Tracking Work (WIP)
The WIP (Work In Progress) view is the heart of AgileNotes: a grid of your tickets with a cell for each day, where you record what state each ticket was in. Those daily statuses drive cycle time, throughput, flow efficiency, and almost every chart.
For a Scrum team it shows the sprint backlog across the sprint timeline; unfinished tickets roll over to the next sprint. Use Refresh to sync from your APM tool (Jira, Azure DevOps, etc.) or Add Ticket for manual entry.
For a Kanban team it shows the team’s tickets across the active flow window. Tickets persist independently and are sliced into each window’s date range — there’s no rollover between windows.
Status shortcuts
Click any daily cell and type a shortcut, the full label, or a partial match — all case-insensitive. The cell resolves when you tab or click away.
| Shortcut | Label | Flow type | Counts toward cycle time? |
|---|---|---|---|
| r | Ready | Waiting | No |
| p | Dev | Active | Yes |
| c | Code Review | Waiting | Yes |
| qr | QA Ready | Waiting | Yes |
| q | QA | Active | Yes |
| uat / ua | UAT | Waiting | No |
| m | Merge | Waiting | Yes |
| so | Sign-off | Waiting | No |
| b | Blocked | Waiting | No |
| D | Done | Done | Yes |
| x | Descoped | — | No |
| * | Not in Sprint | — | No |
| - | No work / Holiday | — | No |
Columns (all teams)
| Column | Description |
|---|---|
| SP | Story Points — the effort estimate |
| RO | Rollover — cycle-time days carried from the previous sprint/window |
| Work Item Age / Cycle Time | Total active days in the system. Shown bold once Done. |
| Assignee | Team member responsible |
| Notes | Click to add a ticket-level note |
Metrics — Scrum
| Metric | Description |
|---|---|
| DWIP | Average tickets in Dev per day |
| WIP | Average tickets being worked (Dev + QA + Review) per day |
| Cycle Time | Average days from first active status to Done |
| Throughput | Number of items completed in the sprint |
Metrics — Kanban
Kanban teams see two rows. The first:
| Metric | Description |
|---|---|
| DWIP | Average tickets in Dev per day |
| WIP | Average tickets in Dev, QA, or Code Review per day |
| Throughput | Items completed in the flow window |
| Cycle Time | Average days from first active status to Done (includes rollover) |
| Lead Time | Average total time in the system (Ready wait + Cycle Time) |
| Flow Efficiency | Active time / Lead Time × 100 |
The second row breaks the time down by state: Avg Ready, Avg In Progress, Avg Code Review, Avg QA, and Avg Waiting (post-work queues: QA Ready, UAT, Merge, Sign-off, Blocked).
Kanban flow columns
Kanban teams also get extra columns for flow visibility — RO Wait, Flow State, an SLE indicator (green within SLE, orange exceeding, red critical), State Age, Waiting, Lead Time, and Efficiency. Active tickets sit above a Completed separator; Done tickets below.
Flow efficiency, explained
Flow efficiency is the share of a ticket’s time spent on productive work versus waiting. Dev and QA count as active; Ready, Code Review, QA Ready, UAT, Merge, Sign-off, and Blocked are waiting. Code Review, UAT, and Merge are handoffs where the developer isn’t actively working — so a team with fast handoffs still scores high.
Tips
- When a ticket is marked Done (D), the remaining days auto-fill with -.
- Tab / Shift+Tab move between cells; Enter moves down the same column; arrow keys navigate the grid.
- Click the ticket-type icon to change type or mark a ticket descoped.
- Mark the first status * to flag a ticket that was added mid-sprint (unplanned).