BoardSnap is an iOS app that turns a sprint planning whiteboard into a structured list of tickets — with story points, owners, and sprint goals — in under ten seconds.
Sprint planning on a whiteboard moves fast and generates real clarity. The team draws a capacity grid, writes user stories in the sprint column, calls out dependencies, negotiates scope in real time. The board is the most honest artifact in the whole planning session.
Then someone has to turn it into Jira tickets. That person is usually the engineering manager or a senior dev, and it takes them an hour after the meeting. By the time the tickets land in the backlog, details have degraded — story point context is missing, the dependency that was drawn as an arrow on the board exists only in the drawer's memory.
The alternative — skipping the whiteboard and going straight to Jira — slows the meeting down, anchors people to existing ticket formats too early, and kills the spatial energy that makes a planning session productive. The whiteboard is worth keeping. The cleanup work is not.
Divide the board: left column for the sprint goal, center for the sprint backlog (stories committed this sprint), right for the icebox (items that didn't make the cut). Add a small capacity block at the top — write each person's name and story point capacity for the sprint.
Each story gets a one-line title and a story point estimate in a circle next to it. Assign an owner by writing initials next to the circle. Dependencies between stories get drawn as arrows. Priority order = top to bottom.
Sum the story point circles. Compare against the capacity block at the top. If you're over, move the lowest-priority stories to the icebox column. If you're under, pull from the icebox. The whiteboard makes this negotiation visual and fast.
Circle any story that has an external dependency (waiting on another team, waiting on a vendor). Mark stories with known risks with a star or triangle. These visual markers help BoardSnap AI flag them in the output.
Write one sentence at the top of the board: 'By the end of this sprint, we will...' This becomes the header of the BoardSnap summary.
Open BoardSnap and capture the sprint grid. VisionKit straightens the perspective. BoardSnap AI reads the columns, stories, point estimates, and owner initials.
The BoardSnap output is a structured story list — title, owner, estimate, column, and any flagged dependencies. Copy each story into Linear or Jira. Pasting from structure takes five minutes instead of an hour.
A structured sprint plan with: the sprint goal as the header, a capacity summary per person, and a ranked list of committed stories with story points, owners, and dependency flags. Icebox items appear in a separate section. Dependencies drawn as arrows on the board are described in the relevant story's output text. The whole thing is paste-ready into any ticket tracker.
Team capacity was 42 story points. The planning board had 11 stories written in the sprint column. BoardSnap read all 11, detected two stories with arrows indicating dependency on a third, and surfaced them as a dependency note in the output. The PM had all 11 Linear tickets created within five minutes of the meeting ending.
The board had two columns: Mobile sprint and Backend sprint. Arrows crossed columns to show dependencies. BoardSnap read both columns separately and described the cross-column dependencies in the output, giving the backend team a direct heads-up about what the mobile team was waiting on.
Four people, no established process. The team used a whiteboard to negotiate what to build and in what order. BoardSnap's output served as both the sprint backlog and the first page of the project documentation — the team pinned it to the BoardSnap project context.
Yes. Numbers written inside shapes — circles, squares, triangles — are recognized. Writing your estimates in a circle next to the story title is the recommended format; it makes the output cleaner.
BoardSnap AI reads whatever notation you use. If you write S / M / L / XL next to stories, those appear in the output exactly as written. The summary will reflect your team's sizing conventions.
Not natively — BoardSnap outputs structured text, not direct Jira API calls. But the output maps cleanly to a Jira story format. Copy the title, points, and owner from each BoardSnap item into the corresponding Jira fields.
If the squads have separate visual regions on the board — separate columns, separate color coding, or a clear dividing line — BoardSnap AI picks that up and structures the output by region.
No hard limit. Boards with 20+ stories have been processed correctly. The denser the board, the more important it is to write clearly and leave space between items.
Close the loop — snap the retro board and get structured action items before the room empties.
Snap the prioritized backlog board and get a ranked list ready to drop into your next sprint.
Capture the standup board before it gets erased — blockers list and all.
Photograph the roadmap board and generate a timeline with milestones and owners.
Snap the board, ship the action items in ten seconds.