Delivery and project leadership
What the exam tests
This domain tests how a Tech Lead plans and runs OutSystems delivery: slicing scope, estimating platform work, organizing the backlog, running reviews, and moving solutions through environments without bypassing governance.
Core rules
- Use discovery and design before build. Confirm the Architecture Canvas placement and integration contracts early.
- Slice work vertically: screen, service action, data change, security role, test, and deployment task. A backlog item that says only build screen is incomplete.
- Estimate platform work explicitly: screen design, aggregates, integration calls, role checks, site properties, and deployment. Add risk for external integrations and data migration.
- Define environments: Development, QA, Pre-Production, Production. Promote through Lifetime deployment plans; do not develop directly in Production.
- Run peer code reviews against naming, reuse, error handling, security roles, and architecture rules. Review before merge, not after release.
Worked example
A feature needs a new customer screen, a new entity field, an ERP integration call, and a manager-only approval. Break it into data model, Core service action, UI, role check, integration error path, test, and deployment plan. Estimate the integration separately because ERP latency and contract changes are the main uncertainty. Reasoning: the estimate now reflects real OutSystems work and exposes the approval and deployment dependencies before the sprint starts.
Traps that cost marks
Estimating only the visible screen; ignoring security and deployment tasks; letting developers publish manually to shared environments; skipping architecture review until late; and accepting scope creep without re-estimating integration and test effort.