Choose per team space
Run sprints in one space and Kanban in another without imposing one operating model on the organization.
A workflow that fits the team running it
Choose Sprint, Kanban, or no framework for each team space. Use focused modules to take incoming work from triage through planning and execution without losing the wider picture.
Why it matters
Make the work clearer, not heavier.
A sprint team and a team handling a continuous stream of requests should not have to pretend they work the same way. Taskonio makes the framework a team-space choice, then gives each stage of the work a clear place to happen.
Designed around the way real teams decide and deliver.
Give each module a job
Separate incoming requests, preparation, scope selection, and active execution so the team can focus on the decision in front of it.
Keep the work connected
The same hierarchy, task details, and view controls support the workflow as work moves forward.
A closer look
How frameworks and modules works in Taskonio.
01
Triage incoming work before committing to it
Triage gives incoming work a place to be assessed. Read the request, clarify its context, and decide how it belongs in the team’s workflow before treating it as committed scope.
- Review incoming requests in context
- Clarify type, ownership, and priority
- Keep intake separate from active execution
02
Prepare the backlog, then select a realistic sprint
Use Backlog to organize and prepare work. In a Sprint space, Planning adds scope selection and live task and estimate totals, so the team can make an informed commitment.
- Groom epics, items, and sub-items in Backlog
- Select work in Planning
- Check task and estimate totals before starting the sprint
03
Run time-boxed work in Sprint
The Sprint module puts the active commitment in focus. Track completed tasks and estimates against the total, check the sprint day, and choose a table or board for the conversation.
- A focused view of current sprint work
- Visible scope and completion totals
- Multiple views for standups, ownership, and detailed execution
04
Keep continuous work moving with Kanban
Choose Kanban for work that moves continuously rather than in a fixed sprint. Prepare work in Backlog and use Kanban for active execution, with tables as well as board views.
- Separate prepared work from the active flow
- Follow status through a board or a detailed table
- Use the same task hierarchy and view controls
05
Step outside a module with All Tasks
All Tasks gives you a broader place to find work instead of starting from one team’s current module. Return to the task itself for its details and context.
- Find work beyond the current module
- Open the same underlying task
- Keep organization-wide discovery separate from team-level planning
06
Keep the framework optional
Some teams need a clear backlog without a sprint cadence or a Kanban operating model. Choose no framework for that space, and change the framework later through guided property remapping when the team’s needs change.
- No framework is a valid starting point
- Framework selection is independent per team space
- Review property mappings when changing an existing framework
How it works
From setup to useful work.
- 01
Choose the operating model
Create a team space and choose Sprint, Kanban, or no framework based on how that team actually works.
- 02
Prepare and organize
Review incoming work, add useful context, and arrange the backlog into work the team can act on.
- 03
Plan and execute
Select sprint scope or keep a continuous flow moving, using the module and view that fit the moment.
Taskonio’s approach
Shared foundations, different working rhythms
Frameworks change how a team organizes execution. They do not require the organization to maintain separate tools or a different vocabulary for every team.
- Framework choice
- Sprint, Kanban, or no framework per team space.
- Intake
- Triage for assessing incoming work.
- Preparation
- Backlog for organizing and clarifying work before execution.
- Sprint scope
- Planning with selection and live scope totals.
- Execution
- Sprint or Kanban modules suited to the chosen framework.
- Broader discovery
- All Tasks outside the current team module.
Compare this workflow with the tools your team already knows.
Taskonio vs JiraA focused engineering workflow or a deeply configurable platform: choose the operating model your team can sustain.Read comparisonTaskonio vs TrelloA board you can shape around almost anything, or an engineering workflow with the planning structure already in place.Read comparisonTaskonio vs NotionCompare an opinionated engineering workflow with a flexible workspace that combines databases, documents, knowledge, projects, and AI.Read comparison
Considering another tool? Explore the full set of guides to find the right fit for your team.
View all comparisonsRelated features
Keep exploring the workflow.
Sprint planning
Sprint planning that doesn’t slow you down
Plan sprints in minutes with three focused modules - Backlog, Planning, and Sprint - plus live scope totals and flexible views for every planning conversation.
ExploreKanban boards
Kanban boards built for how engineers actually work
Choose Kanban for a clean two-module flow - Backlog and Kanban - with table and board views for teams that want continuous delivery without sprint ceremony.
ExploreCustom views
Your work, your way - custom views for every engineer
Create multiple table and board views across Backlog, Planning, Sprint, and Kanban, then keep adjustments local or share them with the team.
ExploreQuestions
Know before you switch.
Can different teams use different frameworks?
Yes. A framework belongs to a team space, not the entire organization. One team can use Sprint while another uses Kanban or no framework.
Is a board the same thing as the Kanban framework?
No. A board is a view layout. Sprint spaces can also use boards. The framework determines the team’s workflow and modules; the view determines how the work is displayed.
What is the difference between Backlog and Planning?
Backlog is for preparing and organizing work. In a Sprint space, Planning is where the team selects scope and sees live task and estimate totals before starting a sprint.
Can we change the framework later?
Yes. Existing team spaces support framework changes through guided property remapping. Review those mappings so existing work stays meaningful in the new workflow.
Do we have to work in sprints?
No. Use Kanban for continuous work or choose no framework when a flexible backlog is enough.
Start with how your team works
Choose a framework for the team, then shape the views around the work.