Odoo Project Management with Agile Methodology: Scrum and Kanban Guide

Odoo's project management module supports both traditional waterfall and agile methodologies. For teams practicing Scrum or Kanban, the module provides sprint planning, Kanban boards, burndown charts, velocity tracking, and time-based resource planning---all integrated with Odoo's broader ecosystem of HR, accounting, and CRM modules. This guide covers configuring and running agile projects in Odoo from sprint zero through continuous delivery.

Key Takeaways

• Odoo supports Scrum (sprint-based), Kanban (flow-based), and hybrid agile methodologies natively
• Sprint planning uses story point estimation with velocity-based capacity calculation
• Burndown and burnup charts track sprint progress with automatic daily updates
• The Kanban board enforces WIP limits, swimlanes, and custom workflow stages
• Time tracking integrates with timesheets for accurate project costing and resource planning

Choosing Your Agile Methodology

Scrum in Odoo

Scrum works best for teams that deliver work in regular iterations. In Odoo, Scrum implementation includes:

• Sprints: Time-boxed iterations (typically 2 weeks) with defined capacity
• Product backlog: Prioritized list of user stories and tasks
• Sprint backlog: Subset of backlog items committed for the current sprint
• Ceremonies: Sprint planning, daily standups, review, and retrospective

Kanban in Odoo

Kanban suits teams with continuous delivery requirements. Key elements:

• Visual board: Columns representing workflow stages with cards for work items
• WIP limits: Maximum number of items allowed in each column
• Pull system: New work is pulled into the pipeline only when capacity is available
• Continuous flow: No sprint boundaries---work flows from backlog to done continuously

Hybrid Approach

Many teams combine elements of both. Use sprints for planning and estimation while maintaining Kanban's WIP limits and visual management during execution.

Project Setup

Creating an Agile Project

1. Navigate to Projects > Configuration > Projects
2. Create a new project with the following settings:
   • Name: Project name
   • Methodology: Scrum, Kanban, or Standard
   • Allow timesheets: Enable for time tracking
   • Allow subtasks: Enable for task decomposition
   • Stage configuration: Define your workflow stages

Configuring Workflow Stages

Define stages that match your team's workflow at Projects > Configuration > Stages:

Story Points and Estimation

Enable story point estimation in project settings. Each task includes a story point field that the team estimates during planning. Common scales:

• Fibonacci: 1, 2, 3, 5, 8, 13, 21 (most popular)
• T-shirt sizes: XS=1, S=2, M=3, L=5, XL=8
• Linear: 1 through 10

Sprint Management

Creating Sprints

Navigate to Projects > Sprints to manage iterations:

1. Sprint name: Descriptive name (e.g., "Sprint 14: Payment System")
2. Start date: Sprint begin date
3. End date: Sprint end date (typically 2 weeks later)
4. Capacity: Total story points the team can handle (based on velocity)
5. Goals: Sprint objectives that guide prioritization

Sprint Planning

During sprint planning:

1. Open the Product Backlog view showing all unassigned stories
2. Sort by priority and business value
3. Drag stories from the backlog into the sprint
4. The capacity indicator shows remaining capacity as stories are added
5. Stop adding stories when capacity reaches 80-90% (buffer for unexpected work)

Sprint Execution

During the sprint, the Kanban board shows all sprint items flowing through stages. Key operations:

• Assign tasks: Drag tasks to team members or use the assignee dropdown
• Log time: Click the timer button to start/stop time tracking on a task
• Update status: Drag cards between columns as work progresses
• Add blockers: Flag tasks that are blocked with reason and blocked-by references
• Subtasks: Break down large stories into implementation subtasks

Sprint Review and Retrospective

At sprint end:

1. Review the Sprint Report showing completed vs planned story points
2. Move incomplete items back to the product backlog or forward to the next sprint
3. The Velocity Chart updates automatically with the sprint's actual completion rate
4. Document retrospective outcomes as tasks for process improvement

Kanban Board Features

Board Configuration

Customize the Kanban board at Projects > Board Settings:

Columns: Map to your workflow stages. Each column can have:

• A WIP limit that shows a warning when exceeded
• A column color for visual identification
• Automatic assignment rules

Swimlanes: Horizontal divisions that group cards by:

• Priority (critical, high, medium, low)
• Assignee
• Task type (feature, bug, chore)
• Epic or parent story

Card display: Configure which fields appear on the card face:

