Warning
🚧 Work in Progress: This page is currently under construction. Content may be incomplete or subject to change. To contribute, see the contribution guide.
Acceptance Criteria
Standards for determining when a feature or project is ready to move from development to staging, and from staging to production.
Development → Staging gate
Before deploying to staging, the following must be true:
Code quality
- Code reviewed and approved by at least one peer (PR approval)
- No critical or high linting/static analysis violations
- Unit tests written and passing for all new business logic
- Test coverage meets the squad’s threshold ((fill in — e.g., ≥ 70%))
Functionality
- All user stories / requirements implemented
- Feature tested in the development environment
- No known P1/P2 bugs outstanding
Documentation
- Code is documented (docstrings, inline comments for complex logic)
-
README.mdupdated if applicable - System documentation in this portal updated or created
Security
- No secrets in code (see Secrets Management)
- LGPD checklist completed if personal data is handled
- Dependencies scanned for known vulnerabilities
Staging → Production gate
Before go-live, the following must be true:
Testing
- UAT (User Acceptance Testing) completed and signed off by business owner
- Integration tests passing in staging environment
- Performance/load tested if the feature is on a critical path
Operations readiness
- Runbook created and reviewed by the ops team
- Monitoring and alerts configured (see Alert Catalog)
- Rollback plan documented and tested
- On-call team briefed on the new feature/system
Governance
- Change ticket opened in ServiceNow
- Maintenance window reserved if required
- Stakeholder communication sent
Info
Who approves the gates?:
- Dev → Staging: squad lead or technical owner
- Staging → Production: technical owner + business owner sign-off