Spike: Breaking Down the LLM Epic

[julialawrence]

User Story

As an engineer I would like to break down the LLM epic and generate plan of attack and story stubs that will allow the team to deliver to the definition of done of the epic.

Value / Purpose

This plan of attack will not only highlight any lingering questions and assumptions and identify dependencies and information gaps but will also be used to track path to completion of the epic.

Useful Contacts

@julialawrence Edwin Bajomo

User Types

No response

Hypothesis

If we carry out a break down exercise with the involvement of the PM , DM and SO, we will give the team more confidence that they're delivering the right thing.

Proposal

We are seeking to address the following:

Integrate Bedrock (LLM) tool in to the Analytical Platform.

1. How do we offer this?
2. Frankfurt or Virginia or both?
3. Who manages model approvals?
4. Constraints?
5. Security?
6. Documentation?

Identify users for the LLM tool and gauge the performance

1. ??????

Put in place mechanism for capturing user feedback

1. How do we want to track this?

Consider how to integrate the identity management and access control into the tool

1. Not sure if this is relevant

Additional Information

No response

Definition of Done

• Dependencies, blockers and assumptions identified
• Where possible, plan of delivery drafted
• Stories raised

[julialawrence]

https://docs.google.com/document/d/11qyHBk80_-WZvubdQngbiXLhCMqwlQQfmKuTjb8KPtY/edit