 |
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)
| 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)
- I'm still trying to fix the Redis issue and am wondering if this ever worked on any of the tiers. I initially misattributed this to the environment variables not being correctly set, but I guess it is something client-related in the node-redis library. Sorry if I wasted your time with investigating this Charles and Mike. (Miller, Eric (NIH/NCI) [C] )
| Panel | ||
|---|---|---|
| ||
Something I learned about during this sprint is... |
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.
