Roadmap
Nothing here is a commitment to a date or a scope. This page mirrors ROADMAP.md in the repository, which is the source of truth; the issue tracker has the detail.
Kudos, with no leaderboard
Section titled “Kudos, with no leaderboard”A short note thanking somebody, visible to the team — on the space itself, and as the closing beat of a standup. The interesting part is the constraint: the moment kudos are counted and ranked they become a performance metric and the honest ones stop, so there is no count, no aggregate, and nothing that orders people by anything. A sender can withdraw a kudo; nobody can edit one, and guests neither send nor receive. See Kudos.
Status: In Progress
Tracking: #386
Honest ceremonies
Section titled “Honest ceremonies”A commitment carries into the next standup and opens with one question: did that land? Two sessions running without landing, and the commitment is flagged as stuck — the commitment, not the person (#479). And a session can be given a limit, publishing what it did not get to when the limit runs out — the poker half of which is separated out and ready to build (#482).
Take the whole instance with you
Section titled “Take the whole instance with you”parley export writes every space, session, estimate, vote and standup entry to
a single versioned archive, and parley import reconstitutes it elsewhere. Data
ownership is a claim until it is a file you are holding. Export lands first and
on its own — it is half the work and most of the trust.
The estimate lands on the ticket
Section titled “The estimate lands on the ticket”A poker story can carry a Jira issue key, and the agreed estimate writes to the story point field when it is saved. That is the whole of the first slice — one write path that always works. Importing a board, syncing status, and filing from the room stay in Exploring under #378; GitHub (#383) waits until Jira write-back is boring.
Tracking: #391
Async standup
Section titled “Async standup”A standup that opens on a schedule, in the team’s timezone, and stays open for a window instead of a meeting. Blockers come first, and yesterday’s commitments come back as done, still on it, or dropped. An open standup shows who has answered. Across days, a team sees only its own aggregate, and only once at least four people are counted. There is no per-person rate and no late badge.
Status: Backlog
Tracking: #388
A plugin system
Section titled “A plugin system”Extend Parley without forking it — integrations, meeting notes, themes, and whole ceremonies, installed by the operator and running under capability grants they approve. Plugin code would be sandboxed WebAssembly with no sockets and no database access, reaching everything through a host function that checks the grant first.
The extensible core shipped (#8); this is the layer on top of it.
Tracking: #9
A parking lot with an owner and a clock
Section titled “A parking lot with an owner and a clock”“Let’s take that offline” is the most-spoken and least-honoured sentence in any ceremony. A first-class parking lot refuses the deferral without a person and a date attached, then puts the item back in front of the room at the next session until somebody deals with it.
The rest of the ceremonies
Section titled “The rest of the ceremonies”Retrospectives with grouping and dot voting, action items that outlive the meeting, user story mapping, a sprint board, team health checks.
Some of these will arrive as plugins rather than core features, which is rather the point of the plugin system above.
A collaborative whiteboard
Section titled “A collaborative whiteboard”An infinite canvas with sticky notes, shapes, connectors, frames, live cursors and comments — and every ceremony above able to run on it.
The largest single bet on the page, and one that deserves an explicit decision before anyone starts: the document engine underneath it is infrastructure, not a feature.
Exploring
Section titled “Exploring”Ideas under consideration, not committed to:
- Boards that work offline and merge on reconnect — nearly free once a conflict-free document engine exists
- Retro synthesis and meeting recaps, with a bring-your-own model endpoint so nothing leaves the instance
- The rest of two-way issue sync — importing a board, syncing status, filing from the room — beyond the write-back now under Next (#378); the same job for GitHub, once Jira works (#383); Linear to follow
- Replaying how a board or a ceremony actually evolved
- Spaces a creator can open to anyone, no sign-in required, on an instance that otherwise requires an identity provider
- Vote with the work — estimate from the ticket itself, not a copied title
- Stance, not a number — confidence or risk alongside points
- A room that dies with the meeting — the session ends when the calendar event does
- Audit logging, retention policies, and SSO group-to-role mapping
- White-label theming, for anyone hosting Parley on someone else’s behalf
- Configurable timers for poker and standup — as one control rather than a ceremony of its own (#380)
- Feature flags, once there is a third ceremony to turn off (#381)
- Slack: a card posted when a session ends (#382)
- Team health and mood over time — anonymity and minimum-n settled before anything is built (#384)
- A shared board owned by a space (#385)
- Reactions and comments on a standup entry or a story (#387)
Things this documentation says are missing
Section titled “Things this documentation says are missing”Several gaps named in Known limitations — membership roles, account linking, knock-to-join — are on the roadmap in the repository. Others, notably observability and supply-chain tooling, are not yet scheduled anywhere. That is the honest position rather than an implied promise.
Feature requests
Section titled “Feature requests”Open an issue. Being discussed does not mean accepted — the status on the issue is the honest signal.