Company OS
This is how we work, decide, and deliver. One place, kept deliberately short. If something here is wrong or out of date, fix it with a PR — don’t work around it.
The whole delivery flow
Section titled “The whole delivery flow”Every box below is a section of this wiki. Start with the stage you’re in.
flowchart LR
Lead["Lead / Sales"] --> Disc["Discovery & BA"]
Disc --> Est["Estimate & SOW"]
Est --> Kick["Kickoff"]
Kick --> Build{"Build loop"}
Build -->|story| Dev["Dev + code review"]
Dev --> QA["QA"]
QA --> Build
Build --> UAT["UAT & sign-off"]
UAT --> Ship["Handover / go-live"]
Ship --> Sup["Warranty & support"]
Jump to
Section titled “Jump to”- The Whole Picture (SDLC) — the entire lifecycle on one page: every stage, gate, and owner. Start here when you’ve lost the thread.
- How We Deliver — turn a lead into a signed, delivered, warrantied project.
- Engineering Standards — how we write, review, and test code.
- Azure DevOps Playbook — branches, PRs, boards, pipelines.
- Roles & Decisions — who owns what, and who decides the big calls.
- Run & Support — operating what we shipped.
- People & Onboarding — getting a new hire shipping fast.
How this wiki works
Section titled “How this wiki works”The rules that keep it trusted and worth reading:
- Every page has one owner and a last-reviewed date (bottom of each page). No owner or 6 months stale → the page gets deleted, not archived.
- Diagram-first. Processes are explained with diagrams, not walls of text. If it needs more than a screen of prose, it becomes a diagram or a link.
- This wiki is the index; Azure DevOps is the source of truth. We describe how we work and link to Boards, Repos, and Pipelines. We never copy board state or pipeline YAML here — it would drift.
- Edit by
PR. Changes go through apull requestlike code. - Add a page only when a question gets asked twice. Fewer, better pages beat exhaustive ones.
Languages / اللغات
Section titled “Languages / اللغات”English is the default. Arabic lives under /ar/. If an Arabic page doesn’t exist yet, you’ll automatically see the English version.
In Arabic pages we keep technical terms in English on purpose — PR, pull request, branch, code review, pipeline, sprint, deployment, and framework names like Angular, .NET, PrimeNG. That’s how we actually talk.