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

chore(SprintOrg): Prepare for the upcoming Sprint #422

Open
3 of 6 tasks
lolaapenna opened this issue Dec 10, 2024 · 2 comments
Open
3 of 6 tasks

chore(SprintOrg): Prepare for the upcoming Sprint #422

lolaapenna opened this issue Dec 10, 2024 · 2 comments

Comments

@lolaapenna
Copy link
Collaborator

lolaapenna commented Dec 10, 2024

Task Description*
To organize all Apeiro and Heureka sprint activities

Acceptance Criteria:

  • Apeiro Backlog: Review committed epics for sprint 12
  • Apeiro Backlog: Outline stakeholder-understandable epics planned for Sprint 13
  • Apeiro Backlog: Review Apeiro commitments in the next Heureka Core Meeting on 11th Dec.
  • Apeiro Backlog: Update Apeiro project board - Next Apeiro Monthly backlog meeting takes place on 13th Dec.
  • Heureka Backlog: Review committed epics for sprint 12
  • Heureka Backlog: Outline epics for sprint 13
@lolaapenna
Copy link
Collaborator Author

lolaapenna commented Dec 11, 2024

For Apeiro

Post-User interviews activities

Continuous scan update
The job tracking (improved scanner) protocol has been completed - enable comms between scanners and heureka core
Distributed, asynchronous and fault tolerant

@lolaapenna
Copy link
Collaborator Author

lolaapenna commented Dec 11, 2024

Apeiro Epics for Takt 13

  1. (heureka): Implement Continuous Scans for the Scanners#30

Update:
The job tracking protocol for the improved scanner has been completed. This enables communication between the scanners and the Heureka core. The system is now distributed, asynchronous, and fault-tolerant, ensuring robust and efficient operations.

  1. (heureka): Enable Multiple Clusters for the Scanners#29

No Update - Probably move 2 sprints ahead

  1. (heureka): Requirements Definition for Remediation Management
### Description
Following the user interviews conducted during the workshop, user feedback on existing implementations as well as expectations regarding the remediation of issues will be translated to define requirements for the Remediation Management feature of Heureka.

### Objectives
Understand common challenges: analyze the difficulties users experience with the current patch management process to inform feature development.
Cluster user expectations: consolidate user suggestions for the remediation management feature of Heureka.
Prioritize development efforts: assess and prioritize potential features and improvements based on the feedback and their anticipated impact on efficiency.
Enhance UX: Improve the overall user experience by addressing pain points on the current state of Heureka.

### Acceptance Criteria
- [ ] Break down the requirements into smaller, actionable tasks or user stories. 
- [ ] Conduct a detailed analysis of user interview data to identify key themes and challenges related to remediation management.
- [ ] Compile a list of user-suggested features and improvements, categorizing them by priority and feasibility.
- [ ] Develop a prioritized roadmap for feature implementation based on user feedback and strategic goals.
- [ ] Document all requirements clearly and concisely, ensuring they are actionable and measurable.
- [ ] Review the finalized requirements before proceeding to development.

4. **(heureka): Deployment of the Scanners**

### Description
The implementation of a CI/CD build and deployment Pipeline for Heureka.

### Objectives
To streamline and automate the process of integrating code changes, testing, and deployments.

### Acceptance Criteria
- [ ] Enablement for Deployment Implementations
- [ ] Documentation for Deployment Implementations
- [ ] Deployment for Heureka Core
- [ ] Deployment for Keppel
- [ ] Deployment for NVD Scanner
- [ ] Deployment for K8s Assets Scanner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant