End2End Onboarding Learning Path

Document objective: This is the umbrella document for the entire set of documents in the KomITi Academy learning library. The goal of the library is to take a Candidate from a complete beginner to an independent Odoo/Python engineer in the KomITi way of working:

• KomITi engineering codexes,
• KomITi infrastructure (AWS, Terraform, Docker setup),
• KomITi git discipline (branch checkout / commit / push / pull / promote workflow),
• KomITi Odoo custom modules development,

In short, the candidate will learn the full DevOps cycle end-to-end — from provisioning cloud infrastructure with Terraform and Docker to developing, testing and deploying custom Odoo modules.

1) On-boarding Project Plan

1.1) Scope of Work (SoW)

Your learning is organized as a project. The project follows a sequence of tutorials in KomITi Academy, each covering a distinct discipline. Each tutorial ends with a self-check or a practical task; you move to the next tutorial only after confirming the exit criteria with the mentor.

• Project & Product Management Roles
  • Scope: who owns what — Product Manager, Business Owner, Project Manager, Service Owner — and why a developer must understand each role before writing code.
  • Exit: candidate can explain the four roles and map them to real KomITi documents and decisions.
• Git & VS Code Basics
  • Scope: Git concepts (branch, commit, push, merge), VS Code elements (Workspace, Explorer, Source Control panel etc.), the KomITi promotion flow (feature → staging → main).
  • Exit: self-check passed; candidate task on komiti_academy project completed (first clean PR).
• Infrastructure: Terraform, Docker & AWS
  • Scope: AWS fundamentals (EC2, VPC, security group, EIP), Docker & container fundamentals, Terraform (provider, resource, variables, state, plan/apply), the KomITi infra stack, problem-class separation (infra vs. runtime vs. application).
  • Exit: infra checklist passed; foundations practical drill completed; local Terraform + Docker Desktop lab running.
• Odoo from 0 to Hero
  • Scope: building a complete library Odoo 19 module step-by-step — scaffold, models, relations, views, actions/menus, security, business logic, automated tests, website UI.
  • Exit: exercise completed; library module installs, passes tests and is demonstrated to the mentor.

Glossary is a reference document used alongside every tutorial above.

1.2) Schedule Plan

• Sprint 1: Set-up local environment, do first git PR
• Sprint 2: one small Odoo task with review
• Sprint 3: independent quickfix + smoke test
• Sprint 4: independent end-to-end task in the KomITi workflow
• Month 6: stable mid-level delivery
• Month 12: professional level for most Odoo/KomITi tasks

Final project checkpoints:

• Day 14: Docker containers running localhost Odoo (web service + PostgreSQL), library module skeleton (Steps 1–2: scaffold, manifest, app menu)
• Day 30: installable MVP (Steps 3–6: models, security, views, tests)
• Day 60: business logic + negative tests (Step 7: ISBN validation, constraints)
• Day 90: website UI + exercise completed + demo to mentor (Step 8 + final exercise)

2) Daily / weekly learning rhythm

Daily (2–3h focused learning): 45 min theory, 90 min practical code/task, 15 min journaling (what was learned).

3) Definition of Done for “0 → pro”

The candidate has completed the on-boarding when all of the following are true: each tutorial's exit criteria are met, the library module installs, passes automated tests and is demonstrated to the mentor.

99) Tasks & tools you will need

These are not dry, read-only tutorials. Every lesson contains hands-on exercises woven into the text, and most tutorials end with a dedicated Section 99 where you do a practical task on a real project. To follow along you will need: