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.
You will find starter boards for a first-time lead alongside the sprint and bug-tracking boards a dev team runs day to day. Pick by stage: building the plan, tracking progress, or running a retrospective and preventing repeat problems.
77 items
Ransomware Recovery Plan: Agree on RPO and RTO, Verify a Pre-Intrusion Restore Point, Set the Order
Agree with the business the RPO (data point to restore) and RTO (hours to restore) for each system, and the ransomware recovery order from identity systems to work PCs. Assuming a breach, rank the operations that cannot stop in a business impact analysis (BIA) table and split decisions across business units, executives, and IT with vendors. Review backups on four points (immutability, a separate admin login, storage off the normal network, a pre-intrusion restore point) plus scope. Post-intrusion backups may hold rogue accounts, so choose one only after a forensic vendor dates the breach, and test in isolation first. Four traps (backups encrypted too, a console open to everyday admins, a second outage, a runbook only on servers) each get what happens, how to check, and the fix. In Japan, the IPA ransomware handbook for executives (September 2026) also helps; check the latest edition. The whiteboard has four pages; the task board has 4 columns, 4 parent tasks, and 12 subtasks.
Privileged Account Management: Inventory, Least Privilege, Temporary Access, and Log Checks
Manage privileged accounts by inventorying owners and last use, then moving to least privilege with separate everyday accounts, time-limited grants, and monthly log reviews. You finish with a table of who holds admin rights and why on servers and business systems, cloud, and employee devices, plus a cutting order, grant steps, and a monthly-check owner. A gap analysis (As-Is / To-Be) and a strength × frequency matrix decide whether to remove, separate, or time-limit each account. Common pitfalls (everyone admin on their own PC, leftover leaver and ex-contractor accounts, shared admin passwords, unchecked emergency accounts, unread logs) each get what happens, how to check, and how to prevent it. To start, copy the names of admin-role accounts from the cloud console and check each one's last sign-in date. The 4 whiteboard pages cover inventory, usage, cutting order, and operation; the task board has 5 columns and 4 parent tasks of 3 subtasks each (16 tasks).
Secrets Handling for Dev Teams: Keep API Keys Out of Code and Revoke Them on a Leak
Decide as a dev team how to keep API keys, database passwords, and private keys out of code, chat, and tickets, and how to revoke and replace one when it leaks. A table records where each secret is used, where it lives now, and who owns it, with one home per environment. Page 2 checks three pitfalls, namely old commits that keep a deleted value, screen shares and logs that show it, and laptops that hold production values. Treat a committed value as leaked and revoke it at the provider before rewriting history. A 5 Whys analysis and an impact matrix lead to a no-write rule, a management system, and a pre-commit check. A rotation schedule with a check for what will stop keeps old keys from lingering for fear of breakage. Login passwords people memorize are changed when they leak or seem at risk, not on a schedule. To start, copy the key names from each service's console. The whiteboard has 4 pages, and the task board has 5 columns, 4 parent tasks, and 12 subtasks.
Company Backup and Restore Test: Review Data with 3-2-1, Then Practice Restores Quarterly
Review your company's backups and run a restore test (actually bringing data back) once a quarter, four times a year, so every piece of data you protect is restored once a year. File server, business system, and cloud data are relocated under the 3-2-1 rule (three copies, two kinds of storage, one offsite), plus one copy disconnected from the network or unchangeable. For admin or IT staff at small firms guarding against failures, accidental deletion, and ransomware. Start by noting from your backup software or NAS console what is saved, how often, and where. Then check three weak points: backups on the same network as the original, an admin account shared with everyday logins, and data never restored. Restore periods for deleted cloud files vary by service, contract, and settings; check the console and latest guidance. Recovery order after a breach is out of scope. The whiteboard has four pages; the task board has five columns, 4 parent tasks, and 12 subtasks.
Cloud IaaS Misconfiguration Review: Lock Down Permissions, Public Access, Logs, and Keys
Teams running systems on AWS, Azure, or Google Cloud use this cloud misconfiguration review template to check permissions, public settings, network entry points, logs, and keys. You check all five areas in the console, settings, and change records (no probing from outside), fix what you find, and use organization policies and automated checks so mistakes do not return. First, split what the provider secures from what you secure under the shared responsibility model; the split varies by service, so check each provider's latest documentation. Four common pitfalls each get what happens, how to check, and how to prevent it: strong permissions left after an incident, public test storage, no log destination or detailed logging (untraceable after default retention ends), and daily use of the top admin account. Changes follow four steps, and every exception gets an expiry and an approver. The whiteboard has 4 pages; the task board has 5 columns, 4 parent tasks, and 12 subtasks.
Shared Link and Drive Audit: Fix External Shares, Leaver Shares, and Public Forms, Then Set Rules
Audit shared links and shared drives to find files anyone with the link can open, shares still open to vendors or former staff, and forms showing responses, then fix them. Setting names differ by service, so match them to the labels in each admin console. You search five angles - link, external, leaver, public form, and personal account - then sort findings on an importance-urgency matrix and set owners and deadlines. Four pitfalls get cards with what happens, how to check, and how to prevent it - default links open to anyone, copies left behind, visible form results, and company files in free personal accounts. Not sure where to start? List each service and its admin from your contract list or card statements. You end with sharing rules by situation, a quarterly check routine, and a way to ask before adopting a service. The four whiteboard pages map shares, find risks, set the fix order, and set rules; the task board has 5 columns and 4 parent tasks with 3 subtasks each.
AI Agent Permission Design: Least Privilege, Human Approval, Logs, and a Stop Plan for Each Job
A permission design template for deciding, job by job, the least access to give AI agents and automation tools, which actions a person approves, what to log, and how to stop them. Common traps: test-time permissions left on, personal accounts used for agents, and read emails or documents treated as instructions. Treat outside content as read-only data and require human approval before sending, deleting, or paying; draw that line by impact and reversibility. Start by copying connected apps and their permissions from your admin screen, then write how to cut the gap. Log who did what and when with 5W1H, and review on a set cycle and when tools change or you delegate more jobs. In Japan, IPA's Top 10 Information Security Threats 2026 (organizations) newly listed AI-related cyber risks at third place; check the latest guidance. Four whiteboard pages (jobs, permissions, approval, log and stop) plus a five-column task board of four parent tasks with three subtasks each.
Work Planning Template for Beginners: Split Jobs into Steps, Estimate Time, and Fill Your Week
When deadlines pile up, plan the week by splitting each job into steps, estimating the time, and fitting the steps into a Monday-to-Friday schedule. This work planning template starts by listing the hours you can really use and the jobs with deadlines, along with who receives each one and what done looks like. Split the nearest-deadline job into five steps such as research, first draft, ask for review, revise, and hand over, and note the time, prerequisites, and who you are waiting on for each. Since time is easy to underestimate, you also note where your own estimates tend to slip. Steps that do not fit are sorted into push back, make smaller, or ask someone, so an overpacked week shows up early. Then you place the morning steps under Now, the afternoon steps under Next, and the rest under Later, and a five-minute morning check lets you rework the plan midweek. The whiteboard has 4 A4 pages and the task board has 5 columns, with 4 parent tasks and 3 subtasks each.
Seminar Planning for Beginners: Your First In-Person Seminar Program, Venue, and Staff Checklist
For a first in-person seminar, decide one to two months ahead who should come and what they should take home, and the rest of the prep falls into order. Start by writing the topic, date, and venue, then tabulate when you will settle the speaker, capacity, and sign-up method. Lay out the program from doors open to close, and follow attendees, from first hearing about it to after they go home, to spot gaps in the prep. Sort what you find into must, should, could, and not this time, so you know what to finish first when hands or time run short. Check the venue for gaps, confirm timing and materials with the speaker, and give each staff role its before, during, and after tasks, ending with thank-yous, a survey review, and a handover. It suits internal study sessions and talks hosted by community groups, for an organizer plus 4 to 7 team members. The whiteboard runs four A4 pages and the task board has four columns, 4 parent tasks, and 12 subtasks.
Kickoff Meeting Prep for Beginners: 5W1H Outline, Agenda, 60-Minute Schedule, Week-One Tasks
This template helps a leader, starting a week ahead, prepare a kickoff meeting for a new project of four to seven people, down to a 60-minute schedule and first-week tasks. Start by outlining the project with the six 5W1H questions, then put the topics you want to raise into four boxes for purpose, roles, working style, and the first week. Sort the topics into Must, Should, Could, and Won't (MoSCoW) and schedule only Must and Should, so the agenda never outgrows the hour. If you are unsure how to write a kickoff meeting agenda, follow the sample lines on the board and swap in your own words. On the day, work from the same board with your limited-visibility team and write each decided task's owner, due date, and finish marker on the spot. The whiteboard has 4 pages, and the task board has five columns with 4 parent tasks and 3 subtasks each.
Charity Fundraiser Planning for Beginners: Pick a Cause and Goal, Choose One Idea, Report Back
Charity event planning starts two to three months ahead by choosing a cause and a target amount, and ends when the money is donated and the charity and helpers hear the result. It suits 4 to 7 volunteers holding a first fundraiser, starting with the cause, goal and date and a check of the charity's work and spending against official sources. A mind map spreads fundraising ideas in six directions, an impact map links who should act and how, and a comparison on four criteria narrows them to one. Rules that may apply, such as collecting donations in public or selling food, go into a box for checking with the venue, health office, local authority or charity. Rewrite the example notes in your own words and you get steps for asking for help, announcing, preparing, the day and reporting back, with owners and deadlines. The whiteboard has 4 A4 pages and the task board has 4 columns and 16 tasks, 4 parent tasks with 3 subtasks each.
Food Booth Planning for Beginners: Menu, Shift Board and Cash Rules for School and Local Fairs
This food booth planning board helps a school festival or local fair team in Japan work backward from the event day, from checking the rules and equipment to shifts and cash reporting. Start by writing down the date, place, hours, and whether fire, water, and electricity are available; that decides which dishes you can serve. Brainstorm ideas in six branches, place them on an appeal-versus-effort matrix, pick two or three, and estimate ingredients from planned sales. Hygiene rules and notifications differ by region and school, so the board only gives you a place to confirm them with the school, the organizer, and the hokenjo (Japan's public health center), plus the fire department if you use flames. Done means you cleaned up, counted the sales, handed them to the agreed person, and filed the report. It suits 4 to 7 people writing together as members of a limited-visibility team. The whiteboard has 4 pages; the task board has 4 columns, 4 parent tasks, and 3 subtasks each.
How to Choose a Project Template
Project management templates differ by the stage of the project they support. Decide first whether you are building a plan, running the work, or reviewing it afterward, and the right board becomes easy to spot. Templates named "for Beginners" are built for first-timers.
Building the Plan
If you have just been handed your first project to lead, start with "Project Management for Beginners". It lays out a charter, a stakeholder map, a milestone table, and a four-quadrant risk grid, so goal, scope, schedule, team, and risks all live on one board. Once scope is set, "WBS for Beginners" breaks deliverables into three levels down to a full task list. To turn that into a schedule, "Gantt Chart for Beginners" gives you a task-by-week grid for start dates, end dates, and owners.
Tracking Tasks and Progress
If a spreadsheet stopped getting updated, a migration-focused starter board can help. Pick "Excel Gantt to Board Migration for Beginners" when the schedule matters most, or the migration board for task lists when you care more about the list and each item's status than about dates. When too much work is half-done, the kanban starter board helps you set a WIP limit that caps Doing at three cards. A weekly-check starter board is also there for teams whose Gantt chart keeps going stale.
Running a Dev Team
Joining a Scrum team for the first time? "Agile Development for Beginners" walks through the three roles, five events, and three artifacts across your first sprint. Teams already running iterations get a two-week cycle board built for ongoing use. To follow a bug from report to released fix, use the bug-tracking board; to track a release from store submission to launch announcement, use the app release checklist board.
Retrospectives and Prevention
On the last day of a sprint or cycle, reach for "KPT Retrospective Board". Start from last time's Try, surface what to Keep and what was a Problem, and narrow the next step down to one thing. To trace a recurring issue to its source, "5 Whys for Beginners" widens the field of candidates with a fishbone diagram, then asks why five times until you reach a root cause and a way to stop it recurring. A risk register that ranks issues by likelihood and impact is also available for planning ahead.
Frequently Asked Questions
Can I look at project management templates without signing up?
Yes, every template's contents are viewable on the public page without an account. Once you want to use one as your own project, free registration lets you copy it from the marketplace. You can compare a planning board against an execution board before deciding.
Can I move from an Excel Gantt chart to a board?
Yes, by copying your current spreadsheet's contents across by hand. "Excel Gantt to Board Migration for Beginners" includes five steps for moving task name, owner, start date, end date, and progress onto the board, plus a space to write your update rules going forward.
Should I use sprints or kanban to track progress?
Sprints suit teams that plan and review in fixed two-week blocks; kanban suits a continuous flow of work with no fixed cycle. "First Kanban Board for Beginners" gets you started with a three-card WIP limit and a weekly check for what's stuck.
Can these also handle bug tracking or a pre-release check?
Yes. "Bug Tracking Board" uses five columns — intake, repro check, in progress, in review, and released — and orders work by impact times frequency. "App Release Checklist" tracks the gates from store submission to launch announcement, splitting waiting-for-submission from in-review.