Retrospective
Where did we improve?
- 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)
- Frontend refactoring is going smoothly, we are still on track to meet scheduled release date despite small amount of hiccups and bugs (Ying, Ming (NIH/NCI) [C])
- As side effects, we fixed a few bugs without trying to do so! It proved refactoring is working fine and worth doing! (Ying, Ming (NIH/NCI) [C])
- We had our tickets assigned ahead of the planning meeting and were able to get a deeper look into them in advance of the sprint starting. (Mattu, Alec (NIH/NCI) [C])
What areas still need improvement? ![(sad)](/s/ju8c6n/9012/ly29vq/_/images/icons/emoticons/sad.svg)
- List anything that we could have done better in this sprint (add your name after your comment)
- Admin portal was vastly underestimated, caused some tickets overflowed into next sprint. (Ying, Ming (NIH/NCI) [C])
What you have learned? ![(lightbulb)](/s/ju8c6n/9012/ly29vq/_/images/icons/emoticons/lightbulb_on.svg)
- List anything you learned about in this sprint (add your name after your comment)
- How to use "cross-env" NPM library to unify build scripts for Linux/Mac and Windows. (Ying, Ming (NIH/NCI) [C])
- How to build a component that can be easily integrated with an existing redux store and manage it's own states, etc (Mattu, Alec (NIH/NCI) [C])
Actions