• Story points
• Assignee avatar
• Due date
• Tags/labels
• Time spent

WIP Limits

Work-in-progress limits are essential for Kanban. Configure limits per column:

1. Navigate to the column settings
2. Set the maximum number of tasks allowed
3. When the limit is reached, the column header turns yellow (warning) or red (exceeded)
4. Team members should pull work from the overloaded column or help resolve blockers before starting new work

Cumulative Flow Diagram

The cumulative flow diagram (CFD) at Projects > Reporting > Cumulative Flow shows how work items accumulate in each stage over time. Key insights from the CFD:

• Widening bands: Indicate bottlenecks in a specific stage
• Parallel bands: Indicate healthy flow with consistent throughput
• Converging bands: Indicate the team is completing more than they are starting (good)

Tracking and Reporting

Burndown Chart

The burndown chart tracks remaining work against the sprint timeline:

• Ideal line: Straight line from total story points to zero over the sprint duration
• Actual line: Real progress updated daily based on completed story points
• Scope changes: Visible as jumps in the burndown (stories added mid-sprint)

Access the burndown chart at Projects > Reporting > Burndown.

Velocity Tracking

Velocity measures the team's throughput in story points per sprint:

• Rolling average: Average of the last 3-5 sprints, used for capacity planning
• Trend: Increasing velocity indicates improving team efficiency or estimation accuracy
• Volatility: High sprint-to-sprint variation indicates estimation inconsistency

Cycle Time Analysis

For Kanban teams, cycle time (how long a task takes from start to completion) is the primary metric:

Time Tracking Integration

Timesheet Logging

Enable timesheets on the project to track time against tasks:

1. Click the timer button on a task to start tracking
2. The timer runs in real time (visible in the header bar)
3. Stop the timer when switching tasks or taking breaks
4. Manual timesheet entries can be added at Timesheets > My Timesheets

Project Costing

With timesheets enabled, Odoo calculates project costs based on:

• Employee cost rate: Defined on the employee record
• Billable rate: Defined on the project or customer contract
• Time logged: Actual hours from timesheets

The Projects > Reporting > Profitability report shows revenue, cost, and margin per project, per employee, and per time period.

Integration with Other Odoo Modules

Helpdesk Integration

Link support tickets to project tasks. When a bug is reported through the helpdesk module, create a task in the development project directly from the ticket. The task links back to the ticket for traceability.

Sales Integration

For professional services teams, project tasks can be linked to sales order lines. Time logged against tasks feeds into invoicing:

• Time and materials: Invoice actual hours logged
• Fixed price: Track time for profitability analysis without invoicing per hour
• Milestone-based: Invoice upon task completion

HR Integration

Resource planning considers employee availability from the HR module:

• Time off: Approved leave reduces sprint capacity
• Working schedule: Part-time employees contribute proportional capacity
• Skills: Match task requirements to employee skills for optimal assignment

ECOSIRE Project Management Services

Implementing agile methodologies in Odoo requires both software configuration and process design expertise. ECOSIRE's Odoo implementation services include project management module setup, workflow configuration, and agile coaching for teams transitioning from traditional project management. Our training services provide hands-on workshops for Scrum masters, product owners, and team members learning the Odoo project interface.

Related Reading

• Odoo Planning Module Guide
• Odoo Helpdesk for Customer Support
• Odoo Reports and Dashboards Guide
• Odoo Approvals Workflow
• SLA Management and Service Contracts in Odoo

Can Odoo replace dedicated project management tools like Jira or Asana?

For many teams, yes. Odoo's project module handles Kanban boards, sprint management, time tracking, and reporting that cover 80-90% of what teams use Jira or Asana for. The advantage of Odoo is integration with invoicing, HR, and CRM. The gap is in advanced features like custom JQL queries (Jira) or advanced timeline views. Teams with complex developer workflows may find Jira more specialized.

How does Odoo handle cross-project dependencies?

Use task dependencies (blocked-by relationships) that can span projects. The Gantt chart view shows cross-project dependencies with connecting arrows. For portfolio-level planning, the Planning module provides a resource view across all projects showing allocation and conflicts.

What is the maximum recommended team size for a single Odoo project?

Odoo handles projects with up to 50-100 team members effectively. For larger organizations, create separate projects per team and use the portfolio view for cross-team coordination. The Kanban board performance remains smooth with hundreds of active tasks.