ub.com chat for the whole squad. Coaching focus: read every suggestion before accepting; paste the actual error into chat and ask "what are the likely causes?" before asking for a fix. Success signal: developers describe a specific place it helped and a specific place it got in the way. Silence means no one is really using it. Phase 2 — PR assistance (weeks 5–8) Turn on PR summaries and suggested reviews. Coaching focus: the summary is an aid to the reviewer, not a substitute for reading the diff. Code-owner approval is still mandatory. Success signal: reviewers say summaries help them orient faster, but can each point to a case where the diff disagreed with the summary. Phase 3 — Coding agent (week 9+, only if gates are strong) Precondition checklist BEFORE enabling: [ ] Branch protection enforced on default branch [ ] Required reviews cannot be bypassed [ ] CI is trustworthy and gates the merge [ ] Test coverage on the affected areas is meaningful Start with small, well-scoped issues (typo fixes, dependency bumps, narrow refactors). Treat every agent PR exactly like a human PR.14:T4b8,TEAM ENABLEMENT PACK — Date: Enablement lead: Tier: GitHub Copilot Business 1. SURFACE READINESS Currently using : Ready for next : Blocking control: Not yet : 2. POLICY STUB (the engineering AI policy for this team) Public-code filter : — owner: legal Training exclusion : prompts/code excluded on Business tier — confirmed Content exclusions : Review norm : AI-assisted code is authored code; committer owns it; reviewer reads the DIFF, not just the summary; tests gate merges Licence posture : documented at 3. MEASUREMENT BASELINE (captured BEFORE expanding

Microsoft Copilot Professional