monday dev is monday.com's product for software teams: a set of connected boards for sprints, epics, a bugs queue and retrospectives, with agile charts and GitHub links built in. Before you customise it, know that the boards depend on each other, so some columns and boards can't be removed without breaking sprint management.
monday.com is blunt about this. Owner, Status, Priority, Type, Estimated SP, Actual SP, Sprints, Epic and Bugs Queue are core columns on the Tasks board and can't be deleted. The solution folder also holds a hidden Capacity board, and deleting that folder destroys it permanently; it can't be recovered from the trash. And you shouldn't duplicate, template or copy individual boards out of the folder, because the connections break and, in monday.com's words, can't be repaired without developer intervention.
The boards that make up monday dev
| Board | What it's for | Safe to delete from a template? |
|---|---|---|
| Tasks | Day-to-day tasks, each in one sprint and linked to an epic | No |
| Sprints | Each sprint and its connected tasks | No |
| Epics | Larger initiatives that span several sprints | Yes, the Epic column just stays empty |
| Capacity (hidden) | Powers the Capacity feature on each sprint | No, and deleting the folder destroys it |
| Bugs Queue | Listing and prioritising software bugs | Yes, it's independent |
| Retrospectives | Discussion points and action items per sprint | Yes, it's independent |
The Tasks board is added when you first install monday dev. If it's deleted by accident, click the plus in your left pane, select Dev templates and then Scrum Team to add the whole folder back.
Running a sprint
Each group on the Tasks board is a sprint, with one group for the backlog of unassigned tasks and one for the active sprint. Columns track the owner, estimated and actual story points, status, an Unplanned tick box, a GitHub link and the connected epic. Comparing Estimated SP with Actual SP is how you get better at planning the next one.
- Click the drop-down arrow beside the New Task button and select New Sprint.
- Give the sprint a name, set start and end dates, record your goals and click Create Sprint.
- Drag tasks from the backlog into the new sprint group.
- Open the group's three-dot menu, click Sprint setup and toggle on Enable automatic Sprint start and complete.
- Set when the current sprint completes and the next one starts, and choose what happens to leftover tasks: keep them, move them to the next sprint, or send them to the backlog.
Use the automatic option if you can. monday.com notes that if you start and complete sprints manually, you lose the automated features, including the generated sprint summary, the burndown chart and Agile Insights. You can only delete a sprint that hasn't started yet; one in progress or completed can't be deleted.
Agile Insights, Kanban and the roadmap
Agile Insights is a board view with a Velocity chart for work completed per sprint, a Planned vs. unplanned chart and a burndown chart. The Kanban view shows the active sprint's tasks as cards under Ready to start, In Progress, Waiting for review, Pending Deploy and Done, and you can set a Work in Progress limit on each column so the team isn't juggling too much at once. If you're deciding which of those ways of working suits you, here's my explainer on kanban vs scrum. The Roadmap tracker organises epics by quarter so stakeholders outside the dev team can follow the plan.
Epics and Hierarchy
On the Epics board each item is an epic with an owner, description, planned timeline, priority and planned quarter. Its Tasks column connects to the Tasks board, and estimated and actual story points and progress are mirrored back from there. Click an epic, open Epic Overview, then Connected boards and All tasks, to see everything under it in one list. The Gantt view puts the same epics on a timeline.
Hierarchy is a newer board view, in Beta and available on Enterprise and Pro plans, that links boards into levels, such as a product roadmap above epics. As of October 2026 you can only add four levels, and the hierarchy is only visible from the level one board. Deleting an item there removes the connection but doesn't delete the items beneath it.
The Bugs Queue and retrospectives
The Bugs Queue groups bugs by status, so you can see new ones, those in progress and those fixed and deployed. It comes with columns for who reported each bug and who's fixing it, a report date, time tracking for how long each bug has been open, and a formula for how long it took to resolve. Share a WorkForms link and anyone outside the team can report a bug, with each submission landing on the board as an item.
The Retrospectives board is meant to be used throughout the sprint, not just at the end. People add discussion points as items while the sprint runs, the team votes in the Vote Column on what to improve, keep or discuss further, and each new sprint starts a new group on the board.
Where AI and integrations come in
As of October 2026, monday AI in monday dev is available on Enterprise and Pro plans, for users whose admins have turned AI on. A Suggested tasks to start column proposes what to work on next, based on the sprint's status and the team's capacity. The categorize action can label each bug report as it arrives, or route new requests to design, engineering or product. In workdocs, the AI Assistant can summarise PRDs, and you can send tasks straight to Cursor.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
For integrations there's GitHub, GitLab, CircleCI, Slack and Microsoft Teams, and an Incident Management solution that logs resolved incidents and works out time to detect, identify and resolve each one.
My verdict on monday dev
I'd use monday dev if your product and engineering teams want sprints, epics and bugs tied together and the rest of the business already works in monday.com, because the roadmap stays readable for everyone. I'd hold off on heavy customisation until you know which boards and columns are load-bearing, and I wouldn't copy boards out of the solution folder at all. If you're comparing it with the obvious alternative, read my take on monday vs Jira.
Most of the time a dev team loses isn't in the code; it's in status updates, triage and chasing what moved. I run AI training and workshops for teams, and help businesses with AI enablement and workflow automation, so the busywork runs itself and people get time back. Most of that work is with SaaS marketing teams and small businesses. Here's how we can work together.
Frequently asked questions
What is monday dev used for?
Managing software development: sprints, epics and roadmaps, a bugs queue, retrospectives and agile reporting, on boards that connect to each other.
Can I delete columns in monday dev?
Not the core ones. Owner, Status, Priority, Type, Estimated SP, Actual SP, Sprints, Epic and Bugs Queue are critical to the workflow and can't be deleted.
Does monday dev work with GitHub?
Yes. You can link GitHub source code to tasks, add the item ID to commit messages, and use the Engineering Performance Dashboard to track sprint tickets alongside their Git status.
Is AI included in monday dev?
monday AI in monday dev is available on Enterprise and Pro plans, for users whose admins have enabled AI capabilities.
What are label change conditions in monday dev?
An Enterprise-only feature that makes a Name, Person, Date or People field required before a status label can change.
