Epic Goal

• Apply AI in the various activities related to how we plan, develop, test, automate and/or document ACM 2.15
• Capture what each team did, including assessing quantitative and qualitative benefits and challenges.
• After delivery of ACM 2.15, we will pull-together all the data and identify specific things that worked well, and apply that in ACM 2.16.

• This is about using AI for our day-to-day, and is separate from building AI capabilities into ACM such as ACM-18874).

Why is this important?

• Application of AI is an objective across Global Engineering.

Scenarios

• Ideas for using AI code assistants and metrics to measure progress here.

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)