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
Student Team App Project Plan for Beginners | Pick Features with MoSCoW and Assign Roles
A student team template to map app features, pick them with MoSCoW and assign roles. Built for the first meeting of 4 to 6 students making their first app. The order is: agree on what to build and the deadline, list features from users' problems, rank them since you cannot build everything, then set who does what. MoSCoW sorts features into Must, Should, Could and Won't this time; a table and three votes each keep one loud voice from deciding. The example is a four-person vocational college team building a campus-festival wayfinding app in 6 weeks. Plan on one session of about 90 minutes. There are four roles (coordinator, screens, data, tester) and a signals column that shows where to go back when plans change. The whiteboard has four A4 pages: project and deadline, feature tree, this round's features, roles and two-week blocks. The task board has 4 columns, 4 parent tasks (one per page) and 12 subtasks.
Project Plan Template for Beginners | Chapters, Scope, Budget, Risks and Boss Approval
Project plan template: write by chapter, fix scope, budget and risks, get your manager's approval. Start by writing the goal, timeline and team, then decide who writes each chapter and in what order. The aim is to get approval in the week before work begins. Set the question for each of the six chapters (background, scope, deliverables, team and schedule, budget, risks), then list what you will and will not do, deliverables and stakeholders on sticky notes. Narrow scope with MoSCoW, split risks by likelihood and impact, and vote on which to act on. Finally, prepare likely approver questions and decide next steps for approved, conditional and sent back. Unlike a Gantt chart, this keeps the schedule to one line of milestones and focuses on scope, risks and approval, for a leader, 2 to 4 members and one approver. The whiteboard has four A4 pages: set chapters, open up scope and risks, narrow the work, get approval. The task board has five columns, 4 parent tasks and 12 subtasks.
MoSCoW Analysis for Beginners | Sort What to Do into Must, Should, Could and Won't
MoSCoW analysis sorts what you want into Must, Should, Could and Won't to pick what to start first. Ask whether skipping it means failure, then name an owner and date for each Must. First write the fixed limits (deadline, people, money, who decides), list everything you want and park it in the four boxes. Then check the Musts fit your people, test each with three questions and votes, and note a reason for every item you drop. Sorting by importance and urgency suits tasks already in hand; MoSCoW suits choosing what goes in within a limited time. Plan for 4 to 7 people and 90 to 120 minutes. The example follows a cooking school with about 30 students: five staff narrow 20 wishes for a September booking site. The whiteboard has 4 A4 pages (deadline and questions, sort into four, challenge the Musts, start with the Musts) and 14 numbered frames. The task board has 5 columns, 4 parent tasks and 12 subtasks (16 in all).
Milestone Setting for Beginners | Write Done States, Pick 5, Set Check Dates and Warning Signs
To set milestones, write each as a done state, not a task, and keep five including the goal. You can then check progress on every check date. First, write the goal on the deadline day in one sentence. Then work backward from the goal to list what must be done before it, narrow the candidates by three criteria (clearly done, essential to the goal, not too far from the last one) and a vote, and line them up on a timeline. For each milestone, set how to judge it, the check date and the owner. If a check date passes undone or two slips occur in a row, redraw the dates on the timeline. Unlike a task schedule, this sets only the checkpoints. The example follows a bakery owner and four staff planning an online ordering launch on July 1, three months away. It suits teams of 3 to 6 and is used up in one sitting. The whiteboard has four pages, from the goal and deadline to check dates and signs. The task board has four columns, 4 parent tasks and 12 subtasks.
Kano Model for Beginners: Sort Features by 2 Questions and Pick What to Build First
The Kano model sorts features into 5 quality types with two questions, then sets the build order. List candidate features and ask users two questions for each, with it and without it, answered as pleased, neutral, or bothered. Find each quality in the quick chart and count people. Build must-be gaps first, then one-dimensional, then attractive features. Ask again when answers contradict, such as pleased to both. The model comes from the paper "Attractive Quality and Must-be Quality" by Noriaki Kano et al. (Hinshitsu, vol. 14, no. 2, 1984); this template narrows the answers to three choices. Unlike importance-and-urgency ranking, it separates needs from mere delights. Plan on 5 to 10 users, about 10 minutes each for 6 features. The whiteboard has 4 A4 pages: set the goal and features, record answers, sort into 5 types, assign what to build. The example reorders upgrades to an internal supply-request tool. The task board has 5 columns, 4 parent tasks, and 12 subtasks.
4L Retrospective for Beginners | Project-End Board: Choose 3 Promises for the Next Project
Close a project with a 4L retrospective and pick 3 promises to carry into the next one. 4L asks four questions: Liked, Learned, Lacked, and Longed for. This board pairs Lacked with Longed for items and narrows them to 3 promises. Line up the goal, result, and a timeline so everyone recalls the same period, then write notes in one color per person and group similar ones. Turn each pair into a draft promise, place it on a chart (likely to recur next project, changeable by us), and vote with 3 votes each. Give each chosen promise an owner, a check date, and a signal to redraft it if it is not kept. Unlike KPT, which teams often run regularly, this board uses 4L once at a project milestone and goes on to what you long for next time. Plan on 5-8 people and 2 hours: 60 min for timeline and notes, 60 for promises and owners. The board is four A4 pages. The task board has five columns, 4 parent tasks, and 12 subtasks.
Fishbone Diagram (Cause and Effect) for Beginners | Sort Causes by 4M, Pick What to Check
Fishbone diagram: state a problem in numbers, sort causes by 4M, pick what to check first. Write the problem as a number such as 8 a month, with when and where it happens. Put causes on sticky notes for each bone: People, Method, Machine, Material. Add Measurement (how you count and record) and Environment (lighting, time of day) to catch causes that fit no bone, then pick one cause per bone. Compare the six on impact, ease of checking, and fact or guess, and vote with three dots each. Unlike 5 Whys, which digs down one cause, this spreads wide first and then narrows, so you are less likely to jump to an assumed cause. Plan for 5 to 8 people and 60 to 90 minutes in one meeting. The example follows a pickle factory line where label mix-ups rose to 8 a month. The whiteboard has four pages: set the problem, list causes, choose factors, check and act. The task board has five columns with 4 parent tasks and 12 subtasks.
How to Find a Bottleneck for Beginners | Spot Pile-Ups by the Numbers, Fix Flow in 5 Steps
Find your bottleneck by the numbers: line up order-to-shipping steps and see where work piles up. Write each step's daily capacity and queue, find the narrowest step, pick two ideas with the five Theory of Constraints (TOC) steps from Eliyahu M. Goldratt, and set an owner and recount day. Count every step the same way: daily capacity, items waiting, days waiting, redos. The step with the lowest daily capacity sets the pace of the whole flow, and work piles up before it. Before adding people or tools, cut its idle time. Where 5 Whys digs into one problem's cause, this picks the step worth fixing first. For small shops and workshops with late shipping, 3 to 6 people. Filling the board takes 60-90 minutes, excluding counting days. The board is 4 A4 pages: counting rules, numbers per step, choosing ideas, trying and recounting. The task board has 5 TOC columns, from find it to find the next, with 4 parent tasks of 3 subtasks each. Recount in about 2 weeks and reuse the board.
Zero Trust Migration Roadmap: Rate Five Pillars and Pick Your Next Move
This zero trust migration roadmap template rates your current stage on the five CISA Zero Trust Maturity Model pillars and turns it into a four-quarter plan. Four stages (Traditional, Initial, Advanced, Optimal) and three cross-cutting capabilities (Visibility and Analytics, Automation and Orchestration, Governance) are checked. Names and boundaries can change, so check the latest CISA material. Instead of replacing an inside-is-safe VPN setup at once, you choose moves by impact and user burden and place them in Now / Next / Later. Four pitfalls (a product seen as the finish line, network work before identity, extra user effort breeding workarounds, exception VPNs that never close) are guarded against by an identity-first order and a closing date per exception. Start by copying the account count, MFA rate, and VPN user count from your identity admin console as evidence. The whiteboard has four pages; the task board has five columns, 4 parent tasks and 12 subtasks.
Vulnerability Management Process: Asset Inventory, Priority, Fix Deadlines, and Exceptions
Vulnerability management works better when findings tie to an asset inventory, priority follows exploitation and impact, not score alone, and unfixable items become time-limited exceptions. It suits teams worn out by score-only ordering and IT or security staff building a process. Start by noting where the inventory lives and who owns it for servers, endpoints, network devices, and software. Then judge each finding on CISA's SSVC factors (exploitation, automatable, technical impact, mission and well-being impact) and set a target fix deadline for each outcome (Track, Track*, Attend, Act). Check internet exposure in the inventory, apart from SSVC. Check factor definitions in CISA's latest material. Inventory cross-checks and expired-exception reviews catch pitfalls early, such as chasing everything by score, missing devices, open-ended exceptions, and closing fixes unverified. The whiteboard has 4 pages and the task board 4 columns, with 4 parent tasks and 3 subtasks each.
SBOM and Vulnerability Handling: Parts List, Intake, Fix-and-Notify, Ready for EU CRA Reports
From September 2026 the EU Cyber Resilience Act (CRA) requires an early warning within 24 hours and a notification within 72 hours of learning of an exploited vulnerability. Severe incidents follow suit; both end with a final report. This template helps software and device makers set per-product SBOMs (software bills of materials), an intake for outside vulnerability reports, a promise to fix and tell users, and who files reports. It also records per-product SBOM update triggers and owners. Recording when you became aware and naming who sends each early warning is the key to the short deadlines. Check the final report deadline in Article 14 of Regulation (EU) 2024/2847 and the latest guidance. Pitfalls, each with what happens, how to check and a fix: an SBOM never updated after shipping, a personal email as the only contact, fixes users never hear about, and no one deciding EU scope. The whiteboard has 4 pages; the task board has 4 columns, 4 parent tasks and 12 subtasks.
VPN, Remote Access, Device Inventory: List NAS, Printers, Cameras, Then Secure Them
Inventory template for the VPN, remote desktop, and vendor maintenance links into your office network, plus NAS, printers, cameras, and Wi-Fi gear. In Japan, the National Police Agency's 2025 figures show over 80 percent of infection routes reported by ransomware victims were VPN equipment and remote desktop; check its latest release. Find entry points from device ledgers, admin screens, contracts, and vendor inquiries, never by probing from outside. Small firms often miss vendor-built maintenance links nobody inside knows, updates left to the seller, default admin passwords, and links left open after work. Start from the accounting payment list to spot maintenance and lease vendors. Change default or possibly leaked passwords, not on a schedule, and prefer an authenticator app or passkey over SMS. Four A4 whiteboard pages cover listing, checking, deciding what to close, and keeping updates running. The task board has 4 parent tasks and 12 subtasks in five columns.
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.