Team and lifecycle governance
What the exam tests
This domain tests role ownership, code and architecture governance, technical debt management, deployment lifecycle controls, and quality gates that keep an OutSystems portfolio maintainable across releases.
Core rules
- Define ownership: the Architect owns the Architecture Canvas and exceptions; the Tech Lead owns code quality, reviews, and delivery standards; QA owns test evidence; operations owns environment controls.
- Use Architecture Dashboard findings as a governance backlog. Set a technical debt threshold and an exception process with an owner and expiry date.
- Manage lifecycle through versioned solutions and Lifetime deployment plans. Require release notes, rollback plans, and environment-specific configuration checks.
- Apply quality gates: peer review, automated tests where feasible, security review for exposed APIs, performance checks for high-traffic screens, and a production readiness checklist.
- Grow the team through reusable components, module documentation, and review feedback that teaches the standard rather than only fixing the defect.
Worked example
Architecture Dashboard shows a Core module consuming an End-User module. The Tech Lead records the finding, assigns an owner, moves the shared logic to Foundation, updates references, and schedules the fix in the next sprint. A review gate prevents new upward dependencies. Reasoning: the issue is a lifecycle risk, not a one-off defect; ownership and a gate stop recurrence.
Traps that cost marks
Treating governance as paperwork; ignoring Dashboard debt; hero deployments without rollback; code review limited to style; and letting exceptions live forever without an owner.