Skip to content

Retro Board

Run retros in Odoo and open the next board on last time's unfinished work.

The short answer

Retro Board runs team retrospectives inside Odoo: a sticky-note wall with columns, dot voting on a per-person budget, and cards that can be anonymous. Promote a card and it becomes an action item with an owner and a date. Anything still open when the next retro starts appears at the top of that board. It suits teams already keeping their work in Odoo.

Get it on Odoo Talk to the engineer who built it

Last updated

What it is for

The retro itself went fine. People said the uncomfortable thing, the team agreed on changes, somebody wrote them on a whiteboard photo, and weeks later the same complaints came round again. That is the failure retrospectives actually have, and no amount of better facilitation fixes it. Whiteboards and sticky-note tools are built for the hour of the meeting. What decides whether a retro was worth holding is the fortnight afterwards, and that is precisely the part they hand back to you as a photograph.

Platform
Odoo
Category
Odoo workspace
Works with
Odoo 18 · Odoo 19
Technical name
retro_board
Status
Published on the Odoo App Store
On the store
Odoo 19 Odoo 18
Pricing
Paid

What is inside it

  1. 01

    The board

    Columns of sticky notes, dot voting with a real budget, optional anonymous cards, drag or arrow keys to move one. Phases run brainstorming through closed, and the controls on screen follow the phase.

  2. 02

    Carry-forward

    Promote a card to an action item with an owner and a due date. Any item still open when the next retro starts is shown on that board before anyone writes a new card.

  3. 03

    The hard part

    An anonymous card's author never enters the payload sent to the browser. Voting resolves the caller from the session, so no argument can vote as somebody else or burn their budget.

  4. 04

    The cockpit

    Twelve tiles in four bands, each opening the rows it counted. None of them count cards or votes, because a drill-down there would list authors beside card text.

What it looks like in practice

  1. An overdue commitment from the last retro opens the next one

    The previous board closed with an action item that had an owner and a date, and that date has now passed. Nobody remembered to raise it again.

    The strip across the top of the new board carries last retro's still-open commitments in, before a single new card is written. When the previous closed board produced nothing, the strip is omitted rather than rendering a row of zeroes.

    Phase
    Voting
    Votes left
    3 of 5
    Carried in
    1 still open

    Figures from the module's own demo data, on a fresh install. Install with demo data and open Retrospectives, then the Sprint 42 board.

    Carry-forwardThe board

  2. Someone wants to raise the uncomfortable thing without their name on it

    The wall is visible to the whole team, and the card that would be most useful is the one nobody wants attributed.

    With anonymous mode on, the author is never sent to the browser at all, rather than being sent and hidden in the template. The flag is re-checked when the board is read, so switching a session to anonymous protects cards already on the wall, and no tile drills into the vote table to recover it.

    Behaviour of the shipped code.

    The hard partThe board

  3. Half the commitments the team raised are still not closed

    Retros keep running on schedule and nobody can say whether the agreed work actually landed.

    The cockpit measures the wall through the commitments it produced: how many closed, how many are past their date, and how many carry nobody's name. Each tile opens the rows it counted, so the follow-through figure is a list you can read.

    Follow-through rate
    50%
    Overdue commitments
    2
    Nobody owns it
    1

    Figures from the module's own demo data, on a fresh install. Install with demo data and open Retrospectives, then the cockpit.

    The cockpitCarry-forward

What it deliberately does not do

No Slack, Teams or Jira
There are no chat or tracker connectors, and the placeholder screens that once promised them have been removed. Action items live in Odoo.
No timer or facilitator kit
There is no countdown, no icebreaker library and no meeting timer. The board is the ceremony surface, not a facilitation suite.
No public sharing link
Participants are Odoo users. There is no anonymous URL for a guest to join a board from outside.
No AI summary
Nothing here writes up your retro. The fields for it exist in the schema and are deliberately not advertised as features.

Questions

Can I install this on Odoo Online?
No. Odoo Online cannot install modules that contain Python, so this runs on Odoo.sh or a self-hosted instance. Check the versions listed above for the series and edition it is verified against.
Can action items sync to Jira, Slack or Teams?
No. There are no chat or tracker connectors, and the placeholder screens that once promised them have been removed. Action items are ordinary Odoo records with an owner and a due date, which is also how the carry-forward strip finds them. If the commitments have to live in a tracker, keep looking.
Can people outside Odoo join a board?
No. Participants are Odoo users, and there is no public URL for a guest to join from outside. Anonymous mode covers the case where somebody does not want their name on a card: it keeps the author out of the response the browser receives, rather than letting outsiders in.
Is the price charged per team or per month?
Neither. It is one payment for one Odoo database, and the number of teams on that database does not change it: a fourth squad starting retros next quarter adds a record, not a line on an invoice. There is no per-seat count to watch and no renewal date.

Have something to build?

Tell us the problem. We'll come back with a plan, a price, and who'd actually build it.

Start a project Browse services
  • Free scoping call
  • Reply within 1 business day
  • No lock-in