---
# System prepended metadata

title: Sprint 63 Planning 20230201

---

# Sprint 63 Planning 20230201

## Sprint Details

Sprint is from 1-28 February 2023, 19 days total (retro and debrief should be taken into account? TBD.)

(NOTE: President's Day is a federal holiday)

## Allocation

- AJ: 15 (no planned leave, no training)
- Arminta: 19 (TBD, discuss later complete/partial focus on oscal-cli-nodejs)
- Chris: 10
- Dmitry: 4 (focused on OSCAL CAT, discuss other issues)
- Michaela: 12
- Nikita: 10
- Wendell: 5

## Blockers, Concerns, Risks

- AJ: Collaboration and review on strategic plan items vs. work on the board: do we track? If no, do we track it somewhere? How?
- Dmitry: Development onboarding and set up on certain tasks means heavy context-switching and difficult spin-up time. How do we confront and find improvements?
- Dmitry, Nikita, Wendell: we have an informal notion of all projects under the OSCAL umbrella but don't track ownership/responsibilities in each of them/across them. How can we plan and implement changes to improve that?
  - Chris: What do we have capacity to support and what are important emergencies? (Where is the prioritization across the portfolio of projects?)
  - Nikita: How are we tracking Metaschema and Metaschema-related tooling projects that are infrastructure under OSCAL (usnistgov/metaschema-node) if it is not tracked/prioritized under OSCAL work
- Wendell: Channels of communication may be out of balance and we need to focus on that in the next sprit (keep this in mind with issue review).
  - AJ: How do respond to Gitter? How do we respond to GH issues? How do we respond to GH discussion items? How do engage with stakeholders who meet with us directly for focused technical assistance and debugging between sync meetings?
  - Michaela: working with organizational oversight (re PRA) and also strategic communications efforts.
  - Wendell: do we want office hours, do we make time for it?
- Wendell: dependency on FISMA Team generally and especially around RMF 800-53/800-53A/800-53B releases. ("Any week now")

## Goal

Make these things fun and enjoyable: stabilize OSCAL development branch, clarify project/repo relationships, focus on high impact bugs/low-risk features with clear community demand.

## Urgent (short-term) focus areas

### Bugs/low-risk features needed ASAP

- https://github.com/usnistgov/oscal-content/issues/167
- https://github.com/usnistgov/oscal-content/issues/109
- https://github.com/usnistgov/OSCAL/issues/1521
- https://github.com/usnistgov/OSCAL/issues/1151
- https://github.com/usnistgov/OSCAL/issues/1539
- https://github.com/usnistgov/OSCAL/issues/961
- https://github.com/usnistgov/OSCAL/issues/1290
- https://github.com/usnistgov/oscal-content/issues/72

### Stabilizing Dev OSCAL Pipeline and Documenting CI/CD Flow

- https://github.com/usnistgov/OSCAL/issues/1434
- Dependency: https://github.com/usnistgov/metaschema/issues/240
- Dependency: test https://github.com/usnistgov/metaschema/issues/235 and confirm it is resolved with 👇 
- https://github.com/usnistgov/oscal-content/pull/139
- Update metaschema module in OSCAL in `develop` branch (AJ to create new ticket)
- Update OSCAL submodule in oscal-content in `develop` (AJ to create new ticket)

### Communicating intention and process of team outwards to community

- https://github.com/usnistgov/OSCAL/issues/1496
- https://github.com/usnistgov/OSCAL/issues/1633
- https://github.com/usnistgov/OSCAL/issues/1408
- https://github.com/usnistgov/OSCAL/issues/1548

### Documentation fixes and documentation site UX

- https://github.com/usnistgov/OSCAL/issues/1552
- https://github.com/usnistgov/OSCAL/issues/1442
- https://github.com/usnistgov/OSCAL/issues/1178
- https://github.com/usnistgov/OSCAL/issues/1599
- https://github.com/usnistgov/OSCAL/issues/1294
- https://github.com/usnistgov/OSCAL/issues/1369
- https://github.com/usnistgov/OSCAL/issues/1365
- https://github.com/usnistgov/OSCAL/issues/1372
- https://github.com/usnistgov/OSCAL/issues/1373


**Chris had previously committed to:** https://github.com/usnistgov/OSCAL/issues/1398 

## Parking Lot

- GitHub Teams permissions and management
- Connecting to RFC request process for community feedback in sprint?
- Discuss what we want to do with mapping model in `develop` branch?

## Appendix

### What's the prioirity for bugs and issues?

We prioritize from presumed user interactions and their level of importance. This list is subject to change.

1. oscal-content
2. OSCAL
3. oscal-cli/liboscal-java? (TBD: Include? Keep in this order?)
4. oscal-cli-nodes? (TBD: Include? Keep in this order?)

### Repo Filters

- [oscal-content bugs](https://github.com/usnistgov/oscal-content/issues?q=is%3Aissue+is%3Aopen+label%3Abug)
- [OSCAL bugs](https://github.com/usnistgov/OSCAL/issues?q=is%3Aissue+is%3Aopen+label%3Abug)
- [oscal-cli](https://github.com/usnistgov/oscal-cli/issues?q=is%3Aissue+is%3Aopen+label%3Abug)
- [liboscal-java](https://github.com/usnistgov/liboscal-java/issues?q=is%3Aissue+is%3Aopen+label%3Abug)
- [oscal-cli-nodejs](https://github.com/usnistgov/oscal-cli-nodejs/issues?q=is%3Aissue+is%3Aopen+label%3Abugs)