Agile Scrum for Project | Odoo Sprint & Backlog Board | Story Points & Kanban WIP | Jira-style Agile
by CODEerts https://www.codeerts.com$ 149.00
Agile Scrum & Sprints for Project
Run real Scrum and Kanban on Odoo Project.
Sprints, story points, a backlog, WIP limits, epics and a velocity chart.
Everything your team expects from Jira, built on the standard Project app. No Enterprise edition required.
|
Scrum
+ Kanban
|
WIP
Limit Badges
|
Epics
Point Rollup
|
Velocity
Forecasting
|
Odoo 19
Compatible
|
The agile gap every Odoo team knows
Odoo Project is great for tasks, but it is not built for Scrum
|
No sprints or story points
You cannot time-box work into sprints, estimate in points, or see what a team can actually deliver each cycle. |
Kanban columns overflow
Nothing stops ten tasks piling into In Progress. There is no WIP limit and no signal that a stage is overloaded. |
No epics or velocity
Big initiatives have nowhere to roll up, and you have no history of committed versus delivered points to plan the next sprint. |
What this module does
Agile Scrum & Sprints turns Odoo Project into a full Scrum and Kanban tool. Group backlog tasks into time-boxed sprints, estimate them in story points, and run a sprint board that carries unfinished work back to the backlog when a sprint closes, exactly the way Jira does.
Kanban columns enforce a WIP limit with a live count badge that turns red when a stage is overloaded. Epics group related stories and roll up their points and progress automatically, a velocity chart compares committed against delivered points across past sprints, and tasks link to each other as relates, duplicates or causes.
|
🏃
Sprints & Backlog
Plan, start and complete sprints. Estimate the backlog in story points, pull tasks into a sprint, and close it, returning unfinished work to the backlog. |
🚦
WIP Limits on Kanban
Set a work-in-progress limit per stage. A live badge shows the current count against the limit and turns red the moment a column is overloaded. |
📈
Epics & Velocity
Group stories under epics that roll up points and progress automatically, and read your real throughput from a velocity chart to plan the next sprint. |
|
🗂 Product Backlog
A dedicated view of every task not yet committed to a sprint, ready to estimate and pull in. |
🎯 Story Points
Estimate each task in points, independent of the allocated hours, and total them per sprint automatically. |
|
📋 Sprint Board
A Scrum board of the tasks in your active sprints, grouped by stage, with WIP badges on every column. |
🧱 Epic Rollup
Each epic shows its number of stories, total points, points done and a progress bar, all computed automatically. |
|
🔗 Task Links
Link tasks as relates to, duplicates or causes, so dependencies and duplicates are visible, Jira style. |
🔁 Carry-Over on Close
Completing a sprint moves any unfinished task back to the backlog automatically, ready for the next sprint. |
|
📊 Velocity Chart
Committed versus delivered story points for every completed sprint, so you can forecast the next commitment. |
🧩 Builds on Standard Project
Adds to the Odoo Project app you already use and runs on Community as well as Enterprise. No core data changed. |
How it works
1 |
Set WIP limits on your stages On each project stage, set a work-in-progress limit. The kanban board then shows a live count badge on every column. |
2 |
Estimate the backlog Open the Backlog, give each task a story-point estimate, and optionally group stories under an epic. |
3 |
Plan and start a sprint Create a sprint, pull backlog tasks into it, and start it. Committed points are totalled for you. |
4 |
Run the sprint board Move tasks across the board. WIP badges warn you when a column is overloaded, keeping the team focused. |
5 |
Complete and review velocity Close the sprint. Unfinished tasks return to the backlog, and the velocity chart records committed versus delivered points. |
Screenshot walkthrough
Follow one team from an empty backlog to a shipped sprint.
Your active sprint as a Scrum board, grouped by stage. The In Progress column carries a live WIP badge that turns red the moment it holds more tasks than its limit.
Every task not yet committed to a sprint, in one list. Estimate each in story points and set its priority before you pull it into the next sprint.
Open any task and the Agile tab adds story points, its sprint and its epic, right beside the fields your team already uses.
Planned, active and completed sprints on one screen, each row showing committed points, completed points and a progress bar.
The sprint goal, start and end dates, committed versus completed points, and the full list of committed tasks, with one-click Start and Complete.
Group stories under an epic and it totals their points, counts how many are done and shows a live progress bar, with no manual updating.
Each epic lists the stories linked to it and its rollup totals, so a large initiative stays readable even when it spans several sprints.
Committed versus delivered story points for every completed sprint, so you can read your real throughput and commit the right amount next time.
Technical information
|
Version
19.0
|
License
OPL-1
|
Editions
Community & Enterprise
|
Dependencies
project (core)
|
Technical name: codeerts_project_agile · Adds: sprints, backlog, story points, WIP limits, epics, velocity, task links
Frequently asked questions
The module adds a Sprints model and an Agile menu. Create a sprint, pull backlog tasks into it, estimate them in story points and start the sprint. When you complete it, unfinished tasks move back to the backlog automatically, just like Jira.
Yes. Each project stage gains a WIP limit field. On the task kanban a small badge shows the current count against the limit and turns red when a column holds more tasks than its limit, so overloaded stages are obvious at a glance.
Mark any task as an Epic, then link stories to it. The epic shows the number of stories, total story points, points already done and a progress bar, all computed automatically from the stories that sit in a closed stage.
The velocity chart plots committed versus delivered story points for each completed sprint, so you can see your team's real throughput and use it to forecast how much to commit to the next sprint.
Use the version selector at the top of this page to pick your Odoo release. The module builds on the standard Project app and works on both Community and Enterprise.
The team behind this module
About CODEerts
Full-Service Odoo ERP Agency · Solutions That Scale
Every module in our store is built from real client work, tested in production and maintained long-term by a team of Odoo certified consultants. When you need more than an app, we deliver the full solution.
|
🏗️ Implementation
Full Odoo roll-outs from requirements to go-live, across any industry and company size. |
🧩 Custom Development
Bespoke modules, OWL components and business logic built precisely to your workflow. |
🔄 Migrations
Zero-data-loss upgrades from older Odoo versions with full custom module porting. |
|
🔌 Integrations
Payment gateways, shipping carriers, biometric devices, eCommerce and third-party APIs. |
🔍 Odoo Audits
Performance, security and code-quality reviews that surface risks before they become problems. |
🧑💻 Support & Training
Ongoing helpdesk, user training and monthly retainers so your team stays productive. |
Odoo Certified |
6+ Years |
50+ Projects |
10+ Industries |
40+ Published Apps |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Project (project)
• Discuss (mail) |
| Lines of code | 522 |
| Technical Name |
codeerts_project_agile |
| License | OPL-1 |
| Website | https://www.codeerts.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module