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
Task Management for Beginners: Your First Week of Brain-Dump, Priorities and Today's 3
A beginner task management template for anyone building a system for the first time: write every task down, set priorities, and keep only 3 for today, all within your first week. On the whiteboard, the left page holds a frame for dumping every task of the week, a four-quadrant importance and urgency matrix, three frames for today's 3, this week and waiting on others, and the four steps of the daily loop of 5 minutes each morning and evening; the right page holds a weekly log of 5 rows by 3 columns, the Friday 10-minute KPT review in three columns of Keep, Problem and Try, two stuck-point frames and a frame on how to keep going. The task board has five columns, Brain-dumped, Today's 3, This week, Waiting on others and Done, and starts with 4 parent tasks and 12 subtasks, from the brain dump to the Friday review, all not started. Task management habits fail when one item is too big and too many go into a day, so the board splits each task to its first step and caps today at three.
Project Management for Beginners: Plan Board for Goal, Scope, Schedule, Team, and Risks
Someone leading a small project for the first time uses this project management template for beginners to set the goal, scope, schedule, team, and risks of the plan on one board. The left page of the whiteboard holds the project charter, the five process groups from initiating to closing, a stakeholder map of influence by interest, and three frames for scope, team, and risks; the right page holds a 4 by 4 milestone table, a risk quadrant of likelihood by impact, and three frames on the weekly check, delays, and closing. The task board has five columns, from planning and preparing to in progress, in review, and done, and starts with 4 parent tasks and 12 subtasks, all not started. Starting work without knowing that a project plan follows a set order leaves gaps, so the five PMBOK process groups run through the board as its flow. It suits small projects that finish in a few weeks to a few months, such as an in-house event or a trial of a new service.
Gantt Chart for Beginners: Schedule Board to List Tasks and Draw Start Dates, End Dates, and Owners
Beginners learning how to make a Gantt chart use this schedule template to list the tasks of a small project and draw start dates, end dates, and owners as bars on a weekly timeline. The left page of the whiteboard has three WBS frames that split the work into prepare, produce, and publish, a four-column MoSCoW filter that narrows the rows, and a Gantt grid of 5 tasks across 6 weeks; the right page holds the goal and deadline, a five-step how-to, three frames on common mistakes and staying on track, the weekly update rules, and a three-column KPT. The task board has five columns, from listing tasks and setting dates to in progress, in review, and done, and starts with 4 parent tasks and 12 subtasks, all not started. A Gantt chart is a table with tasks down the side and weeks across the top, where each period is drawn as a bar. Putting every task on it makes a wall of bars, so narrow the rows with MoSCoW first.
5 Whys for Beginners: Ask Why Five Times to Find the Root Cause and Stop It Coming Back
This beginner-friendly 5 Whys template is for anyone handling root cause analysis for the first time, to follow the method step by step and land on a root cause and a preventive fix. The whiteboard uses two pages: on the left, a frame for the facts, the four steps of a session, a fishbone diagram covering people, method, machine and materials, and a six-row 5 Whys chain; on the right, good and bad whys, the root cause with its fix, and a four-by-four action plan. The task board has five columns - problem, digging into why, fix decided, in progress and effect checked - and starts with 4 parent tasks and 12 subtasks, all not started. Beginners usually get stuck by blaming carelessness and stopping there, so the board spreads the causes across four angles first and uses them as clues for the five whys. A worked example about a double-booked meeting room fills all six rows, and one review takes about 30 minutes.
Agile Development for Beginners: Scrum Roles, Events and Artifacts in Your First Sprint
Anyone new to agile development or joining their first Scrum team uses this beginner template to learn the 3 roles, 5 events and 3 artifacts and to run a first two-week sprint. The whiteboard lays out what agile development means, the 5 steps of a two-week sprint, three frames for the 3 roles, three frames for the 3 artifacts, a table of the 5 events, four MoSCoW columns that pick what fits this sprint, and a KPT retrospective. The task board has five columns - Product Backlog, Sprint Backlog, In development, Waiting for review and Done - and starts with 4 parent tasks and 12 subtasks, from learning the terms to review and retrospective, all not started. Join a team without knowing how Scrum works and the vocabulary leaves you behind, so follow this board from top to bottom for one sprint and you will also know what to say in the daily scrum. Unlike a board for teams already running sprints, this one is about the terms and the first cycle.
Weekly Task Triage for New Hires: From Taking Requests to Hitting Deadlines
A weekly task management template for first-year employees who take work from several seniors at once, covering how to take a request, how to prioritize, and how to hold every deadline. The whiteboard holds this week's ground rules and your measured capacity, a 5W1H check to run the moment a request arrives, an urgency-against-importance matrix (the Eisenhower matrix) for picking today's three, a log of estimates against actual hours, and a Friday KPT retrospective. The task board runs five columns - incoming, today, in progress, in review and done - and opens with five parent tasks, all unstarted, from standardizing intake and ranking work on Monday through checking in before the deadline and closing out the week. Task management stops being guesswork, checking in two days before a deadline turns into a habit, and you never again have to admit on the due date that the work is not done.
Mistake Recovery Playbook: The First 30 Minutes and Preventing a Repeat
The Mistake Recovery Playbook is a template for a first-year employee who made a serious mistake at work, covering the first response, the report to a manager, five whys analysis, and prevention. The whiteboard holds how to face a mistake, a five-step flow for the first 30 minutes, the five points every report needs with phrasing that avoids excuses, a five whys analysis, and a prevention log. The kanban runs from just happened to done in five columns, with five parent tasks and 13 subtasks already written and untouched - first response, separating fact from impact, reporting, finding the cause, and preventing a repeat. Because the words for the report and the next move are decided in advance, you start moving instead of hiding the mistake, and you end up with a safeguard that stops it happening twice.
Meeting Minutes and Reports: Documents People Read Within 30 Minutes
The meeting minutes template for a new hire who has just been handed the minutes and is learning how to write them, opened right before the note-taking starts and again at the pre-send check. The whiteboard holds a 5W1H frame for the report, a grid showing how minutes, status reports, daily notes, and incident write-ups differ, the 30 minutes right after a meeting, a pre-send checklist with house style rules, and a running log of the corrections you get back. The task board runs Draft, Shaping, In review, Shared, and Into the template - five columns holding five parent tasks and 13 subtasks that all start untouched, from taking notes to updating your own template. Move one document as one card and feed every correction back into the template, and you stop guessing what a report should contain while the corrections per document fall month by month.
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.