GALLERY
Project & Development Templates
From planning to retrospectives, use ready-made boards and task structures built for how dev teams work. Whiteboard and kanban come as a set, so you can run them right in the meeting.
16 items
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.