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

Define "Critical" for Our Application #39

Open
sinke237 opened this issue Sep 3, 2024 · 0 comments · May be fixed by #80
Open

Define "Critical" for Our Application #39

sinke237 opened this issue Sep 3, 2024 · 0 comments · May be fixed by #80
Assignees
Labels
Operational Scheme Operational Scheme Evaluation US7

Comments

@sinke237
Copy link
Collaborator

sinke237 commented Sep 3, 2024

Description: Document the criteria that determine what "critical" means for our application, including aspects like uptime, performance, and user impact.
Tasks:

  • Gather input from stakeholders regarding what constitutes critical functionality.
  • Outline the implications of downtime or performance degradation for each feature.

Acceptance Criteria:

  • A clear definition of "critical" is documented and approved by stakeholders.
@sinke237 sinke237 added Operational Scheme Operational Scheme Evaluation US7 labels Sep 3, 2024
@sinke237 sinke237 self-assigned this Sep 16, 2024
@sinke237 sinke237 linked a pull request Sep 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Operational Scheme Operational Scheme Evaluation US7
Projects
None yet
1 participant