POEM Online

The host creates a session and shares the 4-letter code. Players join with that code. Everyone — host included — will play.

When the team is in the lobby, the host clicks Start session.

You see two rows: Target state (top) and Actual state (bottom). The columns from left to right go from strategic through tactical to operative decisions. Below the rows there's a thin pink SM strip per row — Scrum Master / Coach activity.

From the tray below the board, drag the BO, PO and DEV chips onto each row to position where each role decides. Drop chips anywhere along the axis — even between two areas if ownership is a gradient.

Click cells in the pink SM strip to mark columns where Scrum Master / Coach activity is or should be present. Multiple non-contiguous columns are allowed — partial coverage is itself a useful signal.

(Optional) Add custom roles via the "+ Add custom role" button if your org has more (CPO, TechLead, ProxyPO…). Heads up: every extra role beyond BO/PO/DEV is usually an organisational symptom worth discussing.

Click I'm done — submit when ready. Skipping a chip is also valid — leaving a role unplaced is its own statement (e.g. "this role shouldn't exist in the future"). Your picks stay hidden from others until everyone has submitted.

The host clicks Reveal all. The board switches to an aggregate view: each player gets their own row (lane) with their name on the left and their chips on it. Below all player lanes, a dashed Consensus lane appears — initially empty.

Each placed role chip implies a responsibility range, drawn as a thin coloured bar at the bottom of the lane:
• BO covers everything left of their chip.
• PO covers everything between their chip and DEV.
• DEV covers everything right of their chip.

If the gap between BO and PO is at least one full column, a hatched ⚠ decision void warning appears between them — nobody clearly owns those decisions. That's a major discussion trigger.

Discuss the picture. Look for: roles placed in different positions, target ≠ actual gaps, decision voids, mismatched SM coverage. Hover any chip to confirm who placed it.

The host drags chips from the consensus tray onto the Consensus lane to record what the team agrees on. Consensus chips have a ★ dashed border for clarity. Click cells in the consensus pink SM strip to set agreed coverage. Double-click any consensus chip to remove it.

The host clicks End session in the side panel. The final summary screen shows everyone's lanes plus the team consensus. Click Download PNG to export the board for your records.