 |
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 annonymous)
- Team collaboration Ankerso, Seni (NIH/NCI) [C]
- Like the way how thoroughly the user stories are written. The user stories are well updated without delay as/when the requirements evolve, which is very helpful for the QA team.
| 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)
- It would be great if we come up with some easier solution to publish Bento-core packages. Ankerso, Seni (NIH/NCI) [C]
| Panel | ||
|---|---|---|
| ||
Something I learned about during this sprint is... |
- I have learned how to extend configurations to support multiple projects. And how storybook makes development/bug fixing easier by providing development playground. Ankerso, Seni (NIH/NCI) [C]
- Testing Design QA tickets are new to us. We are learning this new approach.
- I've mainly been testing the last several months, so this sprint I've had a refresher course in my writing of detailed test cases - Megan Lewis
Actions
- 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.
