How oca/project-agile works
Project type and purpose
• This is an Odoo “project_scrum” add-on module (version 10.0) that extends the core Project app with Scrum features (sprints, user stories, tests, meetings, etc.).
• It is not a standalone app but a plug-in that lives inside an Odoo server, enhancing its project management capabilities.
File structure
• Top-level:
• project_scrum/ – your module’s code
– models/ (Python ORM classes: project, sprint, meeting, US, test, task, actors)
– views/ (XML menu, form & tree views, mail templates)
– data/ (initial sequences, demo data, test task view)
– security/ (access rules, groups)
– i18n/ (translations)
– static/ (descriptions, assets)
– tests/ (unit tests)
– __manifest__.py (module metadata)
• setup/ – tooling for packaging/installing under Odoo’s “addons” path
• Config files: .travis.yml, .gitignore, oca_dependencies.txt, CI badges in README.
README
• Confirms it’s an OCA (Odoo Community Association) agile project management module.
a. Frontend (Odoo Web Client in the browser)
b. Odoo HTTP Server
c. Your module “project_scrum” (models, views, data, security, i18n, static)
d. Core Odoo modules (project, mail, base)
e. PostgreSQL database
f. External services (e.g., SMTP/Mail server for notifications)
Relationships & data flows
• Browser ↔ HTTP(s) ↔ Odoo Web Controller ↔ ORM Layer ↔ PostgreSQL
• ORM ↔ Python model classes in project_scrum & core modules
• XML view definitions ↔ Controller generate HTML/JSON for browser
• Mail templates in project_scrum/views ↔ Odoo mail subsystem ↔ SMTP server
Architectural patterns & principles
• MVC (Model = your Python files; View = XML definitions; Controller = Odoo HTTP + JS)
• Module-based extension: project_scrum hooks into existing project menus, models, workflows
• Data-driven (initial CSV/XML for security & sequences, demo data)
Technologies & frameworks
• Python 3 + Odoo 10 ORM
• XML for view definitions, data loading
• PostgreSQL as persistent store
• QWeb/JS for client interactions