CHIPSCollaborative Heuristic for Iterative Planning and Story-pointing · documentation for version 1.7.0

Changelog — CHIPS

CHIPS — Collaborative Heuristic for Iterative Planning and Story-pointing. Versions follow semantic versioning: MAJOR.MINOR.PATCH. The version is in scrumpoker/version.py; the database has its own schema version (Admin → Settings shows both).

1.7.0 — 2026-10-28

A demo area, in every edition — Projects → Demo (/demo) makes a ready-made project, CHIPS demo:

  1. One active room — Demo · Sprint 12 planning, which counts as one of the edition's active rooms.
  2. People — a scrum master (Sam), a moderator (Morgan), a watcher (Wes, the product owner) and five team members (Ann, Bob, Cat, Dan, Eve), on the project's team list with seniority and working days.
  3. Stories — 19 user stories and an epic (Checkout redesign) split into four stories: estimated with votes, notes and second rounds, assigned (Ann over her maximum), some in progress or done, the rest in the backlog, and a revealed round with an outlier left on the table.
  4. Analytics in Community and Team — three earlier sprints (archived, so they use no active rooms) give the analytics their history; the demo project's analytics are shown in every edition.
  5. Enterprise and Team features to try — a recording of the first stories (playable in any edition), the demo's activity log entries with a CSV download, REST API examples with the API's answer for the demo room, Jira-style issue keys, and a preview of single sign-on.
  6. One demo per installation, open to every scrum master and administrator; Reset makes it again, Remove frees its room.

Database schema version 9.

1.6.0 — 2026-10-27

Sprint planning with capacity, and analytics.

Sprint planning (every edition)

  1. Working days per person — each project has a team list (Projects → the people button): name, seniority and working days per sprint. A room is a sprint: set its dates (working days are counted) and change anyone's days for that sprint only.
  2. Minimum and maximum story points per person — per person or per sprint; the defaults use 1 story point = 1 working day: maximum = working days × points per day, minimum = half the maximum. The project's points per day can be changed.
  3. Over the maximum turns red — the room's new Sprint capacity panel shows assigned / maximum for each person: red with a warning sign when over, orange under the minimum, green in between; plus unassigned points and assignees not on the team list. The assignee field suggests the team list's names.
  4. Delivery data — stories record when work started and was done, defects, times reopened and sprints carried over (Edit → Delivery), or read them from Jira (Delivery from Jira: status changes, resolution date, linked bugs, the Sprint field).

Analytics (Enterprise edition) — a new Analytics page per project and period, every table as CSV:

  1. Estimator behaviour — first-round votes above, on or below the final estimate; tendency.
  2. Highest and lowest estimator — how often each person was the highest or the lowest.
  3. Velocity contribution — planned and delivered points per sprint, each owner's share, utilisation.
  4. Agreement and divergence — spread of first-round estimates per story, by technique, re-votes.
  5. Anchoring and influence — whether final estimates move toward the first person to comment or the most senior voter more than toward others; influence by person.
  6. Ownership quality — defects, rework and carry-over by owner and by the estimator whose vote won.
  7. Monte Carlo forecast — 50/70/85/95% delivery dates from weekly throughput; chance of finishing by a date.
  8. Points versus cycle time — Spearman, Pearson, R², scatter, box plot by size; whose votes predict best.
  9. More — size drift and point inflation, epic trunk versus the sum of its stories, estimation effort, capacity history.

REST API: team list, room capacity, sprint dates, delivery and GET /api/v1/projects/{id}/analytics. Database schema version 8 (applied automatically).

1.5.0 — 2026-10-26

  1. American or British English — the administrator chooses the spelling of the interface in the setup wizard (Installation options → Language (spelling)) or later under Admin → Settings: English (United States) — color, organization, canceled, license — or English (United Kingdom) — colour, organisation, cancelled, licence. Menus, messages, notifications and Help follow the choice; what people type (story titles, names, notes) is never changed, nor are commands and addresses in Help. Existing installations keep British English. New setting language (en-US / en-GB) in the site settings and the public settings.
  2. The maker — CHIPS is made by EEZEEZEE: EEZEEZEE with the 2nd, 4th and 6th "E" and the 2nd "Z" reversed. On screen (welcome page, Help, the license agreement, documentation and website) every reversed letter is mirrored; plain text (package metadata, the .deb maintainer, LICENSE.txt) uses Ǝ for the reversed E's, as Unicode has no reversed Z. Screen readers read "EEZEEZEE".
  3. Welcome page — under the full name it now says "by EEZEEZEE" (styled as above) instead of "for" and the organisation name.

1.4.0 — 2026-10-26

Running a session: eleven new ways to estimate and moderate.

  1. Custom decks — a sixth technique with your own cards (numbers, words or emoji, 2–30), named, with presets; scrum masters save decks for their other rooms. Number decks get averages and totals.
  2. Pass card — ? now means pass (abstain): it counts as voted but is left out of averages, consensus and outliers; results show how many passed.
  3. Timer — a countdown per vote (rule: seconds per vote, reveal when time is up) or started from the room (30 s – 5 min), with +30 s and stop.
  4. Outliers — after the reveal, votes two or more cards (configurable) from the median are ringed in red with "ask them to explain"; for three-point estimates, PERT values far from the median.
  5. Moderators — the scrum master makes anyone in the room a moderator, who runs the session without an account (rule: moderators vote too).
  6. Kick, lock, hide — remove people from the ⋮ menu (moderators too), lock the room with the padlock, Hide results in one click.
  7. Anonymous voting — revealed cards without names for everyone, including the scrum master; history, downloads and recordings keep them anonymous; turning it off never un-hides a round.
  8. Watchers — Join as watcher (or switch someone): they see everything but do not vote, add notes or react, and never count as missing votes.
  9. Averaging rules — suggested estimate from the mean, the median, the most common card, or the mean without the highest and lowest vote.
  10. Emoji reactions — ten reactions shown next to names and in a feed for ten seconds.
  11. Epics and quick split — estimate an epic as a whole (the trunk), then split it in one step (equal parts, SPIDR, workflow steps, CRUD or your own list) into stories under it; the backlog shows the parts as a tree with their progress and total; an optional "too big — split it?" prompt after a reveal; POST /api/v1/rooms/{room}/stories/{story}/split.

Also: CSV downloads add Type, Epic, Passed, Outliers, Team value rule; the REST API reports roles; database schema version 7.

1.3.0 — 2026-10-25

Builds for macOS and Windows, and Windows as a host.

1.2.0 — 2026-10-24

A welcome page and setup wizard, security hardening, and protected (compiled, signed) builds.

1.1.0 — 2026-10-22

CHIPS becomes a product: editions, license keys, a license agreement and installable packages.

1.0.0 — 2026-10-22

First release under the name CHIPS (previously "Scrum Poker").

Earlier stages (before version numbers)