Development team

A lightweight engineering board that keeps references and blockers visible — with flexible task categories and zero forced fields.

About this template

Built for real dev work: not just "To Do / Done", but also a Resources lane for specs/links and a Questions lane to surface blockers early. It's designed to reduce context switching and make impediments obvious.

Task types cover common engineering work — bugs, urgent fixes, research, rechecks, tech debt, and waiting states — so you can triage quickly without inventing categories from scratch.

No preset custom fields by design: add story points, sprint number, estimates, time tracking, or any fields your team actually uses.

What's inside

Columns included

ResourcesQuestionsTo doPendingBlockedDone

Task types

BadBugComposingCoolCriticalRecheckResearchUnclearUnneededUrgentWIPWait

Key features

  • Resources + Questions lanes to keep knowledge and blockers visible
  • Clear blocked visibility with a dedicated Blocked stage
  • Fast triage via practical work categories
  • Simple flow that works with or without sprints
  • Custom-field free by default (add only what you need)

Who is this template for?

  • Product engineering teams
  • Startup dev teams
  • Dev agencies running multiple streams
  • Teams that want lightweight process
  • Anyone needing better blocker visibility
Ready to get started?
Learn how to create a board from this template in just a few steps.
Read the step-by-step guide

Frequently asked questions

What task types are included?

Common dev categories including bugs/urgent items, research/recheck work, tech debt, and waiting states for clean triage.

Why is there a Resources column?

It's a "reference shelf" for specs, links, docs, and recurring info that shouldn't compete with active tasks.

Can I add story points or time tracking?

Yes! Add custom fields for points, estimates, logged time, sprint IDs, etc.

How do I track dependencies?

Use links/relations between tasks and add a "Depends on" field or a simple checklist of prerequisites in the description.

How do I run sprints with this template?

Add a Sprint field and create a view/filter per sprint, or duplicate the board per sprint if that matches your cadence.

How do I keep the Questions column from becoming a graveyard?

Set a weekly "triage" ritual: every question must end as either a task, a decision, or a closed item.

Related templates