Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Vision and Strategic Plan Pages #1561

Open
6 tasks
aj-stein-nist opened this issue Nov 29, 2022 · 6 comments
Open
6 tasks

Create Vision and Strategic Plan Pages #1561

aj-stein-nist opened this issue Nov 29, 2022 · 6 comments
Labels
Aged A label for issues older than 2023-01-01 enhancement User Story

Comments

@aj-stein-nist
Copy link
Contributor

aj-stein-nist commented Nov 29, 2022

User Story

As a NIST OSCAL community member, in order to understand short, medium, and long-term goals of the NIST OSCAL Team and expectations of the community, I want to see a public website page with OSCAL's vision statement, and the strategic plan (or plans over the course of years if they change).

Goals

  • Add vision in Add Vision Page #1801
  • A copy of the OSCAL strategic plan, if already existing, on a page in the pages.nist.gov/OSCAL site that is easy to find
  • Evidence in the code changes of a directory/site structure to support historical record of changes to the vision and/or strategic plans as they evolve over time

Dependencies

N/A

Acceptance Criteria

  • All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
  • A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
  • The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.
@aj-stein-nist
Copy link
Contributor Author

I had talked to @david-waltermire-nist and @iMichaela and they did not oppose/welcomed tackling this in the next sprint, I would like to know more about what the rest of the team thinks, if there is no opposition to the idea of publishing it generally (details like publication of tasks assignments should be redacted maybe?) and move forward with this in the upcoming/new sprint (61).

@aj-stein-nist aj-stein-nist moved this from Needs Triage to Allocated to Milestone in Issue Triage Dec 1, 2022
@aj-stein-nist
Copy link
Contributor Author

aj-stein-nist commented Dec 16, 2022

Holding off on this for now, moving to backlog.

@aj-stein-nist
Copy link
Contributor Author

Time to bring this back out of the back log and move forward with this after the conference.

@iMichaela
Copy link
Contributor

@aj-stein-nist - Great. I suggest linking it to the website analysis and review issue (#1778). to identify the optimal place for it.

@aj-stein-nist
Copy link
Contributor Author

@aj-stein-nist - Great. I suggest linking it to the website analysis and review issue (#1778). to identify the optimal place for it.

We can discuss offline or in sprint planning but I would prefer we add a vision page and reorganize it accordingly later, going incrementally with content and organization as we need. If we need to discuss this, let me know and we can set aside some time tomorrow morning maybe?

@aj-stein-nist aj-stein-nist removed this from Allocated to Milestone in Issue Triage Sep 20, 2023
@aj-stein-nist
Copy link
Contributor Author

@iMichaela and I to update strategy and vision docs for FY24. Then we can move this work to ready.

@Compton-US Compton-US added the Aged A label for issues older than 2023-01-01 label Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aged A label for issues older than 2023-01-01 enhancement User Story
Projects
Status: Blocked
Development

No branches or pull requests

3 participants