---
# System prepended metadata

title: Key Decision Drivers

---

# Key Decision Drivers

- We will never fully understand requirements
  - we need an agile process that will allow us to discover requirements collaboratively with our community and to work iteratively to define, implement, and test requirements
- A decision or action must increase real-world usage and/or _tactical_ engagement in the development of some part of OSCAL or the whole by the outside community.
  - If observing or measuring that increase is not possible, this is not a valid case of increase.
  - Decisions or actions that are part of incremental testing and experimentation to validate our understanding of requirements and discover new ones.
- A decision or action must work to reduce inter-personal dynamics that impede work within the team.
  - Sometime more conflict is necessary in the short term to put in place measures to improve inter-personal dynamics
- A decision or action must work to clarify and document roles and responsibilities of members within the team.
- A decision or action must increase real-world usage and/or _tactical_ engagement, they _should_ be part of a strategic goal. Those with a related strategic goal are more important and beneficial than those without, those related to strategic goals more important than others have the highest prioirity.
- Strategic goals need to reflect necessary change in an agile way, but they must be stable to allow continued, measurable progess. 


# Core values:

- We work transparently with the community; sharing ideas early and often to get input.
- We don't let perfect be the enemy of good enough.
  - We focus on the 80% solution that requires 20% of time to implement.
- Transparency
  - All work needs to be documented on GitHub, our collaboration platform.