This is a repository for project management in the event-driven architecture POC project.
Time span 2024-05-02 until 2024-08-02. What: replace one timer in production with an event. How: implement a basic pub/sub messaging pattern using the confluent Kafka platform. Why: evaluate viability of messaging pattern at clinical genomics to reduce turn around times.
@seallard will act as a facilitator, setting up meetings, planning and ensuring the project moves forward.
The user stories are created as milestones here in this repo. The implementation plan is broken down into work item issues which are associated with the milestone. The sprint starts once the sprint planning is done and lasts for a preset time period (usually two weeks).
Doing the steps above separately decreases uncertainty about what needs to be done which means we get more things done.
Title: A short, descriptive title.
As a [type of user],
I want [an action or feature],
So that [benefit or reason].
Acceptance Criteria
- Criteria 1
- Criteria 2
- Criteria 3
...
Notes
- Additional information.
- Dependencies.
- Related user stories.Each story is assigned a priority based on how important it is to production.
The developers prepare for a refinement meeting for a specific user story and discuss the way to implement it. The decided upon implementation plan is documented and an estimate of the amount work is done. Separate work item issues are created based on the implementation plan and associated with the story milestone.
Based on the dependencies, priority and work estimate, the developers decide on which stories to work on during the sprint. Individual work items are scheduled for the sprint - put into the ready column on the project board. Developers are assigned to the user stories and know which work items they should work on.
The developers implement the work items. If anything is unclear regarding the implementation, a technical refinement is scheduled if necessary. If anything is unclear regarding the acceptance criteria, a user story meeting is scheduled if necessary.
Once the sprint is over, the devs meet and