GALLERY
Public Templates
Official and community project templates, ready to copy
8 items
Web Production Flow: A Five-Phase Template From Requirements to Launch
The producer running a website build opens this template at project kickoff. The whiteboard holds a five-phase timeline, a grid pairing each phase's deliverables with what the client reviews, and a matrix for sorting change requests. The task board is split into five parent tasks from requirements to launch, moving through internal review and client review before they are done.
Two-Week Sprint Board: Plan to Retrospective
For development teams running two-week iterations, opened on day one and used until the sprint closes. The whiteboard holds the sprint goal, team agreements, blockers, and daily notes, plus a map of the two-week flow and the four sprint events. The task board tracks work through code review and testing, and starts with four parent tasks - planning, daily rhythm, review, and retrospective - each with its own subtasks.
Project Risk Register: Score by Likelihood and Impact, Act Early
Opened by the project lead in the first week, then reopened at the monthly risk review. The whiteboard leads with a likelihood-by-impact matrix that sets priority, plus a mindmap of where risks come from, a table of the four responses - avoid, reduce, transfer, accept - and the rules that keep the register from going stale. The task board runs from Identified through Assessing, Responding and Monitoring to Closed, and starts with five parent tasks - identify, score, respond, monitor and review - each with its own subtasks.
Product Roadmap: Aligning on Now, Next, and Later
For whoever sets product priorities with the team, opened at the start of each quarter and again at every monthly review. The whiteboard holds a frame for the target state, a grid crossing Now / Next / Later with feature, platform, and experience work, a value-versus-cost grid, a mind map of what informs the calls, and the operating rules. The task board runs from an idea pool through Now, Next, and Later to shipped, and starts with four parent tasks - shaping it, locking the Now, tidying Next and Later, and keeping it current - each with its own subtasks.
OKR Operations Board — run one quarter of objectives and key results
Open this with your team at the start of a quarter, then come back to the same board in every weekly check-in. The whiteboard holds a framed statement of the Objective and its ground rules, a mindmap breaking the goal into KRs, a table pairing each KR with its baseline and the moves planned for each stretch of the quarter, a 2x2 for sorting candidate actions, and the operating cycle from kickoff to scoring. The task board walks through setting the Objective, narrowing to three KRs, filling in the board, running the weekly check-in, and closing the quarter with a mid-point review and final scoring.
KPT Retrospective Board: From Last Try to the Next One
For teams that close each cycle with a retrospective, opened shortly before the session and used live during it. The whiteboard holds a frame for how the last Try went, the Keep / Problem / Try frames, a grid for sorting problems by impact and control, a 60-minute agenda, and a frame for the Try you commit to. The task board runs from raw topics through running the Try to checking its impact, and starts with four parent tasks - prepare, collect, decide, follow through - each with its own subtasks.
Bug Tracking Board: From Intake and Repro Check to Released Fix
Opened by the development team the day a bug report lands, and kept in use until the fix ships. The whiteboard leads with an impact-by-frequency matrix that sets the order of work, plus triage ground rules, a repro-steps template with worked examples, the six stages from intake to release, and how to call it when a bug won't reproduce. The task board runs from Reported through Reproducing, Fixing and Verifying to Released, and starts with five parent tasks - intake, repro, fix, release and follow-up - each with its own subtasks.
App Release Checklist: From Store Submission to Launch Announcement
The release owner opens this template two weeks before store submission. The whiteboard lays out the four gates to clear, the flow from submission to launch, and a matrix for deciding whether a bug blocks release. The task board splits into preparing the build and assets, getting through review, and announcing the launch, with the ready-to-submit and in-review columns showing exactly how far along you are.