3. Development and Feedback

Cadence: 2-week sprints; daily standups; sprint reviews with live demos; retros with 3–5 concrete improvements per sprint.

Engineering practices: trunk-based development; protected main; PR reviews; pair/mob for complex areas; contract tests for integrations; consumer-driven API testing; test pyramid enforced; security scans in CI; dependencies with SBOM.

CI/CD:

• Build → unit/integration tests → SAST/DAST → artifact sign → deploy to UAT → smoke tests → manual approval → prod deploy (blue/green or canary) → automated rollback on health-check failure.

• Quality bar:
• Unit test coverage thresholds; p95 latency thresholds in UAT; error budget policy; A11y checks; i18n; feature flags with kill switch.

• Feedback loops:
• UAT cohorts; pilot group heatmaps; in-app feedback widget; shadow traffic; A/B where applicable.
• Documentation: ADRs, API docs, runbooks, onboarding guides, architectural decision log.
• Release readiness: checklists for training artifacts, support scripts/macros, known issues doc, KB articles, comms plan.