 |
Page History
| Page properties | ||||
|---|---|---|---|---|
|
Retrospective
| Panel | ||||
|---|---|---|---|---|
| ||||
Something our team did well is... |
- List anything that went well in this sprint including shout out to others that went out of their way to help (add your name after your comment or feel free to keep it anonymous)
- New cart Page design and Team effort on BE task (Rana, Ambar (NIH/NCI) [C] )
| Panel | ||||
|---|---|---|---|---|
| ||||
Something that I think we need to improve for next time is... |
- List anything that we could have done better in this sprint (these comments can be anonymous)
- Discrepancy in Data between Dev, QA & Local difficulty to verify the issue & fix. (Rana, Ambar (NIH/NCI) [C] )
| Panel | ||
|---|---|---|
| ||
Something I learned about during this sprint is... |
Learn more about Cypher query and opensearch. (Rana, Ambar (NIH/NCI) [C] )how to add pagination to avoid exceeding the Neo4j heap memory limit when loading large amounts of data into Opensearch (other groups encountered this and came up with this solution - we aren't near this limit w/ our data sizes, but it's nice to know a solution/workaround exists if needed). (Miller, Eric (NIH/NCI) [C])
Actions
- Kuffel, Gina (NIH/NCI) [C] to create at task in order to bundle web fonts with our application.
- Better catalog/documentation of system changes, ie. a DevOps log
- Always reschedule standup meetings
- Be sure to update test cases if and when requirements evolve
- DevOps leads should sign off on new microservice designs
- Create an external service to cache data from external APIs (Performance Caching)
- Mukherjee, Amit (NIH/NCI) [C] to create a DevOps task to implement performance caching and polling/reporting of outages to Slack or email.
- Demos will only be on QA or Dev (QA being the preferred environment) moving forward.
- Use GitHub actions to automate things like deployments for the BE, FE
