Y25-005 - As a TL I would like to work through the 16S pipeline process map and build an initial backlog of user stories to support it in Limber.
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 111
- Forks
- 34
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 29
Description
Description
As a TL (Tom W) I would like to work through the 16S pipeline process map and build an initial backlog of user stories to support it in Limber.
Acceptance Criteria
The following outputs from the research are produced:
- An estimated set of user stories to implement the pipeline labelled '16S'
- An annotated process map showing links to user stories.
- Updated Confluence project page.
Who the primary contacts are for this work
TBD
Knowledge or Stake holders
TBD
Additional context or information
See the Confluence page "16S"in PSD-public under Projects
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Confluence page "16S" in PSD-public and the 16S pipeline process map referenced by the issue. Work through the map to identify an estimated set of user stories labelled "16S", annotate the map with links to those stories, and update the Confluence project page. The issue lists no primary contacts or stakeholders, so those need to be established before work can proceed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100