01
Capture every idea without filtering
The Ideas column is a low-friction inbox. Drop in technical explorations, architecture proposals, and improvement hunches. Filtering happens later during planning, not at capture time.
// Engineering Backlog
Prioritize the technical work.
Not every important project has a product spec. Track infrastructure upgrades, technical debt, tooling improvements, and research in a dedicated engineering backlog.
Ideas
3Evaluate GraphQL federation for microservices
Research
Prototype edge caching for API responses
Enhancement
Explore migrating CI/CD to GitHub Actions
Research
Planned
2Rewrite notification pipeline to async queue
Enhancement
Add database read replicas for analytics queries
Feature
In Progress
2Implement incremental static regeneration for docs site
Feature
Refactor auth middleware to support multi-tenant tokens
Enhancement
Shipped
2Deploy zero-downtime database migration framework
Shipped
Launch rate limiter with sliding window algorithm
Shipped
02
Promote to Planned with clear scope
When an idea is ready, write a clear problem statement and acceptance criteria on the card, then move it to Planned. Vague cards stay in Ideas until they are concrete enough to estimate.
03
Limit In Progress to active commitments
Only cards someone is actively working on belong in In Progress. If work stalls, move the card back to Planned with a comment explaining why. Honesty beats optimism on a backlog board.
04
Celebrate what shipped
The Shipped column is your team changelog. Review it during retrospectives and all-hands. Seeing shipped work builds momentum and helps stakeholders understand engineering velocity.
01 What belongs in an engineering backlog?
+
Technical debt, infrastructure improvements, developer tooling, architecture changes, performance work, and exploratory research. If it improves the system but is not a direct product feature, it belongs here.
02 How often should I groom the engineering backlog?
+
Review the Ideas column biweekly. Close items that are no longer relevant, merge duplicates, and promote high-value items to Planned. A backlog that grows without grooming becomes a graveyard.
03 Should I separate the engineering backlog from the product backlog?
+
Yes. Product backlogs are prioritized by customer impact. Engineering backlogs are prioritized by system health, developer productivity, and technical risk. Mixing them leads to technical debt being perpetually deprioritized.
// Ship the invisible work
Track what matters under the hood.
No credit card. Free engineering boards with real-time sync and full activity history.