# Value stream issue management for usnistgov/OSCAL#1688

## Background

## Organization

We propose in this draft document a non-exhaustive list of value streams. A value stream is a thematic collection of work items, varying in scope of work by quantity or quality (large epics to small issues), but still related to the same theme in that work. There are different kinds of work items, with some nested-like epics with user stories within them. An epic nested with epics concept is counter-intuitive, so we will label each one as a value stream. For organizational purposes, we organize the value streams grouped by high-level use cases in OSCAL. This grouping may be beneficial to link the resulting value of work completed in a value stream to a downstream developer tasks of making OSCAL-enabled tooling.

## Value streams grouped by use case

### Define control requirements (catalogs)
- Control mapping and relations
- [Add group IDs](https://github.com/usnistgov/OSCAL/issues/1299)
### Customize control requirements (catalogs, profiles)
- Control origination
- [Analyze New Default Control Origination Values in Core OSCAL](https://github.com/usnistgov/OSCAL/issues/1502)
- Parameter management
- [Add System Flag or Prop to Catalog Parameter Guidelines](https://github.com/usnistgov/OSCAL/issues/1411)
- Profile resolution improvements
- [Profile resolution: clarify requirements for identifying 'add' positions](https://github.com/usnistgov/OSCAL/issues/1311)
- [Profile resolution: clarification needed wrt pruning? ](https://github.com/usnistgov/OSCAL/issues/1314)
### Document system elements (CDEF, SSP)
### Data validation and recommendation(all)
- Constraint Management
- [Review Top-Level Model Indices and Supporting Constraints](https://github.com/usnistgov/OSCAL/issues/1431)
- [Fully Deploy OSCAL Metaschema Constraints](https://github.com/usnistgov/OSCAL/issues/1530)
- [Implement new allowed value design](https://github.com/usnistgov/OSCAL/issues/1396)
### Document system implementations (SSP)
- Reusable implementation
- [Component definition needs implementation](https://github.com/usnistgov/OSCAL/issues/1300)
### Share control implementations (CDEF, SSP)
- Reusable implementation
- Customer Responsibility Matrix
### Plan implementation testing (AP)
### Implementation testing (AR, POA&Ms)
### Track implementation findings (POA&M)
### New model functionality (n/a)
### Common metadata (all)
- Party and role management
- [Clarify behavior for conflicts in role, location, party, and reference identifiers across imported OSCAL content](https://github.com/usnistgov/OSCAL/issues/1290)
- Backmatter management
- [Imprecise description of profile backmatter resolution](https://github.com/usnistgov/OSCAL/issues/1442)

### Relations between data elements (all)
### Examples of content (all)
### Model development with Metaschema (n/a)
### Public communication (n/a)
- Website UX improvements
- [Create vision and strategic plan pages](https://github.com/usnistgov/OSCAL/issues/1561)
- Vision Plan
- Strategic Plan
- Strategic Plan updates and review blog posts
### Public communication infrastructure (n/a)
### Developer infrastructure (n/a)
- [Next Steps in Modularizing CI/CD ](https://github.com/usnistgov/OSCAL/issues/1470)
- [Generate and Publish OSCAL Metaschema without XML Entities](https://github.com/usnistgov/OSCAL/issues/1665)
- [Information about collaboration/interaction with NIST OSCAL team.](https://github.com/usnistgov/OSCAL/issues/1656)

### Implementation guides (all)

## Notes