Keep the board open during your daily meeting
Whatever your team calls it, a stand-up or, if you run Scrum, the Daily Scrum, you run it off the board on the screen, and somebody always moves a card while you are still talking about it. Leave the board open: it re-reads the query on its own, so the change to Broker portal: quote validity extended to 30 days shows up without anyone reaching for F5.
Steps
- Open AnyKanban under Boards and open the board. For a meeting that spans Claims Platform, Core Insurance and Digital Banking, the change request board.
- Leave the tab in the foreground and run the meeting. Do not reload the page.
- Have the person who owns a card move it in their own tab, dragging Broker portal: quote validity extended to 30 days from New to Triage, or change its state on the work item form.
- Keep watching your own board. The card arrives in Triage within about twenty seconds; the two column counts change with it.
- Switch to another browser tab and back. Returning focus asks for a refresh straight away, so a tab you left an hour ago is current by the time you have read the first card.
- Press Refresh in the header for an immediate, complete re-read: the query, every card, the checklists and related rows, and the rollup. The cards stay on screen while it reads, Refreshing shows at the right of the tab row, and the new cards replace the old ones in one step. Until then nothing on the board can be dragged or edited, because the new read would overwrite the change. The board's own settings are read once per tab, so a WIP limit someone else changed arrives when you reload the page, not from this button.
What you should see
Only what actually changed moves. A refresh cycle that finds nothing new publishes nothing, so an idle board does not flicker, does not jump the scroll position and does not quietly reorder itself under the pointer. When something did change, the card appears in its new column and both column counters follow; everything else on screen stays exactly where it was.
Your own changes come back faster than that: after a drag settles, the board reconciles with the server about a second later, and closing a work item form you opened from a card refreshes almost immediately.
Notes
The cadence is fixed in the product, not a setting: roughly twenty seconds while the tab is visible and roughly two minutes while it is hidden, each with a small random spread so a room full of open boards does not all call at the same instant. Repeated failures stretch the interval further rather than retrying harder. While a read-only As of snapshot is open, refreshing stops completely, because a snapshot is meant to hold still.
A board left open all day stays current on its own, at the cost of one page reload an hour. Azure DevOps accepts AnyKanban's sign-in for an hour, and it can take up to a quarter of an hour after that to hand out a new one by itself. Reloading the Azure DevOps page gets a new one at once. So on the AnyKanban hub, in the last ten minutes of that hour, the board reloads the page at the first moment nobody is using it: when the tab is in the background, or when nobody has clicked, typed or scrolled on the board for two minutes. If the board is in use the whole time, it reloads two minutes before the end. It waits while you drag a card, while a change is still being saved, while a board's settings are open or a board is being created, and while you are typing into a box on the board. If you come back to a wall board and find it has just reloaded, that is the board reconnecting, not a fault.
When the sign-in runs out all the same, the board keeps its cards and says what time they were loaded. Where it can tell when Azure DevOps will hand out the new sign-in, it names that time and reads again then. A board on a dashboard never reloads the page: it keeps its cards and waits. If the board asks you to reload the Azure DevOps page, do it, because a reloaded page reconnects at once.