Y24-165 - As PO I would like the an initial backlog of user stories to be drafted to deliver the EMSeq pipeline.

[TWJW-SANGER]

Description
SeqOps would like to move the DNA - EMSeq pipeline from R&D / Bespoke to production to support a larger number of samples coming through.

Additional Context or Information
Google Doc description

Process Map

Acceptance Criteria

• Annotated Process Map with User Stories created (on tab in existing Lucid chart above)
• Backlog of labelled and roughly sized user stories written to deliver the pipeline.
• Creation of page on Confluence under Pipelines to link to these resources.
• Any outstanding questions or risks captured and documented in stories or Confluence as appropriate. [initial questions are in overview google doc]

Knowledge or Stake holders
Scott G created the process and the process map
Sara W is the manager responsible.

Stories created

1. Research story
2. Pipeline configuration story
3. Bed verifications story

[andrewsparkes]

Initial thoughts on stories:

1. research story to determine how to do the submissions (small to medium), options:
   a. one submission only at start, both branches to complete before close off requests
   b. one submission at start for DNA WGS, one extra autosubmission for EM at End Prep plate.
   c. one submission at start for DNA prep, two autosubmissions for EM and WGS at End Prep plate.
2. pipeline configuration story, SS and Limber plus integration suite test with placeholder manual transfer steps where robots will be used (medium to large). No new labware creators or presenters anticipated (unless research story identifies something is needed), so should be all config.
3. bed verifications story to do all the anticipated bed verifications, plus update the integration suite test with robot steps where have placeholder manual steps (small)

[andrewsparkes]

Might have to fold 1 into 2 as you'd need some of the pipeline built in order to test the options?

[andrewsparkes]

Added stories to description