Kanban vs Scrum

When creating a project, you choose a methodology. Here's what each one means and how it affects your experience.

Kanban

Kanban is a continuous flow approach. Work items move through statuses (Todo → In Progress → Done) at their own pace, without fixed time periods.

Best for:

• Support teams handling incoming requests
• Teams with unpredictable workloads
• Ongoing maintenance work
• Teams that prefer flexibility over structure

In Dragon Planner, Kanban projects:

• ✅ Have the Board (Kanban) view
• ✅ Have the List and Activity views
• ❌ Don't show Sprint fields
• ❌ Don't have the Backlog view

Scrum

Scrum organizes work into sprints — fixed time periods (usually 1–4 weeks) where the team commits to a set of work.

Best for:

• Product development teams
• Teams that benefit from regular planning cadences
• Projects with defined milestones
• Teams that want to measure velocity and predictability

In Dragon Planner, Scrum projects:

• ✅ Have all views (List, Board, Backlog, Activity)
• ✅ Show Sprint fields on work items
• ✅ Can assign items to sprints
• ✅ Have the Sprint Board for per-sprint tracking

Can I Switch?

Yes! You can change a project's methodology in Project Settings. Switching from Scrum to Kanban hides sprint-related features. Switching from Kanban to Scrum enables them. Your data is preserved either way.

Not Sure?

If you're unsure, start with Kanban — it's simpler and you can always switch to Scrum later as your process matures.