 |
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)
- Our team did everything we could to ensure we could deliver the software release before the holiday. This required a lot of work addressing bugs by engineers and thorough testing by the QA team, and a comprehensive Design QA review. Thank you to everyone for the efforts. (Kuffel, Gina (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)
- The CloudOne team continues to be a dependency that cannot be planned for. (Kuffel, Gina (NIH/NCI) [C] )
| Panel | ||
|---|---|---|
| ||
Something I learned about during this sprint is... |
How to use GiHub pages for building and serving a website and using plugins and markdown extensions. (Kuffel, Gina (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.
