BoardSnap is an iOS app that reads timeline retrospective whiteboards and turns the sprint's chronological event map — including emotional markers — into a narrative retrospective document with pattern-based action items.
A timeline retrospective is different from column-based formats. Instead of asking 'what went well and what didn't,' it asks 'when did things happen and how did the team feel at each moment?' The horizontal timeline traces the sprint from day one to sprint end.
This format is particularly powerful for identifying the cause of late-sprint crunch, for surfacing moments of confusion that got resolved, and for finding recurring patterns across sprints. But it only works if the output preserves the chronological structure.
A photo of a horizontal timeline is hard to read on a phone screen — the text is small, sideways, and the emotional markers blur into the event markers. BoardSnap reads it correctly.
A line from left (sprint start) to right (sprint end). Mark the calendar at regular intervals — daily for two-week sprints, weekly for longer projects.
Each team member adds sticky notes or flags at the relevant point on the timeline. Events can be external (dependency delivered, stakeholder review) or internal (design complete, testing started).
Above or below the timeline, mark the team's emotional state at key points: thumbs up, thumbs down, or a simple curve showing energy/confidence level. This is the most valuable layer — it maps how the work felt, not just what happened.
Where did the emotional curve drop sharply? Where did it spike? Circle these — they're the moments worth discussing. Write a one-line explanation next to each circled point.
Does crunch always appear in the last three days? Do confidence drops always follow a dependency on another team? Patterns become structural action items.
BoardSnap reads the timeline left to right, capturing events in chronological order, emotional markers, inflection point annotations, and pattern insights.
A chronological retrospective document: the sprint timeline with events plotted at their dates, emotional markers summarized at inflection points, identified patterns with root cause notes, and action items derived from recurring problems. The output reads as a sprint narrative — clear enough for stakeholders to follow without having been in the room.
Three consecutive timelines revealed the same pattern: confidence dropped on day eight (of ten) every sprint. The cause, visible when comparing the three BoardSnap captures side by side, was always a late-arriving design asset. One structural fix — moving design handoff to day six — eliminated the pattern.
A six-week product launch mapped on a single board. BoardSnap identified seven distinct inflection points — three positive, four negative — and generated action items for the four negative ones. The document was shared with the full company as the official launch retrospective.
An incident postmortem traces a single incident's timeline, focused on failure causation. A timeline retrospective traces a full sprint or project period, focused on team experience and recurring patterns. They share the timeline format but serve different purposes.
Yes. Place sticky notes at the appropriate calendar point on the timeline. Make sure notes are labeled with a date or sprint day — BoardSnap uses these to place events chronologically in the output.
Write explicit labels: 'High confidence,' 'Stressful week,' 'Team confusion' above or below the timeline at the relevant point. Smiley/frowny face drawings are captured but written labels give BoardSnap more to work with.
Three to four sprints is enough to identify recurring patterns. Two is suggestive. One is anecdote. The BoardSnap project accumulates timeline snaps automatically — the project AI chat can compare them on request.
Snap the board, ship the action items in ten seconds.