🔄 Agile Process
Agile Process Manager
Full agile project management with Scrum, Kanban and Hybrid frameworks. Product backlog, sprint planning, Kanban board with WIP limits, burndown charts, velocity tracking and Scrum Guide 2020 compliant roles. All in one free tool — works on any device.
Get Started Free →🔄
3 Agile Frameworks
Scrum with sprints and ceremonies, Kanban with continuous flow and WIP limits, or Hybrid Scrumban combining both approaches.
📋
Product Backlog
User stories with MoSCoW prioritization, acceptance criteria, story points, Class of Service, dependencies and tags.
📈
Metrics & Charts
Velocity tracking, burndown/burnup charts, CFD, lead/cycle time, throughput, sprint health score and team workload analysis.
👥
Scrum Guide 2020 Roles
Fine-grained permission matrix: Product Owner, Scrum Master, Development Team. Kanban equivalents: SRM and SDM.
See It in Action
How It Works
1
Choose Your Framework
Create a project and select Scrum, Kanban or Hybrid. Each framework comes with tailored columns, roles, metrics and workflows.
2
Build Your Backlog
Add user stories with MoSCoW priority, acceptance criteria, story points and tags. Estimate with integrated Planning Poker.
3
Run Sprints or Flow
Plan sprints with team capacity, track progress on the Kanban board, monitor burndown and velocity, and run retrospectives.
3 Agile Frameworks, One Tool
Choose the methodology that fits your team. Switch between frameworks as your process evolves.
🏃
Scrum
Sprint-based iterative development following the Scrum Guide 2020. Fixed-length sprints (1-4 weeks) with planning, daily standups, sprint review and retrospective. Roles: Product Owner manages the backlog, Scrum Master facilitates ceremonies, Development Team estimates and delivers. Track velocity and burndown across sprints.
Best for: Teams building products with evolving requirements, who benefit from regular
feedback cycles and predictable delivery cadence.
📊
Kanban
Continuous flow management based on David Anderson's Kanban Method. Visualize work on a board with customizable columns, enforce WIP (Work In Progress) limits, define explicit column policies, and categorize work with Class of Service (Standard, Expedite, Fixed Date, Intangible). Use swimlanes to group cards by assignee, priority, CoS or tag. Roles: Service Request Manager and Service Delivery Manager.
Best for: Support teams, maintenance workflows, environments with changing priorities, or
teams transitioning gradually to agile.
🔀
Hybrid (Scrumban)
Combines the best of Scrum and Kanban: keep sprint structure for planning rhythm while using Kanban's WIP limits and flow metrics for daily execution. Optional sprints, simplified ceremonies, and both velocity and flow metrics. Get the predictability of Scrum with the flexibility of Kanban.
Best for: Teams transitioning between frameworks, projects with mixed feature development
and maintenance, or teams needing sprint structure with more flexibility.
Framework Deep Dive
Each framework comes with tailored columns, roles, metrics and workflows. Here's exactly how they work inside Keisen.
🏃 Scrum — Sprint-Based Iterative Development
Keisen implements Scrum following the Scrum Guide 2020 with full ceremony support and role-based permissions.
Sprint Lifecycle (4 Phases)
- Planning — The Product Owner selects stories from the prioritized backlog. The team estimates with integrated Planning Poker and commits based on team capacity (hours per member, adjusted for availability and vacations). Sprint duration is configurable from 1 to 4 weeks.
- Active — The Development Team works on committed stories. The Kanban board shows 4 columns: To Do → In Progress → In Review → Done. Track daily progress with the burndown chart (ideal vs. actual), record daily standup notes (Yesterday / Today / Blockers) per team member, and detect blockers automatically.
- Review — The Scrum Master conducts a formal Sprint Review following Scrum Guide 2020. Each story receives an outcome: Approved, Needs Refinement, or Rejected. Capture stakeholder feedback, demo notes, formal decisions (action items, scope changes, technical decisions) and lessons learned.
- Completed — Velocity is calculated automatically. The sprint links to an integrated Retrospective board. Unfinished stories return to the backlog for the next sprint.
Scrum Roles (Scrum Guide 2020)
- Product Owner — Owns the backlog. Creates, edits, deletes and prioritizes stories. Sets the Definition of Ready. Defines the final estimate after team discussion. Assigns team members to stories.
- Scrum Master — Facilitates ceremonies. Creates, starts and completes sprints. Runs Sprint Review and Retrospective. Configures WIP limits and board settings. Removes impediments.
- Development Team (Developer, Designer, QA) — Estimates stories via Planning Poker. Self-assigns to stories. Moves own stories on the board. Records daily standup notes. Cannot create stories or manage sprints.
- Stakeholder — View-only access. Participates in Sprint Review feedback. Cannot modify stories, sprints or board.
Scrum Metrics
- Velocity — Story points completed per sprint, with trend line across sprints
- Burndown Chart — Points remaining per day vs. ideal burndown line
- Burnup Chart — Points completed per day showing scope changes
- Sprint Health Score — Automatic risk detection when progress falls below 80% of ideal
- Estimation Accuracy — Estimated vs. actual points comparison
- Lead Time & Cycle Time — Days from creation to done / in-progress to done
📊 Kanban — Continuous Flow Management
Keisen implements Kanban following David Anderson's Kanban Method with 6 practices: visualize workflow, limit WIP, manage flow, make policies explicit, implement feedback loops, improve collaboratively.
Board Configuration (6 Default Columns)
- Backlog — All incoming work. Policy: "Sort by priority". No WIP limit.
- Refinement — Stories being analyzed and detailed. WIP limit: 5. Policies: "Max 2 days in column", "Requires acceptance criteria".
- Ready — Stories that meet the Definition of Ready. WIP limit: 5. Policy: "Estimations completed".
- In Progress — Active development. WIP limit: 3. Policy: "Max 1 item per person", "Daily status update".
- Review — Code review / QA. WIP limit: 2. Policy: "Max 24h in column", "Requires code review".
- Done — Completed work. Policy: "All acceptance criteria met". No WIP limit.
WIP Limits & Visual Status
Each column shows a real-time WIP indicator with color coding: green = under limit, orange = at limit, red = exceeded. Expedite items (Class of Service) can exceed WIP limits when needed for urgent work.
5 Swimlane Types
- Class of Service — Expedite (top, red) → Fixed Date (purple) → Standard (blue) → Intangible (grey)
- Assignee — One horizontal row per team member
- Priority — Must (top) → Should → Could → Won't (bottom)
- Tag — One row per tag for category-based grouping
- None — Classic flat column view
Class of Service (4 Categories)
- Standard (blue) — Normal FIFO processing, respects WIP limits
- Expedite (red) — Urgent work, can exceed WIP limits, processed immediately
- Fixed Date (purple) — Immovable deadline, scheduled commitment
- Intangible (grey) — Technical debt, infrastructure, no immediate business value
Kanban Roles
- Service Request Manager (SRM) — Equivalent to Product Owner. Manages incoming requests, prioritizes backlog, defines acceptance criteria.
- Service Delivery Manager (SDM) — Equivalent to Scrum Master. Manages flow, monitors WIP limits, facilitates improvement meetings, removes impediments.
- Team Members — Pull work from the board, self-assign, update status daily.
Kanban Metrics
- Cumulative Flow Diagram (CFD) — Visualizes work item count per status over time, revealing bottlenecks
- Lead Time — Days from story creation to completion
- Cycle Time — Days from "In Progress" to "Done"
- Throughput — Items completed per week
- Work Item Age — How long each item has been in its current status
- Flow Efficiency — Ratio of active work time vs. total lead time
- WIP Distribution — Current items per status column
🔀 Hybrid (Scrumban) — Best of Both Worlds
Hybrid combines Scrum's sprint rhythm with Kanban's flow management. Keep the predictability of time-boxed iterations while using WIP limits and flow metrics for daily execution.
Board Configuration (Simplified)
- To Do — Sprint-committed stories ready to start. No WIP limit.
- In Progress — Active development. WIP limit: 5. Policy: "Max 1 item per person".
- Done — Completed work. Policy: "All acceptance criteria met".
What Hybrid Takes from Each Framework
| From Scrum | From Kanban |
|---|---|
| Optional sprint time-boxing | WIP limits per column |
| Velocity tracking | Flow metrics (CFD, lead/cycle time) |
| Burndown / Burnup charts | Continuous improvement cadence |
| Sprint planning & capacity | Pull system (team decides when to start) |
| Retrospectives per sprint | Column policies |
When to Use Hybrid
- Teams transitioning from Scrum to Kanban (or vice versa)
- Projects mixing feature development (sprint-based) with maintenance (flow-based)
- Teams that need sprint structure for planning but want more flexibility in daily execution
- Organizations with mixed maturity levels across teams
Scrum Guide 2020 — Role Permissions Matrix
Every action is controlled by a dual-layer role system: access role (owner, admin, member, viewer) combined with functional role (Product Owner, Scrum Master, Developer). For Kanban projects, roles are remapped: PO → Service Request Manager, SM → Service Delivery Manager.
| Action | Product Owner | Scrum Master | Dev Team | Stakeholder |
|---|---|---|---|---|
| Backlog Management | ||||
| Create / Edit / Delete Stories | ✅ | — | — | — |
| Prioritize Backlog (MoSCoW) | ✅ | — | — | — |
| Set Final Estimate | ✅ | — | — | — |
| Assign Team Members | ✅ | — | — | — |
| Sprint Management | ||||
| Create / Start / Complete Sprint | — | ✅ | — | — |
| Facilitate Retrospective | — | ✅ | — | — |
| Configure WIP Limits | — | ✅ | — | — |
| Estimation & Development | ||||
| Estimate Story Points (Planning Poker) | — | — | ✅ | — |
| Self-assign to Stories | — | — | ✅ | — |
| Move Own Stories on Board | ✅ | ✅ | ✅ | — |
| Move Any Story on Board | ✅ | ✅ | — | — |
| Team Management | ||||
| Invite Members | ✅ | ✅ | — | — |
| Remove Members / Change Roles | ✅ | — | — | — |
Kanban equivalents: Product Owner → Service Request Manager (SRM) · Scrum Master → Service Delivery Manager (SDM) · Development Team → Team Members. Same permission matrix, different terminology.
Complete Agile Toolkit
- Product Backlog Management — User stories with "As a... I want... So that..." template, MoSCoW prioritization (Must, Should, Could, Won't), acceptance criteria, business value scoring and story dependencies
- 7-State Story Workflow — Track stories through Backlog → Refinement → Ready → In Sprint → In Progress → In Review → Done with automatic status management
- Sprint Planning & Capacity — Configure sprint duration (1-4 weeks), calculate team capacity based on member availability, allocate stories by story points vs. capacity
- Kanban Board with WIP Limits — Customizable columns with Work In Progress limits, visual WIP status indicators (green/orange/red), and explicit column policies per Kanban Practice #4
- 5 Swimlane Types — Group cards by Class of Service, Assignee, Priority (MoSCoW), Tag, or no grouping for maximum board flexibility
- Class of Service (Kanban) — Categorize work items as Standard (FIFO), Expedite (can exceed WIP), Fixed Date (immovable deadline), or Intangible (tech debt)
- Burndown & Velocity Charts — Real-time burndown with ideal vs. actual lines, velocity tracking across sprints with trend analysis, sprint health scoring
- Lead Time & Cycle Time — Live calculation of lead time (creation to done) and cycle time (in-progress to done) for flow efficiency analysis
- Scrum Guide 2020 Permissions — Role-based access: PO manages backlog, SM manages sprints, Dev Team estimates and self-assigns. Fine-grained permission matrix for every action
- Daily Standup Tracking — Structured "Yesterday / Today / Blockers" notes per team member with blocker detection and historical tracking
- Sprint Review with Outcomes — Formal review with story-level outcomes (Approved / Needs Refinement / Rejected), stakeholder feedback, demo notes and formal decisions
- Team Capacity & Skill Matrix — Dual-view capacity planning (Scrum standard + hours view), skill matrix, member availability tracking with unavailable date ranges
- Integrated Estimation Room — Connect to Planning Poker sessions with Fibonacci, T-Shirt, PERT and Bucket estimation methods directly from stories
- Built-in Retrospective — Link sprints to retrospective boards with 5 templates, action items tracking and sentiment analysis
- Audit Trail — Complete change history tracking 11 actions (create, update, delete, move, estimate, assign, complete, start, close, invite, join) across 5 entity types
- Google Sheets Export — Export 5 formatted sheets: Product Backlog, Sprint Planning, Team & Capacity, Retrospective, and Aggregated Metrics
Methodology Guide: Each framework includes a built-in interactive guide with sections on
roles, events, artifacts, best practices, anti-patterns and FAQs — helping your team adopt agile the right
way.
Built on Proven Methodologies
Keisen's Agile Process Manager isn't just another project board — it implements the actual frameworks as defined by their creators. Scrum follows the Scrum Guide 2020 by Ken Schwaber and Jeff Sutherland, with proper accountability boundaries between Product Owner, Scrum Master and Developers. Kanban implements David Anderson's six practices — from visualizing workflow to collaborative improvement — with real WIP limits, explicit policies and Class of Service categorization.
The permission matrix enforces Scrum's separation of concerns: only the Product Owner manages the backlog, only the Scrum Master manages sprints, and only Developers estimate. This isn't optional — it's how the framework is designed to work, and Keisen enforces it so your team builds the right habits from day one.
Combined with the integrated Estimation Room for Planning Poker, the Retrospective Board for continuous improvement, the Eisenhower Matrix for strategic prioritization, and Smart Todo for operational task management, Keisen provides a complete agile ecosystem — not just isolated tools.
Frequently Asked Questions
What agile frameworks does Keisen support?
Keisen supports 3 agile frameworks: Scrum (sprint-based with full
ceremony support including planning, daily standup, review and retrospective), Kanban
(continuous flow with WIP limits, swimlanes, column policies and Class of Service), and
Hybrid/Scrumban (combining sprint structure with Kanban flow and WIP limits). Each
framework has tailored features, roles, metrics and default board configurations.
Is the Agile Process Manager free?
Yes, Keisen Agile Process Manager is free to use. You can create agile projects,
manage sprints, use Kanban boards with WIP limits, track velocity, generate burndown charts, manage your
team and invite members. Sign in with Google and start working in seconds.
What's the difference between Scrum, Kanban and Hybrid?
Scrum uses fixed-length sprints (1-4 weeks) with 4 ceremonies
(Planning, Daily Standup, Sprint Review, Retrospective) and 3 defined roles (Product Owner, Scrum Master,
Development Team). It tracks velocity and burndown. Kanban uses continuous flow with no
sprints — work is pulled when capacity is available. It uses WIP limits, column policies, swimlanes and
Class of Service. It tracks CFD, lead time, cycle time and flow efficiency. Hybrid
(Scrumban) combines optional sprints with WIP limits and flow metrics — giving you the planning
rhythm of Scrum with the flexibility of Kanban.
How does the Kanban board work?
Keisen's Kanban board features customizable columns with configurable WIP limits
that show visual status (green = under limit, orange = at limit, red = exceeded). You can define explicit
column policies (e.g., "Max 24h in this column", "Requires code review"), use 5 swimlane groupings (Class
of Service, Assignee, Priority, Tag, None), and categorize work with 4 Classes of Service (Standard,
Expedite, Fixed Date, Intangible). Cards are managed by drag-and-drop.
How does sprint management work?
Sprints follow the complete lifecycle: Planning (select stories
from backlog, set capacity by team member), Active (track progress with burndown chart,
daily standup notes, blocker detection), Review (evaluate each story with formal
outcomes: Approved, Needs Refinement, Rejected, plus stakeholder feedback and formal decisions), and
Completed (automatic velocity calculation, retrospective link). Sprint duration is
configurable from 1 to 4 weeks.
How does the 7-state story workflow work?
Every user story follows 7 states: Backlog (new, unprioritized) →
Refinement (being analyzed, acceptance criteria added) → Ready (meets
Definition of Ready, estimation done) → In Sprint (committed to a sprint) → In
Progress (development started) → In Review (code review / QA) →
Done (all acceptance criteria met). Only stories marked as "Ready" can be added to a
sprint, enforcing proper grooming.
How do user stories work in Keisen?
User stories follow the "As a... I want... So that..." template. Each story
includes: MoSCoW priority (Must, Should, Could, Won't), acceptance
criteria (checklist of conditions for "Done"), story points (estimated via
Planning Poker), Class of Service (Standard, Expedite, Fixed Date, Intangible),
business value (1-10 scoring), tags for categorization,
dependencies on other stories, and assignee. Stories also track actual
hours and custom progress percentage.
What is MoSCoW prioritization?
MoSCoW is a prioritization technique used in Keisen's product backlog. Each story is
classified as: Must Have (critical, project fails without it), Should
Have (important but not vital), Could Have (desirable if time permits), or
Won't Have (out of scope for now). The backlog can be sorted by MoSCoW priority, and
swimlanes can group cards by priority level on the Kanban board.
How does the Estimation Room integrate with Agile Process?
Keisen's Estimation Room integrates directly with the
Agile Process Manager. From any user story, you can launch a Planning Poker session using Fibonacci,
T-Shirt, PERT (3-point), Bucket, Decimal, Dot Voting or Five Fingers methods. Team members vote
anonymously, discuss differences, and reach consensus. The final estimate is set by the Product Owner and
saved as story points on the story. Only Development Team members can estimate — the Product Owner can
only set the final value.
What is Class of Service in Kanban?
Class of Service categorizes work items by their urgency and nature:
Standard (blue) — normal FIFO processing, respects WIP limits; Expedite
(red) — urgent work that can exceed WIP limits and is processed immediately; Fixed Date
(purple) — work with an immovable deadline; Intangible (grey) — technical debt or
infrastructure work with no immediate business value. You can group the board by Class of Service using
swimlanes.
What are swimlanes and how do they work?
Swimlanes are horizontal groupings on the Kanban board. Keisen supports 5 types:
Class of Service (Expedite on top, then Fixed Date, Standard, Intangible),
Assignee (one row per team member), Priority (Must → Should → Could →
Won't), Tag (one row per tag), and None (classic flat view). Swimlanes
help visualize workload distribution, identify bottlenecks per category, and manage parallel workflows.
How does the Sprint Review work?
Keisen implements Sprint Review as a formal Scrum Guide 2020 event. The Scrum Master
conducts the review, recording: demo notes for each story demonstrated,
story-level outcomes (Approved, Needs Refinement, or Rejected for each story),
stakeholder feedback from attendees (PO, SM, developers, stakeholders, guests),
formal decisions (action items, backlog changes, scope changes, technical decisions) with
assignees and due dates, and lessons learned. A sentiment score (1-5) captures overall
team mood.
What is the Daily Standup feature?
Each sprint includes structured daily standup tracking. Team members record three
things: What did you do yesterday?, What will you do today?, and
Any blockers? Blockers are automatically detected and flagged. Standup notes are saved
per member per day, creating a historical log that helps identify patterns, recurring blockers and team
velocity trends.
How does team capacity planning work?
Keisen offers dual-view capacity planning: Scrum Standard View
shows velocity, throughput and suggested story points per sprint. Hours View shows
available hours per member (configurable hours/day), allocated hours, and utilization percentage. Each
team member has configurable capacity hours per day (default 8), skills
for the skill matrix, and unavailable dates (vacations, holidays) that automatically
reduce sprint capacity.
What is the Skill Matrix?
The Skill Matrix visualizes your team's competencies in a grid. Each team member
lists their skills (e.g., React, Python, UX Design, Testing), and the matrix shows coverage across the
team. This helps sprint planning by identifying skill gaps, balancing workload across specialists, and
making informed assignment decisions. It's particularly useful for cross-functional Scrum teams.
How do WIP limits work?
WIP (Work In Progress) limits cap the number of items allowed in each Kanban column.
When a column is under the limit, the header shows green. At the limit shows orange. Exceeding the
limit shows red. This prevents bottlenecks and multitasking. Expedite items (Class of Service)
can exceed WIP limits when urgent work needs immediate attention. WIP limits are configurable by the Scrum
Master / Service Delivery Manager.
What is a Cumulative Flow Diagram (CFD)?
The CFD is a Kanban metric that shows the count of work items in each status over
time, stacked as colored bands. It reveals: bottlenecks (widening bands),
throughput (the rate items reach "Done"), WIP trends (total active
items), and lead time approximation (horizontal distance between bands). It's the primary
diagnostic tool for Kanban teams and is available in Kanban and Hybrid frameworks.
What are Column Policies?
Column Policies are explicit rules that define when a work item can enter or exit a
Kanban column. Following Kanban Practice #4 (Make Policies Explicit), Keisen lets you
define policies per column — for example: "Requires acceptance criteria defined" for Refinement,
"Max 1 item per person" for In Progress, "Requires code review approval" for Review, or
"All acceptance criteria met" for Done. Policies are visible in column headers and help teams
build consistent workflow habits.
What Scrum roles and permissions does Keisen support?
Keisen implements Scrum Guide 2020 compliant roles with a
fine-grained permission matrix: Product Owner (backlog management, story creation, prioritization, final
estimate, member assignment), Scrum Master (sprint management, facilitation, retrospective, WIP
configuration), Development Team (estimation via Planning Poker, self-assignment, own story movement). For
Kanban, equivalent roles are Service Request Manager (SRM) and Service Delivery Manager (SDM).
Stakeholders have view-only access. Each action has specific role-based access control — see the full permission matrix.
How do Kanban roles differ from Scrum roles?
In Kanban projects, Keisen remaps Scrum roles to Kanban equivalents: Product
Owner → Service Request Manager (SRM) who manages incoming requests and prioritizes the
backlog, Scrum Master → Service Delivery Manager (SDM) who manages flow, monitors WIP
limits and facilitates improvement meetings, Development Team → Team Members who pull
work and self-assign. The permission matrix stays the same — only the terminology changes to match Kanban
conventions.
What metrics and charts are available?
Metrics adapt to your framework: Scrum gets Velocity tracking,
Burndown/Burnup charts, Sprint health scoring, Estimation accuracy. Kanban gets
Cumulative Flow Diagram (CFD), WIP distribution, Flow efficiency, Work item age. All
frameworks get Lead Time and Cycle Time (live calculation), Throughput metrics, Team workload
analysis, Scope change tracking, and Commitment trend analysis. Metrics are displayed in a dedicated
dashboard with interactive charts.
How does the Retrospective integrate with sprints?
After completing a sprint, Keisen links it to an integrated Retrospective board. You can choose from 6 templates:
Start/Stop/Continue, Sailboat, 4Ls (Liked/Learned/Lacked/Longed For), Starfish, Mad/Sad/Glad, and DAKI
(Drop/Add/Keep/Improve). The retrospective follows guided phases: Create → Brainstorm → Group → Vote →
Discuss → Finalize. It includes sentiment voting, weather icebreakers, coach tips, and action items
tracking. For Kanban, retrospectives can be scheduled at any cadence.
How does the Audit Trail work?
Keisen tracks every change in your agile project with a complete audit trail. It
logs 11 actions (create, update, delete, move, estimate, assign, complete, start, close,
invite, join/leave) across 5 entity types (project, story, sprint, team, retrospective).
Each entry records who performed the action, when, the previous and new values, and which fields changed.
The audit log is filterable by action type, entity, user and date range.
Can I export project data?
Yes, Keisen exports to Google Sheets with 5 formatted sheets:
Product Backlog (all stories with metadata), Sprint Planning (timeline
and allocations), Team & Capacity (roster with skills and capacity),
Retrospective (items, sentiment, action items), and Aggregated Metrics
(velocity, throughput, lead/cycle time). The export uses Google Sheets API v4 and requires Google Sign-In.
What are story dependencies?
Story dependencies let you define blocking relationships between user stories. If
Story B depends on Story A, it means A must be completed before B can start. Dependencies help the Product
Owner sequence the backlog correctly and prevent the team from starting work that's blocked by incomplete
prerequisites. Dependencies are visible on the story card and in the backlog view.
Can I switch frameworks after creating a project?
The framework (Scrum, Kanban, or Hybrid) is set when you create the project and
determines the available tabs, default columns, roles and metrics. If you need a different framework, you
can create a new project with the desired framework and move your stories. The Hybrid framework is a good
starting point if you're unsure — it supports both sprint-based and flow-based work.
Can I use Keisen for remote agile teams?
Absolutely. Keisen is a web application accessible from any browser, designed for
both remote and co-located teams. Features like real-time collaboration, team invites with role
assignment, daily standup tracking, integrated retrospective boards, and Google Sheets export make it
ideal for distributed agile teams. All team members can access the backlog, board and metrics
simultaneously.
Does the Agile Process Manager work on mobile devices?
Yes, Keisen Agile Process Manager is fully responsive and works on smartphones,
tablets, and desktop browsers. You can manage your backlog, track sprints, and monitor metrics from any
device — no app download needed. The interface adapts to your screen size for the best experience.
How does Keisen compare to Jira or Monday.com?
Keisen offers 3 agile frameworks in one tool (Scrum, Kanban, Hybrid), Scrum Guide
2020 compliant role permissions, built-in Estimation Room integration with
7 estimation methods, integrated Retrospective boards with 6 templates,
a team skill matrix, a complete audit trail, and Google Sheets export — all for free. Unlike complex
enterprise tools with per-user pricing and months of setup, Keisen is designed for teams that want
powerful agile features with immediate productivity.
Explore Other Tools
📋
Smart Todo
Collaborative Kanban board with custom columns and smart task management
🎯
Eisenhower Matrix
4-quadrant prioritization by urgency and importance with RACI integration
🃏
Estimation Room
Real-time collaborative estimation with 7 methods including Planning Poker
💬
Retrospective
5 retrospective templates with guided phases and anonymous feedback
Ready to run your agile projects?
Start managing sprints, Kanban boards and team capacity with a tool built for real agile teams. Free for everyone.
Get Started Free →