Skip to content

Ai strategy for Software Engineering#321

Open
martyn-fewtrell wants to merge 3 commits intomainfrom
ai-strategy
Open

Ai strategy for Software Engineering#321
martyn-fewtrell wants to merge 3 commits intomainfrom
ai-strategy

Conversation

@martyn-fewtrell
Copy link
Contributor

Initial draft of Software Engineering's AI Strategy Document

Introduces a comprehensive AI strategy for Software Engineering, detailing the adoption and governance of developer-facing AI tools (primarily GitHub Copilot). The document covers principles, objectives, use cases, capability development, governance, security, implementation roadmap, metrics, risk mitigation, and review processes to ensure responsible and secure AI adoption.
Refined language to emphasize platform controls over sandboxes for AI developer tools. Updated "Enabling Platform & Tooling" for consistency, removed redundant lines, and omitted outdated references to annexes and sandboxes. Edits improve clarity and align the strategy with current Copilot adoption practices.
@snyk-io-eu
Copy link

snyk-io-eu bot commented Feb 26, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Comment on lines +229 to +232
- Over-reliance on generated code � enforce mandatory peer review and testing.
- Data leakage via external services � redact sensitive inputs.
- IP and licensing uncertainty � provide legal guidance and approval workflows.
- Uneven adoption � monitor usage and target support to teams lagging behind.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove odd characters


This is a living strategy and will be reviewed annually to reflect technology, policy and operational lessons learned.

---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Get rid of these line breaks, the H2 already has line breaks so it just breaks up the document flow


This strategy aligns with the UKHO AI strategy and Data Strategy and supports cross-departmental interoperability, auditability and assurance. It complements existing security, accessibility and procurement policies and provides actionable controls for safe developer-facing AI adoption.

Refer to the Code Generation Tools Policy for detailed organisational requirements on the use of code generation and AI-assisted development tools: `software-engineering-policies/CodeGenerationTools/CodeGenerationToolsPolicy.md`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make this a link to the actual policy

Implementation notes:

- Licensing: maintain a licence registry and reconcile seat usage quarterly.
- Training approach: each team will schedule team-level sessions at a cadence appropriate to their members; cadence will vary according to need. Periodic deep-dive workshops will remain available for cross-team topics. New starters must complete basic Copilot training as part of onboarding.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is basic Copilot training to be found?

- 50%+ of engineers have completed basic Copilot training within 6 months.
- Two case studies demonstrating measurable productivity gains.

### Phase 2: Integrate & Scale (Years 2�3)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another odd character

Copy link
Contributor

@elerivaliant elerivaliant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Content reads fine, could use some links to where we're doing some of the things we're saying we going to do later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants